Chapter Three

Software Project Management

Approaches
 Outlines
Traditional Software Project management approaches
Waterfall Six Sigma
Critical Path Method (CPM) Critical Chain Project Management (CCPM)
Agile Software Project Management
KANBAN, SCRUM
Lean KANBAN, Extreme Programming (XP),
Hybrid
Scrumban, Agile Six Sigma,
PRINCE2 Agile

2
 Outlines
Traditional Software Project management approaches
• Waterfall
• Six Sigma
• Critical Path Method (CPM)
• Critical Chain Project Management (CCPM)

3
 Traditional Project Management
A project management methodology is a set of principles
and practices that guide you in organizing your projects to
ensure their optimum performance.
Traditional project management is a universal practice
which includes a set of developed techniques used for
planning, estimating, and controlling activities.
The aim of those techniques is to reach a desired result on
time, within budget, and in accordance with specifications.

4
 Waterfall methodology
 The Waterfall method is a traditional approach to project management.
 Its tasks and phases are completed in a linear, sequential manner, and each
stage of the project must be completed before the next begins.

5
 Six Sigma methodology
 Six Sigma is a methodology that helps organizations in making their
process better and more efficient by identifying and removing errors
and variations.
 Variations in processes can lead to errors, these errors can lead to
product defects and product defects can lead to poor customer
satisfaction.
 By reducing variation and errors Six Sigma can reduce process costs
and increase customer satisfaction.
 Six Sigma was introduced in 1986 by an American Engineer Bill
Smith.
6
 Six Sigma methodology
 He introduced this term while working at Motorola.
 Industries like manufacturing, service industry, government
agencies, aerospace, and e-commerce use Six Sigma to improve
their processes and product quality.
 Six Sigma is a process of producing high and improved quality
output.
 This can be done in two phases
 Identification and
 Elimination.

7
Six Sigma methodology

8
Six Sigma methodology

9
Six Sigma methodology

10
What Is Lean Six Sigma?

11
17-12

Critical Path Method

Critical Path Method (CPM) is a method used in project planning,
generally for project scheduling for the on-time completion of the
project.
It helps in the determination of the earliest time by which the whole
project can be completed.
There are two main concepts in this method namely critical task and
critical path.
Critical Task: is the task/activity that can't be delayed otherwise the
completion of the entire project will be delayed.
It must be completed on time before starting the other dependent tasks.
17-13

Critical Path Method

Critical path: is a sequence of critical tasks/activities and is the largest
path in the project network.
It gives us the minimum time which is required to complete the entire
project.
The activities in the critical path are known as critical activities and if
these activities are delayed then the completion of the entire project is
also delayed.
17-14

Critical Path Method

Benefits of using the critical path method in

project management:
Show the project schedule visually.
Highlight important tasks with CPM.
Use CPM to find and handle risks.
CPM helps the project team communicate better.
17-15
The Network Diagram

Network (precedence) diagram – diagram of project activities that

shows sequential relationships by the use of arrows and nodes.
Activity-on-arrow (AOA) – a network diagram convention in which
arrows designate activities.
Activity-on-node (AON) – a network diagram convention in which
nodes designate activities.
Activities – steps in the project that consume resources and/or time.
Events – the starting and finishing of activities, designated by nodes in
the AOA convention.
17-16

The Network Diagram (cont’d)

Path
Sequence of activities that leads from the starting node to the finishing node
Critical path
The longest path; determines expected project duration
Critical activities
Activities on the critical path
Slack
Allowable slippage for path; the difference the length of path and the length
of critical path
 Project Network – Activity on
17-17

Arrow
Order
AOA furniture 4
Furniture
Locate 2 setup
facilities

Remodel
1 5 6
Move in

Interview
Hire and
train
3
17-18
Project Network – Activity on
Node
Order
furniture

Locate Furniture
2 setup
facilities
AON
1 6
Move in
Remodel

S 5 7

Hire and
Interview train

3 4
17-19

Network Conventions

a
b
c a

c
b

a c
a c

b Dummy
activity
b d
17-20

Example 1

6 weeks
Deterministic 4
time estimates
3 weeks
8 weeks 2

11 weeks Move in
1 5 6
1 week

4 weeks
9 weeks

3
 Example 1 Solution
Critical Path

Path Length Slack

(weeks)
1-2-3-4-5-6 18 2
1-2-5-6 20 0
1-3-5-6 14 6

17-21
17-22

Computing Algorithm

Network activities
ES: early start
EF: early finish
LS: late start
LF: late finish
Used to determine
Expected project duration
Slack time
Critical path
17-23

Example

Reading Assignment
17-24

Critical Chain Project Management

(CCPM)

Reading Assignment
Agile Software
Project
Management
 What Is Agile Project Management
(APM) ?
 Agile Project Management (APM) is an iterative and flexible
