ASQ Agile v Waterfall

Only available on StudyMode
  • Download(s): 103
  • Published: October 6, 2013
Read full document
Text Preview
Waterfall vs. Agile Project Management
Lisa Sieverts, PMP, PMI-ACP

Phil Ailes, PMI-ACP

Waterfall vs. Agile Project Management
Agenda

• 
• 
• 

• 

What is a Project
Overview
–  Traditional Project Management
–  Agile Project Management
The Differences
–  Product Life Cycle
–  The Teams
–  Requirements
–  WBS/Product Backlog
–  Schedule
–  Risk
–  Quality
Q&A

2
©Lisa Sieverts & Phil Ailes

1

Waterfall vs. Agile Project Management
What is a Project?

•  Temporary
•  Goal
•  Constrained
3
©Lisa Sieverts & Phil Ailes

Waterfall vs. Agile Project Management
What makes projects special?

•  Projects are

characterized by
uncertainty

4
©Lisa Sieverts & Phil Ailes

2

Waterfall vs. Agile Project Management
Traditional Waterfall Projects

•  Traditional Waterfall Projects
–  Dates from the end of WWII
–  Grew out of Defense industry
–  Based on Deming Cycle of Plan-Do-Check-Act
–  Emphasizes heavy up-front analysis
–  Lots of documentation
–  PMBOK versions 1-4
©Lisa Sieverts & Phil Ailes

Waterfall vs. Agile Project Management
Traditional Waterfall Project
High
Medium
Requirements
Low
Optional
High
Design

Medium
Low
Optional
High
Development Medium
Low
Optional
High
Testing

Medium
Low
Optional
High
Deploy

Medium
Low
Optional

6

©Lisa Sieverts & Phil Ailes

3

Waterfall vs. Agile Project Management
Waterfall - Advantages

7
©Lisa Sieverts & Phil Ailes

Waterfall vs. Agile Project Management
Waterfall - Advantages

•  Established Processes- Project Management Body of
Knowledge

•  Management Controls
•  (Apparent) Predictability
•  Great for low uncertainty/high dependency projects
–  Construction
–  Update of established product
–  Maintenance projects
8
©Lisa Sieverts & Phil Ailes

4

Waterfall vs. Agile Project Management
Waterfall - Disadvantages

9
©Lisa Sieverts & Phil Ailes

Waterfall vs. Agile Project Management
Waterfall - Disadvantages

•  Sometimes is more about the Process than the
Product

•  Keeps the customer at bay – by the time they see the end results it may be too late

•  Project teams often become rigid and resistant to
change: “Those darn users keep changing their
minds.”

•  Long product development time

10
©Lisa Sieverts & Phil Ailes

5

Waterfall vs. Agile Project Management
Agile Project Management

•  The Agile Way
–  Experiments in the 1990s
–  Values self-organizing teams
–  No formal “project
management”

–  Iterative approach
–  Flexible

©Lisa Sieverts & Phil Ailes

Waterfall vs. Agile Project Management
Manifesto

• 

The Agile Manifesto for Software Development

–  “We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:

•  Individuals and interactions over processes and tools •  Working software over comprehensive documentation
•  Customer collaboration over contract negotiation
•  Responding to change over following a plan
–  That is, while there is value in the items on the right, we value the items on the left more.”

12
©Lisa Sieverts & Phil Ailes

6

Waterfall vs. Agile Project Management
The Agile Way

Sprints – High Priority Features

Integrate

Test

Sprints – Low Priority Features

Integrate

Test

Integrate

Test

Design
Test

Test
Develop

Integrate

Test

Demo & Feedback

Develop

Requirements

Test

Test

Develop

Sprints – Optional Priority Features

Demo & Feedback

Requirements

Design
Test

Design
Test

Demo & Feedback

Develop

Requirements

Test

Demo & Feedback

Requirements

Design
Test

Sprints – Medium Priority Features

13
©Lisa Sieverts & Phil Ailes

Waterfall vs. Agile Project Management
Agile - Advantages

14
©Lisa Sieverts & Phil Ailes

7

Waterfall vs. Agile Project Management
Agile - Advantages

•  Shorter...
tracking img