The document discusses some common pitfalls that can occur when using a waterfall project management methodology. It outlines issues like using the wrong methodology, creating an inaccurate work breakdown structure, underestimating tasks, and improperly tracking project status. Specifically, it notes that waterfall does not actually exist in pure form and that mixing iterative elements can help address some of its weaknesses by allowing for more flexibility over time. The key is to select the right processes and tools for the project and not be afraid to modify waterfall to fit each unique situation.
5. What is Scrum, What is Waterfall?
▪Scrum
–Elaborative requirements
–Fixed date
–Project Plan Projection
–Estimation: Story Points
▪Waterfall
–Detailed spec upfront
–Fixed scope, date, budget, quality
–Project Plan Commitment
–Estimation: Hours
6. Project Tracking
▪Scrum
–Input
▪Product Backlog (story points)
–Metrics:
▪Velocity (story/sprint)
▪# of Sprints Left
▪Waterfall
–Input
▪Planned Value (PV)
▪Earned Value (EV)
▪Actual Cost (AC)
–Metrics:
▪SPI=EV / PV
▪CPI=EV / AC
7. EVM
Task
Original Estimate (PV)
Time Spent (AC)
Remaining Estimate
Status
Earned Value (EV)
CPI
Task-1
10
20
0
Complete
10
50%
Task-2
10
5
4
In Progress
Task-3
10
5
15
In Progress
Task-4
10
10
1
In Progress
Task-5
10
5
Complete
10
200%
Task-6
10
5
Complete
10
200%
Task-7
10
10
Not Started
Task-8
10
20
Not Started
Total
80
50
50
30
60%
8. Waterfall Project Tracking
Category
Metric
Original Plan
Current
Scope
Dev Estimate (man-month)
20.53
20.53
Dev Estimate (man-days)
410.60
410.60
Dev Change Orders (man-days)
-
210.15
Dev Revised Estimate (man-days)
410.60
620.75
Dev Remaining Work (man-days)
410.60
85.00
Dev Work Complete (man-days)
-
535.75
Dev % Complete
86%
Dev Time Spent (man-days)
-
540.13
Total Team Time Spent (man-days)
1,011.63
Schedule/Time
Project Start Date
10/22/2012
10/22/2012
Project Duration (months)
3.93
5.95
Planned Dev Delivery Date
2/17/2013
4/18/2013
Planned Project Acceptance
3/3/2013
5/2/2013
Actual Dev Delivery Date
2/17/2013
12/15/2014
Actual Project Acceptance
3/3/2013
12/29/2014
Budget/Cost
Budget per month -dedicated team ($)
$ 41,700.00
$ 41,700.00
Total Team Budget per month ($)
$ 47,200.00
$ 47,200.00
Total Project Budget ($)
$ 185,729.20
$ 185,729.20
Change Orders ($)
$ -
$ 95,057.85
Revised Budget ($)
$ 185,729.20
$ 280,787.05
Budget Spent ($)
$ 226,538.40
Budget Left ($)
$ 54,248.65
Budget Needed ($)
$ 60,475.00
9. Waterfall Project Tracking
Category
Metric
Original Plan
Current
Scope
Dev Estimate (man-month)
20.53
20.53
Dev Estimate (man-days)
410.60
410.60
Dev Change Orders (man-days)
-
210.15
Dev Revised Estimate (man-days)
410.60
620.75
Dev Remaining Work (man-days)
410.60
85.00
Dev Work Complete (man-days)
-
535.75
Dev % Complete
86%
Dev Time Spent (man-days)
-
540.13
Total Team Time Spent (man-days)
1,011.63
Schedule/Time
Project Start Date
10/22/2012
10/22/2012
Project Duration (months)
3.93
5.95
Project %
Planned Dev Delivery Date
2/17/2013
4/18/2013
Planned Project Acceptance
3/3/2013
5/2/2013
Actual Dev Delivery Date
2/17/2013
12/15/2014
Actual Project Acceptance
3/3/2013
12/29/2014
Budget/Cost
Budget per month -dedicated team ($)
$ 41,700.00
$ 41,700.00
Budget per month -Architect, UI/UX, VMs ($)
$ 5,500.00
$ 5,500.00
Total Team Budget per month ($)
$ 47,200.00
$ 47,200.00
Total Project Budget ($)
$ 185,729.20
$ 185,729.20
Change Orders ($)
$ -
$ 95,057.85
Revised Budget ($)
$ 185,729.20
$ 280,787.05
Budget Spent ($)
$ 226,538.40
Budget Left ($)
$ 54,248.65
Budget Needed ($)
$ 60,475.00
Category
Metric
Original Plan
Current
Scope
Dev Estimate (man-month)
20.53
20.53
Dev Estimate (man-days)
410.60
410.60
Dev Change Orders (man-days)
-
210.15
Dev Revised Estimate (man-days)
410.60
620.75
Dev Remaining Work (man-days)
410.60
85.00
Dev Work Complete (man-days)
-
535.75
Dev % Complete
86%
Dev Time Spent (man-days)
-
540.13
Total Team Time Spent (man-days)
1,011.63
Schedule/Time
Project Start Date
10/22/2012
10/22/2012
Project Duration (months)
3.93
5.95
Project %
Planned Dev Delivery Date
2/17/2013
4/18/2013
Planned Project Acceptance
3/3/2013
5/2/2013
Actual Dev Delivery Date
2/17/2013
12/15/2014
Actual Project Acceptance
3/3/2013
12/29/2014
Budget/Cost
Budget per month -dedicated team ($)
$ 41,700.00
$ 41,700.00
Budget per month -Architect, UI/UX, VMs ($)
$ 5,500.00
$ 5,500.00
Total Team Budget per month ($)
$ 47,200.00
$ 47,200.00
Total Project Budget ($)
$ 185,729.20
$ 185,729.20
Change Orders ($)
$ -
$ 95,057.85
Revised Budget ($)
$ 185,729.20
$ 280,787.05
Budget Spent ($)
$ 226,538.40
Budget Left ($)
$ 54,248.65
Budget Needed ($)
$ 60,475.00
Category
Metric
Original Plan
Current
Scope
Dev Estimate (man-month)
20.53
20.53
Dev Estimate (man-days)
410.60
410.60
Dev Change Orders (man-days)
-
210.15
Dev Revised Estimate (man-days)
410.60
620.75
Dev Remaining Work (man-days)
410.60
85.00
Dev Work Complete (man-days)
-
535.75
Dev % Complete
86%
Dev Time Spent (man-days)
-
540.13
Total Team Time Spent (man-days)
1,011.63
Schedule/Time
Project Start Date
10/22/2012
10/22/2012
Project Duration (months)
3.93
5.95
Project %
Planned Dev Delivery Date
2/17/2013
4/18/2013
Planned Project Acceptance
3/3/2013
5/2/2013
Actual Dev Delivery Date
2/17/2013
12/15/2014
Actual Project Acceptance
3/3/2013
12/29/2014
Budget/Cost
Budget per month -dedicated team ($)
$ 41,700.00
$ 41,700.00
Budget per month -Architect, UI/UX, VMs ($)
$ 5,500.00
$ 5,500.00
Total Team Budget per month ($)
$ 47,200.00
$ 47,200.00
Total Project Budget ($)
$ 185,729.20
$ 185,729.20
Change Orders ($)
$ -
$ 95,057.85
Revised Budget ($)
$ 185,729.20
$ 280,787.05
Budget Spent ($)
$ 226,538.40
Budget Left ($)
$ 54,248.65
Budget Needed ($)
$ 60,475.00
Dev
QA
UI/UX, SA
10. Hint #1: Modified Waterfall
RolePhase-1Phase-2Phase-3Phase-4Phase-5Phase-6Phase-7Phase-8Phase-9Phase-10Phase-11Phase-12RMSADevDevDevDev QAQARolePhase-1Phase-2Phase-3Phase-4Phase-5Phase-6Phase-7Phase-8Phase-9Phase-10Phase-11Phase-12RMSADevDevDevDev QAQA
23. Communication & Reserve
▪Dev coding estimate = 40 days. What will be devschedule (in months) for 1 dev?
–5 months
–6.24 months
–6.86 months
Group
Name
% of Efforts
Engineering
Unit testing
20%
Engineering
Defect fixing & Code review
35%
Engineering
Development testing
10%
Engineering
Integration testing
0%
Engineering
Automated testing
0%
Engineering
Acceptance testing
20%
Engineering
Configuration Management & CI
5%
Engineering
Technical documentation
5%
Engineering
Deployment
5%
Management
Meetings & Communication
20%
Management
Contingency Reserve
30%
Total
150%
24. The Right Calc…
Group
Name
% of Efforts
Engineering
Unit testing
20%
Engineering
Defect fixing & Code review
35%
Engineering
Development testing
10%
Engineering
Integration testing
0%
Engineering
Automated testing
0%
Engineering
Acceptance testing
20%
Engineering
Configuration Management & CI
5%
Engineering
Technical documentation
5%
Engineering
Deployment
5%
Total
100%
2.00
Group
Name
% of Efforts
Management
Meetings & Communication
20%
Total
20%
1.20
Group
Name
% of Efforts
Management
Contingency RESERVE
30%
Total
30%
1.30
3.12
3.12
25. Even Better…
Group
Name
% of Efforts
Engineering
Unit testing
20%
Engineering
Defect fixing & Code review
35%
Engineering
Development testing
10%
Engineering
Integration testing
0%
Engineering
Automated testing
0%
Engineering
Acceptance testing
20%
Engineering
Configuration Management & CI
5%
Engineering
Technical documentation
5%
Engineering
Deployment
5%
Total
100%
2.00
Group
Name
% of Efforts
Management
Meetings & Communication
20%
Total
20%
1.20
Group
Name
% of Efforts
Management
Contingency RESERVE
30%
Total
30%
1.30
3.12
3.12
Vacations
10%
3.432
26. Wrong Tracking
Too Complex or No Workflow
Remaining Estimate
Time Spent
Excel over MS Project or JIRA
Status1Status2AnalysisOpenAnalysis In ProgressIn ProgressBA In ProgressClosedClient ApprovalIn ProgressClosed (Completed)ClosedClosed (Duplicate)ClosedClosed (Resolved: By Design)ClosedClosed (Resolved: Duplicate)ClosedClosed (Resolved: Fixed)ClosedClosed (Resolved: Implemented)ClosedClosed (Resolved: Not Reproducible)ClosedClosed (Resolved: Verified)ClosedClosed (Resolved: Won't Fix)ClosedClosed (Resolved: Won't Implement)ClosedClosed (Won't Implement)ClosedDeploymentClosedDevelopmentIn ProgressDevelopment In ProgressIn ProgressOn HoldIn ProgressQA In ProgressClosedQueuedOpenQueued for AnalysisOpenQueued For BAOpenQueued For DevelopmentOpenQueued for QAClosedQueued For ReviewIn ProgressQueued for TestingClosedReady for DB ReviewClosedReady For DeploymentClosedReady to PushClosedReady to UATClosedResolved (Completed)ClosedResolved (Deployed)ClosedResolved (Duplicate)ClosedResolved (Won't Implement)ClosedResolved: By DesignClosedResolved: DuplicateClosedResolved: FixedClosedResolved: ImplementedClosedResolved: Not ReproducibleClosedResolved: VerifiedClosedResolved: Won't FixClosedResolved: Won't ImplementClosedTestingClosedWaiting on ResponseIn Progress
27. Summary
There is no one good tool fits all cases
Waterfall does not exist
Do not be afraid of Waterfall
Iterative & Evolutionary Waterfall
Keep it simple
Mix it all