methodology that emphasizes adaptability, collaboration, and
customer satisfaction.
 Initially developed for software projects, it’s now applied across
diverse industries to manage dynamic, fast-changing
environments.
 Through short sprints and continuous feedback, APM enables teams
to deliver value quickly, adapt to evolving needs, and ensure
alignment with business goals.

26
 What Is Agile Project Management
(APM) ?
 Breaks projects into smaller sprints for faster and flexible delivery.
 Incorporates ongoing customer feedback to refine product
development.
 Promotes teamwork between developers, stakeholders, and clients.
 Enables teams to quickly adjust to changing priorities and
requirements.
 Focuses on learning and refining processes throughout the project
lifecycle.

27
Benefit of Agile Project Management
(APM)

28
Phase of Agile Project Management (APM)

29
 Phase of Agile Project Management (APM)
Phase Description Key Activities
Define the product vision and overall project • Create project charter or vision statement
Envision objectives. Identify stakeholders, high-level scope, • Define product goals & target users
and business goals. • Choose Agile framework (Scrum, Kanban, etc.)
• Create Product Backlog (list of features)
Break down the vision into prioritized features and • Define Epics and User Stories
Speculate
create a release roadmap. • Estimate story points
• Prioritize backlog (e.g., MoSCoW method)
Conduct Sprint Planning
Execute iterations/sprints to develop working Develop, code, test user stories
Explore/Excution product increments. Team builds, tests, and Daily Scrum meetings (15 min stand-ups)
integrates features continuously. Continuous integration and testing
Deliver working software each sprint
Review feedback from users and stakeholders, Sprint Review meeting (demo completed features)
Adapt/Review assess performance, and adjust processes or goals as Collect feedback from users or product owner
needed. Update backlog based on feedback
Release working increment to users or production
Close
Wrap up the project, finalize documentation, and Sprint Retrospective: discuss what went well, what
release/Retrospectiv
conduct a retrospective to capture lessons learned. didn’t, and how to improve
30 next sprint
e
Document learnings and adjust processes
Common Agile Project Management (APM) ?

31
 What is Scrum?

• Scrum is a powerful Agile framework that has

revolutionized the world of software development.
• In this section, we’ll delve into the key elements of Scrum
like
• Core principle
• Scrum Role
• Scrum Artifacts
• Scrum Ceremonies
32
 The Core Principles of Scrum
• Empirical Process Control: scrum is built on the idea that complex
problems can’t be fully understood upfront.
• Instead, it relies on transparency, inspection, and adaptation to navigate
uncertainties.
• Iterative and Incremental Development: scrum divides the project
into small, manageable parts called “sprints,” typically 2–4 weeks
long.
• Each sprint delivers a potentially shippable product increment, allowing for
rapid feedback and adaptation.
.

33
 Scrum Roles
• Product Owner: the product owner represents the customer and is
responsible for defining and prioritizing the product backlog,
ensuring that the team is working on the most valuable features.
• Scrum Master: the Scrum master serves as a servant-leader for the
team, ensuring that Scrum principles and practices are followed,
removing impediments, and facilitating collaboration.
• Development Team: The development team is a self-organizing
group responsible for delivering the product.
• It consists of developers, testers, designers, and others with the necessary
skills.

34
 Scrum Artifacts
• Product Backlog: this is the prioritized list of all features, user
stories, and tasks that need to be completed for the product.
• The product owner owns and manages the backlog.
• Sprint Backlog: at the beginning of each sprint, the development
team selects a set of items from the product backlog to work on
during that sprint.
• Increment: An increment is the sum of all the product backlog
items completed during a sprint.
• It should be a potentially shippable product increment, even if it’s not
released.

35
 Scrum Ceremonies
• Sprint Planning: at the start of each sprint, the team conducts sprint
planning to select items from the product backlog and create a sprint
goal.
• Daily Standup: daily meetings, usually 15 minutes, where the team
members share progress, discuss obstacles, and plan their day.
• Sprint Review: at the end of each sprint, a review is held to
demonstrate the completed work to stakeholders and gather
feedback.
• Sprint Retrospective: a meeting held after the sprint review to
reflect on the sprint and identify areas for improvement.
36
 Benefits of Scrum
• Faster Time-to-Market: scrum’s iterative approach allows for
quicker delivery of valuable features and regular releases.
• Customer-Centric: scrum prioritizes customer needs, leading to
higher customer satisfaction and better product-market fit.
• Improved Collaboration: scrum promotes collaboration among
team members, stakeholders, and customers, leading to better
communication and shared understanding.

37
 What is Kanban?
• Kanban, a Japanese term meaning “visual card” or “billboard,” has
evolved into a powerful Agile framework that transcends its origins
in manufacturing and has found applications in software development,
project management, and beyond.
• In this section, we’ll explore the core principles of Kanban like
• Core Principles of kanban,
• Kanban board design,
• Key practices of Kanban, and real-world use cases to help you
harness the power of visualizing work for your projects.
.
38
What is Kanban?

