Planning Value S T S Cg
You thought I never th ht h VS
You thought earning value was
just a joke.
thought he would look
at that chart
Earned ValueEarned Value
Leslie (Les) DupaixUSAF Software
Technology Support CenterTechnology Support [email protected]
(801) 775-2064DSN 775 2064
Les Dupaix - 1Earned Value
DSN: 775-2064
Report Documentation Page Form ApprovedOMB No. 0704-0188
Public reporting burden for the collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering andmaintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information,including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, ArlingtonVA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to a penalty for failing to comply with a collection of information if itdoes not display a currently valid OMB control number.
1. REPORT DATE MAY 2011 2. REPORT TYPE
3. DATES COVERED 00-00-2011 to 00-00-2011
4. TITLE AND SUBTITLE Planning Value vs Earned Value
5a. CONTRACT NUMBER
5b. GRANT NUMBER
5c. PROGRAM ELEMENT NUMBER
6. AUTHOR(S) 5d. PROJECT NUMBER
5e. TASK NUMBER
5f. WORK UNIT NUMBER
7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) USAF Software Technology Support Center,Hill AFB,UT,84056
8. PERFORMING ORGANIZATIONREPORT NUMBER
9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSOR/MONITOR’S ACRONYM(S)
11. SPONSOR/MONITOR’S REPORT NUMBER(S)
12. DISTRIBUTION/AVAILABILITY STATEMENT Approved for public release; distribution unlimited
13. SUPPLEMENTARY NOTES Presented at the 23rd Systems and Software Technology Conference (SSTC), 16-19 May 2011, Salt LakeCity, UT.
14. ABSTRACT
15. SUBJECT TERMS
16. SECURITY CLASSIFICATION OF: 17. LIMITATION OF ABSTRACT Same as
Report (SAR)
18. NUMBEROF PAGES
26
19a. NAME OFRESPONSIBLE PERSON
a. REPORT unclassified
b. ABSTRACT unclassified
c. THIS PAGE unclassified
Standard Form 298 (Rev. 8-98) Prescribed by ANSI Std Z39-18
TopicsLif lLifecycles
DevelopmentDevelopment
Planning Value
Stones to Pebbles
Pebble Values
Earning ValueEarning Value
Communication
Les Dupaix - 2Earned Value
Get a Life(cycle) If you don’t have a If you don t have a life cycle, you don’t know
hA Need Finished
System– Where you are– Where you are going
System
F ilSuccess
Requirements System TestFailures
Success
High-Level Design Integration TestFailures
Success
Low-level Design Unit TestFailuresSuccess
Code
Les Dupaix - 3Earned Value
Lifecycles Strengths and Lifecycles Strengths and Weaknesses
Capability Pure Code Spiral Modified PrototypeCapability PureWaterfall
Code-and - Fix
Spiral ModifiedWaterfall
Prototype
Poorly understoodrequirements Poor Poor Excellent Fair to
Excellent Excellent
Poor Architecture Poor Poor Excellent Fair toExcellent Poor to Fair
Highly Reliable System Excellent Poor Excellent Excellent Fair
System Growth Built in Excellent Poor to Fair Excellent Excellent ExcellentSys e G ow u Excellent Poor to Fair Excellent Excellent Excellent
Risk Management Poor Poor Excellent Fair Fair
Predefined Schedule Fair Poor Fair Fair Poor
Midcourse Correction Poor unknown Fair Fair ExcellentCustomer Visibility Poor Fair Excellent Fair Excellent
Management Visibility Fair Poor Excellent Fair to FairFair Poor Excellent Excellent Fair
Low Management anddeveloper skill level Fair Excellent Poor Poor to Fair Poor
Low Overhead Poor Excellent Fair Excellent Fair
Les Dupaix - 4Earned ValueRapid Development (McConnell, 96)
The Development TriangleYou can control only two sides of a triangle; The third side MUST bea “free variable”.
Product(Functionality + Quality)
Schedule(Functionality Quality)
CostLes Dupaix - 5Earned Value
Cost
Change Possibilityg y4x
st
2x
rt\
Cos 1.5x
1.25xX8x
Eff
or
.8x.67x
.5x
.25x
Phase
RFI RFPContract Award
Req. Review
Design Review
Code Review
Test Delivery
Les Dupaix - 6Earned Value
PhaseCost Models for Future Life Cycle Processes: COCOMO 2.0 (Boehm, 1995)
Planning ValuePlanning ValuePlan a value for each h d t kphase and task.
All phases sum to the total projecttotal project.All tasks sum to each phase.pThe planned value for each task is the percent of the alue percent of the value for phase.Simple measures are Simple measures are the best and easiest.
Les Dupaix - 7Earned Value
Plan Example
Task Task Plan Cum Task #
Task Description
Plan Hours
Cum Hours
1 Presentation Plan
1 1Plan
2 Presentation Outline
2 3
3 Create 12 153 Create Presentation
12 15
4 Review Presentation
3 18
5 Present 1 19
6 Postmortem 1 20
Les Dupaix - 8Earned Value
Plan Value Example
Task Task Plan Cum Plan Cum Task #
Task Description
Plan Hours
Cum Hours
Plan Value
Cum Value
1 Presentation Plan
1 1 5 5Plan
2 Presentation Outline
2 3 10 15
3 Create 12 15 60 753 Create Presentation
12 15 60 75
4 Review Presentation
3 18 15 90
5 Present 1 19 5 95
6 Postmortem 1 20 5 100
Les Dupaix - 9Earned Value
Plan Value Example ith S h d l with Schedule Task
#Task
DescriptionPlan
HoursCum Hours
Week Plan
Plan Value
Cum Value
1 Presentation Plan
1 1 1 5 5
2 Presentation Outline
2 3 1 10 15Outline
3 Create Presentation
12 15 3 60 75
4 Review 3 18 4 15 904 Review Presentation
3 18 4 15 90
5 Present 1 19 5 5 95
6 Postmortem 1 20 5 5 100
Les Dupaix - 10Earned Value
Planning Milestones gA Need Finished
SystemWhat % of the whole
is each phase? Systemp
Requirements System TestAre we planning to
re-plan at the
High-Level Design Integration Testcorrect times?
Low-level Design Unit Test
Code
Les Dupaix - 11Earned Value
Isn’t this the same guy who made us attend
the “Planning I’ll go gather the
i t d the “Planning Seminar” last week?
requirements and come up with a
design. The rest of you START you START CODING!!
Les Dupaix - 12Earned Value
Slicing Milestones to Inch PebblesInch Pebbles
Separate Milestones Separate Milestones into Measure-able individual task that individual task that can be accomplished
– Review document – Identify interfaces– Write test plan
Id tif i t t Identify inputs to and outputs from each task (including Critical Path)
Les Dupaix - 13Earned Value
each task (including Critical Path)
Planning Milestones If you d ’t
gMore detailed
Plan or Re-plan
don’t know enough to Plan or Re plan enough to plan well, plan often
Entire Plan
plan often.
Entire PlanSystem Delivery
Know Measure-ableMilestones
Know the
critical Milestones critical path.
Les Dupaix - 14Earned Value
Example - Iterative ApproachPhase I 35%Phase I 35%
– Planning 7.5%» Entire Project 5%» Phase 2.5%
R i t 25%And during this
phase – Requirements 25%– Design 25%– Code 30%– Test 12.5%
phase ...
Phase II 30%– Planning 2.5%– Requirements 25%
Design 25%– Design 25%– Code 30%– Test 12.5%
Phase III 30%– Planning 2.5%– Requirements 25%– Design 25%– Code 30%Code 30%– Test 12.5%
System Test 5%
Les Dupaix - 15Earned Value
Plan Value Example
Task Task Plan Cum Plan Cum
Phase ITask
#Task
DescriptionPlan
HoursCum Hours
Plan Value
Cum Value
1 Project Plan 200 200 5 5
2 Phase Plan 100 300 2.5 7.5
i 5 5 53 Requirements 1000 1500 25 32.5
4 Design 1000 2500 25 57.5
5 Code 1200 3700 30 87.5
6 Test 500 4200 12.5 1006 Test 500 4200 12.5 100
Les Dupaix - 16Earned Value
Detailed Planned Value Example Example
T k T k Pl C Pl C
Project Plan (part of Phase I)Task
#Task
DescriptionPlan
HoursCum Hours
Plan Value
Cum Value
1Identify
Resources for 8 8 4 41 Resources for each Phase
8 8 4 4
2 Identify Requirements 78 86 39 43q
3Match
Requirements to Phases
20 106 10 53Including Critical
Path4 Identify Risk
Areas 20 126 15 63
5 System Test Plan 50 176 25 88
Path
Plan6 Review 20 196 10 98
7 Postmortem 4 200 2 100
Les Dupaix - 17Earned Value
Duration ChartsGantt (Bar) Chart
Si lSimpleCan show dependenciesTracking planned vs
Activity A
Activity B
Tracking planned vs actual
Milestone Time
Activity C
Activity D Milestone
Markers showing progressDoesn’t show consumption of resources
Activity A
Activity B
Normally part of Gantt chartZero duration Time
Activity C
Activity D
Les Dupaix - 18Earned Value
Zero duration
Critical Path Method (CPM)( )Network analysis technique– Used to predict project duration by
analyzing path with least amount of float– Early dates: Forward pass calculation– Late dates: Backward pass calculationCritical path– The series of activities determining the earliest
completioncompletion– Usually defined as activities with float < or = a
specified value (often zero)
Les Dupaix - 19Earned Value
Critical Path Method
Critical PathCritical Path
Gantt Chart is common methodof display. Can also be a pert chart.
Les Dupaix - 20Earned Value
Rebuilding Milestones from Inch Pebbles
And if Charlie from Inch Pebbles
To make a schedule you need 3 things
does not get hurt again we
you need 3 things– the estimated direct project
hours
...
– a calendar of available direct hours
– the order in which the tasks will be done
You then need toYou then need to– estimate the hours needed
for each task– spread these hours over the
calendar of available hours– Make sure you check and
h k C i i l P h
Les Dupaix - 21Earned Value
recheck Critical Path
Earning ValuegNo schedule
blYou earn value when you
problemsthat I can see!
ycomplete a task
No partial credit
Les Dupaix - 22Earned Value
Earned Value ExampleP j t Pl ( t f Ph I)
Task Task i i
Plan Cum Plan l
Cum Plan Plan
k Week HoursActual Hours
Cum Earned
Project Plan (part of Phase I)
# Description Hours Hours Value Plan Value Week Week Hours Hours
CumEarned Value
1Identify
Resources for each Phase
8 8 4 4 1 1 7 7 4
2 Identify Requirements 78 86 39 43 4 6 96 103 43
3Match
Requirements 20 106 10 53 5 7 24 127 533 Requirements to Phases
20 106 10 53 5 7 24 127 53
4 Identify Risk Areas 20 126 10 63 6
5 System Test Plan 50 176 25 88 8
6 Review 20 196 10 98 9
7 Postmortem 4 200 2 100 9
Only get credit on the week completed
Les Dupaix - 23Earned Value
the week completed
Status Reporting708090
100p g
Status is earned 010203040506070
Status is earned compared to plannedWhen earned and plan
1 2 3 4 5 6 7 8 9
Actual Planned
When earned and plan get too far off balance Re-PlanRe PlanRemember life happenshappensYou probably never can catch up
Les Dupaix - 24Earned Value
Communication Communicating with a Software Engineers is only slightly less difficult than Large-scale software
requires many
slightly less difficult than communicating with the
DEAD.q ypeople - and without a process, there is p ,little (if any) effective communication. Earned value versus Earned value versus planned value can be a simple sanity be a simple sanity check
Les Dupaix - 25Earned Value