Download presentation
Presentation is loading. Please wait.
Published byJulia Skinner Modified over 9 years ago
1
Copyright 1995-2009, Dennis J. Frailey CSE7315 – Software Project Management CSE7315 M30 - Version 9.01 SMU CSE 7315 Planning and Managing a Software Project Module 30 Managing with Earned Value / Measurement Issues
2
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 2 Objectives of This Module To discuss how to manage a project using earned value measures To discuss some measurement issues
3
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 3 Managing with Earned Value
4
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 4 BCWS or PV (Budgeted Cost of Work Scheduled) The amount of effort you had planned to expend (i.e., the amount you budgeted) “How much work should have been done” BCWS
5
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 5 BCWP or EV (Budgeted Cost of Work Performed) The value produced for the effort you have actually expended What you have earned “How much work was actually done” BCWP
6
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 6 ACWP or AV (Actual Cost of Work Performed) The amount of money you have spent so far The “actual” cost “What did your work cost?” ACWP
7
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 7 What Can We Tell About the Schedule From These Three Numbers? SV - Schedule Variance SV = BCWP - BCWS SPI - Schedule Performance Index SPI = BCWP / BCWS Negative means behind schedule Less than 1 means behind schedule
8
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 8 SPI Indicates Whether You are Ahead of or Behind Schedule Ahead of Schedule Behind Schedule
9
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 9 What Can We Tell About the Cost From These Three Numbers? CV - Cost Variance CV = BCWP - ACWP CPI - Cost Performance Index CPI = BCWP / ACWP Negative means over budget Less than 1 means over budget
10
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 10 CPI Indicates Whether You are Under or Over Budget Under Budget Over Budget
11
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 11 Variances on Graph Schedule Variance Cost Variance
12
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 12 Three Useful Numbers BAC - Budget at Completion –The total budget for the project –BCWS at project completion (BCWS BAC ) SCHED - Schedule for the project –The total number of weeks or months or years planned for the project EAC - Estimate at Completion –Your estimate of actual project cost (ACWP EAC )
13
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 13 EAC - Your Estimate of the Final Cost This is your estimate of the final project cost, based on your insight on the project. –Perhaps you know that performance to date is higher or lower than is likely in the future This is a judged value
14
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 14 Independently Estimated Cost At Completion IEAC - Independent estimate of the project cost at completion –The projected cost of the project, based on performance so far IEAC = BAC / CPI –Note that this may be different from your estimate. This value is based on facts
15
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 15 How Much Over or Under? VAC - Variance at Completion VAC = BAC - IEAC or VAC = BAC - EAC Negative means over budget by this much
16
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 16 Schedule At Completion ISAC - Independent Schedule at Completion –The projected schedule of the project ISAC = SCHED / SPI SVAC - Variance at Completion SVAC = SCHED - ISAC Negative means behind schedule by this much
17
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 17 Thus You Can Tell... How far behind or ahead of schedule you are How far over or under budget you are What your eventual schedule and cost are likely to be You also have an early warning of trouble that you can use to try to fix the underlying problems
18
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 18 A Handy Graph of SPI and CPI Indicates Your Overall Status SPI CPI
19
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 19 Reasons for Being Behind Schedule If you are also Under Budget –There is not enough work being done Not enough people People being used for other tasks If you are at or Over Budget –There is a productivity problem Underestimation of the effort Excessive “non-value-added” work
20
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 20 You Can Set Control Limits and Thresholds for Earned Value Just as you can for many other quantities Usually based on history from previous programs –Acceptable variation is established by the behavior of programs that did not get into trouble This is typically done by mature organizations with good historical data. At lower levels of maturity, you lack the data to set useful limits.
21
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 21 Control Limits on SPI Chart Upper Control Limit Lower Control Limit
22
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 22 What Are Your Chances of Meeting Your Budget? If CPI or SPI is outside of the control limits, it means you are under or over performing to a degree that means corrective action is necessary But also look at trends - they can indicate potential problems in the future
23
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 23 What If the Budget Changes? Sometimes projects adjust budgets and goals –In light of clear evidence that previous budgets & goals cannot be met –Or due to changes in goals or requirements –Or due to changes in commitments –Or due to changes in resources –… How does this effect earned value?
24
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 24 Responding to Budget Changes You can continue to track against the original plan, but show new estimates on the same graphs or You can “replan” –Re-compute BCWS and other values affected by the change and compute earned value against the new plan –This is recommended if the new budget is significantly different
25
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 25 What If You Are Asked to Recommend The Adjusted Budget? Suppose, in light of clear evidence that previous budgets & goals cannot be met, you are asked to estimate the likely cost and thus the recommended new budget? How do you know if your new estimate is enough? (next slide)
26
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 26 “To Complete” Performance Index Let BAC be your original budget and EAC be your estimate of actual cost Then TCPI = (BAC-BCWP) / (EAC-ACWP) (work left to do / money left to spend) This tells you how you must perform in order to meet your estimate (EAC)
27
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 27 Using TCPI (“To Complete” Performance Index) TCPI = (BAC-BCWP) / (EAC-ACWP) If TCPI is outside the control limits (i.e., not very close to 1.0), it indicates that, if you continue to perform as you have in the past, you are unlikely to meet the EAC estimate –So you must change the goal –Or take other corrective action
28
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 28 EAC or IEAC? You can compute TCPI using either the estimated or computed “estimate at completion”. IEAC assumes your past performance on the project is a reliable guide – generally recommended after 15-20% complete EAC assumes you have information that is more reliable than past performance
29
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 29 Summary Earned Value Can... … tell you your true status … give you an effective schedule / budget outlook … help you understand the reasons why if you are not meeting your plan If the estimates are developed by the workers, they are more likely to “buy in” to the results
30
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 30 Summary (continued) Various indices can be computed to tell you things about your project, such as: –Projected cost or schedule –Performance level required to meet a specific goal (original budget or revised budget)
31
Copyright 1995-2009, Dennis J. Frailey CSE7315 – Software Project Management CSE7315 M30 - Version 9.01 Measurement Issues
32
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 32 Measurement Issues Frequency Synchronization Updating estimates Margin Peak vs. average Units Interplay of resources
33
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 33 Frequency How Often to Measure Too often results in high cost, disruption of process Too seldom results in failure to see problems soon enough Frequency should depend on degree of risk and cost of measurement
34
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 34 Synchronization Getting the True Picture
35
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 35 Update Projections and Estimates
36
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 36 Margin A Frequently Misunderstood Term What does “leave 50% margin” mean? Code Margin 66 2/3 50 100 Code Margin
37
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 37 Peak vs. Average “Software must be able to handle 100 screens per minute” Peak? (Worst Case) Average over Some Interval? How Often to Measure?
38
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 38 Units Often Subject to Misinterpretation Memory Size: words, bytes, bits??? Program Execution Time: –Hours since shipped? {was it delivered?} –Hours since received by customer? {was it installed?} –Hours since installed? {was it used?} –CPU execution time since installed? CPU Time: cycles, instructions, MIPS, FLOPS, ? Beware of innocent misinterpretations
39
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 39 Interplay of Resources Few Things Happen in Isolation Sometimes, system resources interact with each other, giving misleading evidence of performance Memory Capacity: 80 cycles per micro- second CPU 50 MIPS I/O Channel 20 MIPS Display 40 MIPS CPU may run at only 20 MIPS because of memory saturation
40
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 40 Summary of Measurement 1) Know WHAT you are measuring - attributes, etc. 2) Know WHY you are measuring - goals, risks, etc. 3) Select wisely –Complete - something for each part of the process –Reasonable cost of collection –High information content –Minimal organizational disruption 4) Beware of incorrect interpretations 5) Beware of misuse “Nobody believes statistics anyway.” Adams, The Dilbert Principle “Nobody believes statistics anyway.” Adams, The Dilbert Principle
41
Copyright 1995-2009, Dennis J. Frailey CSE7315- Software Project Management CSE7315 M30 - Version 9.01 41 END OF MODULE 30
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.