39
 The Core Principles of Kanban
• Visualizing Work: kanban revolves around visual boards that
represent the workflow, allowing teams to see work items, their
status, and bottlenecks at a glance.
• Limiting Work in Progress (WIP): setting WIP limits for each stage
of the workflow prevents overloading and promotes a smooth,
sustainable pace of work.
• Managing Flow: Kanban encourages the continuous and smooth flow
of work items through the workflow, minimizing delays and
optimizing throughput.
• Making Process Policies Explicit: Clearly defining and documenting
workflow rules and policies helps ensure consistency and alignment.
40
 Kanban Board Design
• Columns: kanban boards typically consist of columns that represent
the stages of the workflow, from “To Do” to “Done.”
• Cards: work items are represented as cards, each with a description,
status, and possibly additional information.
• WIP Limits: WIP limits are set for each column to prevent
overloading and encourage focus on completing existing work before
starting new tasks.

41
 Key Kanban Practices
• Pull System: Work is pulled into the system only when there is
capacity, as opposed to being pushed in based on arbitrary schedules.
• Daily Standup: Teams may hold daily stand-up meetings to discuss
progress, potential issues, and adjustments to the workflow.
• Cycle Time and Lead Time: Analyzing cycle time (time to complete
a task) and lead time (time from request to completion) helps teams
identify bottlenecks and improve predictability.

42
 Benefits of Kanban
• Enhanced Visibility: Kanban boards provide real-time visibility
into work status, allowing for quick identification of blockers and
opportunities for improvement.
• Increased Flexibility: Kanban’s adaptability makes it suitable for
various industries and processes, from software development to
customer support.
• Continuous Improvement: Kanban fosters a culture of continuous
improvement by encouraging teams to regularly review and optimize
their workflows.
.
43
 What Is XP?
• Extreme Programming (XP) is a renowned Agile methodology that
goes beyond project management practices to elevate software
development to a whole new level of excellence.
• In this section, we’ll explore the core principles of XP like
• Core Values
• Key Practices of Extreme Programming
• Roles in Extreme Programming
• Benefits of Extreme Programming

44
What Is XP?

45
 Core Values of Extreme Programming
• Communication: XP promotes open and frequent communication
between team members, stakeholders, and customers to ensure
everyone is on the same page.
• Simplicity: XP encourages simplicity in design and code, advocating
for the “You Ain’t Gonna Need It” (YAGNI) principle to avoid
unnecessary complexity.
• Feedback: Rapid feedback is crucial in XP.
• Developers receive feedback through continuous integration, testing, and
customer involvement.
• Courage: XP teams are encouraged to take calculated risks and
address issues head-on, fostering a culture of continuous
46
improvement.
 Key Practices of Extreme Programming
• Pair Programming: developers work in pairs, with one writing code
while the other reviews it in real-time.
• This practice enhances code quality and knowledge sharing.
• Test-Driven Development (TDD): XP promotes writing automated
tests before writing the code itself, ensuring that the code meets
requirements and is maintainable.
• Continuous Integration: code changes are frequently integrated into
a shared repository, allowing for early error detection and reducing
integration issues.
• Small Releases: XP encourages frequent, small releases to deliver
valuable features to customers quickly and gather feedback.47
 Roles in Extreme Programming
• Customer: the customer is an active participant in XP, providing
requirements, prioritizing features, and participating in testing.
• Programmer: Programmers write code, perform testing, and
collaborate closely with customers and other team members.
• Coach: The XP coach provides guidance on XP practices and
ensures the team adheres to XP principles.
• Tracker: The tracker helps manage the project’s schedule, making
sure that work is progressing and that the team remains on track.

48
 Benefits of Extreme Programming
• High Software Quality: XP’s focus on engineering practices leads to
high-quality code and fewer defects.
• Customer Satisfaction: Regular customer involvement ensures that
the product aligns with customer needs and expectations.
• Faster Time-to-Market: Frequent releases enable quicker delivery
of valuable features and rapid response to changing requirements.
• Team Collaboration: Pair programming and open communication
foster strong teamwork and knowledge sharing.

49
 Lean
• Lean, a philosophy initially developed in manufacturing, has evolved
into a powerful framework for streamlining processes, eliminating
waste, and delivering value in various industries, including
software development and project management.
• Lean Project Management is a method for overseeing projects with a
focus on efficiency and resource optimization.
• Instead of just completing tasks, it prioritizes delivering value to
customers while minimizing waste
• In this comprehensive guide, we’ll explore the core principles of
Lean, its benefits, key practices.
50
The Core Principles of Lean

51
 The Core Principles of Lean
• Identify Value: Lean begins by identifying what adds value from the
customer’s perspective. Anything that doesn’t add value is considered
waste and should be minimized or eliminated.
• Value Stream: Value stream mapping helps visualize the end-to-end
process and identify areas where value can be added and waste reduced.
• Flow: Lean emphasizes the smooth flow of work or products through the
system, minimizing bottlenecks and delays.
• Pull: Work or production is pulled based on customer demand rather than
being pushed based on forecasts, reducing overproduction.
• Perfection: The pursuit of continuous improvement and perfection is a
fundamental Lean principle. 52
 Key Practices of Lean
• Kaizen: Kaizen represents the philosophy of continuous
improvement.
• Teams regularly review processes and seek small, incremental changes to
improve efficiency.
• 5S: The 5S method focuses on organizing the workplace for
efficiency and effectiveness, involving steps like sorting, setting in
order, shining, standardizing, and sustaining.
• Just-in-Time (JIT): JIT manufacturing or production aims to deliver
the right product, in the right quantity, at the right time, minimizing
inventory and waste.
• Andon: Andon systems use visual cues to signal problems or
53
anomalies in real-time, enabling immediate corrective action.
 Benefits of Lean
• Reduced Waste: Lean practices help identify and eliminate various
forms of waste, such as overproduction, defects, and unnecessary
inventory.
• Improved Efficiency: By streamlining processes and optimizing
workflows, Lean leads to greater efficiency and resource utilization.
• Enhanced Quality: Reducing defects and improving processes
inherently result in higher product or service quality.
• Customer Focus: Lean encourages a customer-centric approach,
ensuring that value is delivered according to customer needs and
preferences.
54
 Agile Frameworks
Framework Core Focus Team Structure Workflow Best Suited for Challenges

Iterative Defined roles: Scrum Can feel rigid in

Sprint-based Teams with clear goals
Scrum development, Master, Product Owner, dynamic
(2-4 weeks) and stable project scope
time-boxed sprints Development Team environments

Continuous Teams needing Risk of undefined

Continuous
Kanban delivery, visual No predefined roles flexibility, support deadlines without
flow
management teams control

Requires
Large enterprises
Efficiency, waste Continuous continuous
Lean Varies (often flexible) focused on eliminating
elimination improvement evaluation of
inefficiencies
processes

Continuous
XP (Extreme Software teams Overhead for non-
Code quality, Technical roles: releases,
Programming prioritizing quality and technical
frequent releases Developers, Testers TDD, pair
) frequent updates environments
programming 55
Hybrid Project
Management
Waterfall methodology

57
Hybrid methodology

58
Hybrid methodology

59
 Hybrid methodology
• Hybrid project management methodology is a combination of two
different methodologies, primarily Agile and Waterfall.
• We can also combine Scrum and Kanban or Agile and DevOps or
other methodologies.
• But when it comes to the traditional definition of hybrid project
management, experts refer to combining Agile with Waterfall.

60
 Scramban
• Scrumban is the application of Kanban systems in a Scrum context.
• Scrumban project management, the inherent capabilities of Scrum are
improved and amplified.
• Layering the Kanban method alongside Scrum, though, brings some
new capabilities and perspectives into the spotlight.
• The result is a simple-to-use, flexible, and efficient Agile framework
that can be easily implemented at any organizational level.
• Still, it’s important to understand the main characteristics of both
Scrum and Kanban first to fully grasp Scrumban.

61
Scramban

62
 Six sigma methodology
• Agile Six Sigma is not a single methodology but a combined
approach that uses the structured, data-driven problem-solving of
Six Sigma within the flexible, iterative framework of Agile.
• This hybrid strategy allows organizations to achieve both the process-
improvement rigor of Six Sigma, often using the DMAIC cycle, and
the adaptability, rapid delivery, and customer focus of Agile,
especially in areas like software development.

63
Six sigma methodology

64
 Traditional vs Agile vs Hybrid
Feature Traditional Agile Hybrid
Initial planning but not strictly fixed.
Planning Upfront Ongoing
Room for changes
Blend of sequential,
Flow Linear and sequential Incremental and iterative
overlapping, iterative
Deliverables Fixed Changing Fixed with space for improvement
Some upfront idea with space for
Timelines and costs Upfront fixed Ongoing calculations
changes
Quite easy as you are working in
Change management Difficult, disrupts the flow Better than waterfall
short cycles
Throughout the development
End-user feedback After the big launch Throughout the development process
process
Heavily during the planning phase and
Client collaboration Throughout the project Blend of both
launch
Well-defined fixed requirements, stable Evolving requirements, fast-paced Projects with some defined elements and
Project types
market environment market environment room for change
Testing After the development phase After every sprint After every sprint
65
Team collaboration Within the department Cross department collaboration Both
Thank you!!!!!

Q&A