20 USD/AUD | 15 EUR/GBP
THE MEASURABLE NEWS
The Quarterly Magazine of the College of Performance Management 2016.02
mycpm.org
INSIDE 07 17 25 31 Making EVM Work in Implementing Project On the Use of Empirical EVM and Agile THIS Agile Development Controls: Preparing for or Artificial Project Data Development Projects the Establishment of the Collaboration for a ISSUE Integrated (Cost and By Mario Vanhoucke Purpose By Ray W. Stratton Schedule) Performance Measurement Baseline By Matthew Strain
By Matthew T. Gonzales THE MEASURABLE NEWS
The Quarterly Magazine of the College of Performance Management 2016.02
2016 ISSUE 02 CONTENTS
05 In This Issue... Matthew Gonzalez
07 Making EVM Work in Agile Development Projects Ray W. Stratton, PMP, EVP
17 Implementing Project Controls: Preparing for the Establishment of the Integrated (Cost and Schedule) Performance Measurement Baseline Matthew T. Gonzales
25 On the Use of Empirical or Artificial Project Data Mario Vanhoucke
31 EVM and Agile Development Collaboration for a Purpose Matthew Strain
35 CPM Washington DC (CPMWDC) NEWS
36 CPM Tennessee Valley (CPMTV) Chapter Special Event – February 16, 2016 Norman Dean
37 CPM Tennessee Valley (CPMTV) Chapter Quarterly Meeting – March 1, 2016 Norman Dean mycpm.org 38 College of Performance Management Tennessee Valley (CPMTV) Chapter Meeting
39 Vendors/Services THE MEASURABLE NEWS IS AN OFFICIAL PUBLICATION OF THE THE COLLEGE OF THE MEASURABLE NEWS COLLEGE OF PERFORMANCE PERFORMANCE MANAGEMENT MANAGEMENT The Quarterly Magazine of the College of Performance Management EDITORIAL STAFF Publisher: College of Performance Management Story Editor: Peter Schwarz Design: id365 Design + Communications 2016.02 Communications VP: Lisa Wolf 2016 BOARD & STAFF EDITORIAL COPY PRESIDENT Wayne Abba Editorial contributions, photos, and miscellaneous 703-658-1815 • [email protected] inquiries should be addressed and sent to the editor at the College of Performance Management (CPM) headquarters. Please follow the author guidelines VICE PRESIDENT OF FINANCE posted on the CPM web site. Letters submitted to Buddy Everage the editor will be considered for publication unless 202-507-4372 • [email protected] the writer requests otherwise. Letters are subject to editing for style, accuracy, space, and propriety. All VICE PRESIDENT OF ADMINISTRATION letters must be signed, and initials will be used on Lauren Bone request only if you include your name. CPM reserves +44 (0) 7766 97 40 63 • [email protected] the right to refuse publication of any letter for any reason. We welcome articles relevant to project VICE PRESIDENT OF CONFERENCE & EVENTS management. The Measurable News does not pay for Susan Wood submissions. Articles published in The Measurable 850-585-4830 • [email protected] News remain the property of the authors. VICE PRESIDENT OF EDUCATION & CERTIFICATION ADVERTISING Bill Mathis Advertising inquiries, submissions, and payments 703-825-5588 • [email protected] (check or money order made payable to the College of Performance Management) should be sent to CPM VICE PRESIDENT OF RESEARCH & STANDARDS headquarters. Advertising rates are $1000 for inside Dale Gillam front or back cover (full-page ad only), $800 for other 703-431-6398 • [email protected] full-page ads, $500 for half-page ads, and $300 for quarter-page ads. Issue sponsorships are available at $2,500 per issue. Business card ads are available VICE PRESIDENT OF GLOBAL OUTREACH for $100 per issue (or free with full-page ad). Rates Kym Henderson are good from January 1, 2016 – December 31, 2016. 61-414-428-437 • [email protected] College of Performance Management reserves the mycpm.org right to refuse publication of any ad for any reason. VICE PRESIDENT OF COMMUNICATIONS Lisa Wolf SUBSCRIPTIONS 301-802-0627 • [email protected] All College of Performance Management publications are produced as a benefit for College of Performance PAST PRESIDENT Management members. All change of address or Gary W. Troop membership inquiries should be directed to: 310-365-3876 • [email protected] College of Performance Management 12100 Sunset Hills Road, Suite 130 EXECUTIVE DIRECTOR Reston, VA 20190 Don Kaiser Ph 703-370-7885 • Fx 703-370-1757 703-370-7885 • [email protected] www.mycpm.org
All articles and letters represent the view of the authors and not necessarily those of College of Performance Management. Advertising content does not signify endorsement by College of Performance Management. Please notify College of Performance Management for single copy or reproduction requests. Appropriate charges will apply.
© 2016 by the College of Performance Management. All rights reserved.
THE MEASURABLE NEWS 2016.02
IN THIS ISSUE... By Matthew Gonzalez
In this issue of The Measurable News we continue the Agile EVM conversation with an in-depth article on how to adapt the EVM system to accommodate non-traditional EVM tenets associated with Agile development. Another article provides updates on Agile and EVM guidance from PARCA. Also included in this issue is a brief overview of the artificial and empirical project data generated and collected by the researchers from the Operations Research and Scheduling (OR&S) group from Ghent University in Belgium. Moving from the erudite to the pragmatic, a ‘how-to’ article on setting up a successful performance measurement baseline walks the reader through all aspects of planning the successful PMB.
‘Making EVM Work in Agile Development Projects’ by Ray W. Stratton, provides a detailed look at how to plan and manage an Agile development project and still be EIA 748 compliant. In this article, the reader is challenged to look at some of the EVM hard and fast rules of a performance baseline that reflects a fixed scope of work and where completion of work that does not produce an SPI of 1.0. Mr. Stratton offers a detailed example on how the tenets of Agile can be planned and managed in a traditional EIA 748 construct and how to analyze the metrics. We are treated to an example of the adaptability of the EVM system to accommodate a different approach to managing work scope, while still providing valuable metrics that allow visibility into work-in-progress performance.
‘EVM and Agile Development Collaboration for a Purpose’, by Matthew Strain, provides some updates on the Agile conversation from a working group looking at how to apply agile methods to improve acquisitions. This informative article updates the reader on the white paper issued by PARCA, titled “Agile and Earned Value Management: A Program Manager’s Desk Guide” which focuses on recommended practices for planning, controlling, and forecasting agile software development projects. The release culminates a year’s worth of effort on the part of Government and industry participants.
‘We live in a world where the words “big data” have become the buzzwords to refer to the increasing importance of the availability of data and the powerful methodologies to analyze these huge amounts of data for improved decision making. The paper ‘On the Use of Empirical or Artificial Project Data' by Mario Vanhoucke, is a brief overview of the artificial and empirical project data generated and collected by the researchers from the Operations Research and Scheduling (OR&S) group from Ghent University in Belgium. Artificial data are generated by project network generators under a strict design to control both the network structure and the resource constraints, while the empirical project data are collected over a time horizon of multiple years, using a standardized collection and classification method.
‘Failing to prepare, is preparing to fail’. John Wooden. The article ‘Implementing Project Control: Preparing the Performance Measurement Baseline’, by M.T. Gonzales, offers the reader an anatomy of how to put together an integrated cost and schedule baseline in an EVM environment. The focus of the paper is preparing to succeed by looking at the planning phase as a discrete manageable effort with tangible products and developing a plan to lead a team of planners to successful completion of an integrated cost and schedule baseline.
The Quarterly Magazine of the College of Performance Management | mycpm.org 05 Succeed more. Drive project and portfolio management with Deltek’s PPM solutions.
Manage costs, forecasts and performance with Deltek Cost and earned value solutions. Build the most realistic project plans with Deltek schedule tools, and accurately evaluate and manage risk exposure with Deltek Risk.
» deltek.com/ppm
Attending EVM World 2016 in Naples, FL? Stop by booth #10 & 11 or join us during one of our sessions:
Wednesday, June 1 2:30 – 3:15 PM: The Project Management Easy Button 3:45 – 4:30 PM: Data Driven Metrics: Deltek Acumen & wInsight Analytics Thursday, June 2 2:30 – 3:15 PM: Embrace the Ghosts of Projects Past THE MEASURABLE NEWS 2016.02
MAKING EVM WORK IN AGILE DEVELOPMENT PROJECTS By Ray W. Stratton, PMP, EVP
How to make EVM work in agile development? That subject has been a major attendees’ interest at CPM’s EVM conferences (EVM World, IPMC, and IPMW) since spring 2012. Conference workshops and practice symposiums have presented various approaches in applying EVM concepts to agile development efforts while still meeting the guidelines of EIA 748. Why the challenge?
This article will review the challenges and propose a method to meet EIA 748 while applying EIA 748 principles and producing useful EVM data. Since this article was first written PARCA has released “Agile and Earned Value Management, A Program Manager’s Desk Guide”. The concepts presented in this article describe how to establish a Performance Measurement Baseline within a Control Account and are believed to be consistent with the PARCA guidance. The author is not aware of any regulatory or agency policy defining how EVM is to be implemented in agile development projects. The method illustrated in this article is how the author would apply EVM to an agile development with the intention of meeting EIA 748. Other methods may also meet the requirements of EIA 748 and the PARCA guidance. The example shown was presented at the fall 2015 IPMW to a packed room of over 100 attendees. This article’s intention is to share the concepts presented to a wider audience and those who could not attend the session.
BACKGROUND Why is it so hard to address agile development and EVM at the same time? The major challenge is rethinking the project’s key priority. Traditionally the scope (SOW) has been fixed as the priority of the project. The contractor is expected to meet and deliver all the scope. This leaves the cost and schedule sides of the “triple constraint” to be of lower priority. All three elements, scope, cost, and schedule cannot all be inflexible. In other words the message was “Deliver everything I want, and spend the time and budget needed to do so.” In implementing EVM the scope is therefore fixed and the cost and schedule performance metrics tell us what might be the final cost and completion date.
Here is a very simplified explanation why agile development is different from our traditional development above. Agile development allows for prioritization and assignment of requirements (features) to successive software releases (sprints) determined by the development team and stakeholders. The team is generally a fixed resource (fixed size) operating to a fixed budget. As development proceeds some of the requirements may need more resources than planned. When the fixed budget is exhausted the work stops. Some requirements may never be completed (think “bucket list”), but since the prioritization of features implemented involved the stakeholders, the most valuable requirements were delivered. Maximum utility was achieved for the time and budget spent. The cost is contained. Therefore the challenge in applying EVM is that all the scope may never be completed when the budget (or time/schedule) is exhausted. The project is done when the money is gone, not when the scope is completed.
That changes everything.
RETHINKING EVM Using agile development and using EVM requires some changes in how we think about EVM. Long standing “cultural rules” need to be revisited, not the EIA 748 guidelines, just the informal “cultural rules”. Table 1 shows how some common EVM expectations change in agile development where scope is not fixed, budget is.
The Quarterly Magazine of the College of Performance Management | mycpm.org 07 Traditional Development Agile Development Done means cumulative BCWP = BAC Done means cumulative ACWP = BAC Final cumulative BCWP equals final Final cumulative BCWP does not equal final cumulative BCWS cumulative BCWS Final SPI = 1 Final SPI ≠ 1
Table 1, Traditional Versus Agile EVM "rules"
None of the agile cultural rules conflict with EIA 748 guidelines. They are simply a consequence of realizing that not all scope will be completed. (Of course, if at the project’s end the scope is “adjusted” to match the actually completed work then the traditional rules will apply.)
EVM AND AGILE - MOVING TOWARD CONSENSUS Over time various papers, speakers, and concepts have been presented about applying EVM in agile development. There seems to be a consensus developing around concepts that appear to work in implementing EVM in agile development.
1. Do not base BCWS or BCWP on the periodic schedule of sprints or releases. They are fixed and will occur anyway, often in two to six weeks, fixed, uniform, periods. There will be no schedule variance likely or useful.
2. Stories (requirements) are not all equal. There are complex stories and simple stories requiring more or less effort to complete. “Story points” is a method to show the complexity of one story relative to another, however, no standard metric for a story point exists. Each sprint team will determine how to assign story points to stories. Generally a story with two story points may be twice as hard to complete as a story assigned one story point. (Story point values are often based upon Fibonacci series: 1, 2, 3, 5, 8, 13…)
3. Because each sprint team defines their story point there is no universal mapping of story points to staff hours or budget. A team’s story point unit value may simply be set by the simplest story within their assigned scope, with all other stories estimated effort relative to this story.
4. A sprint team has the capacity to complete a finite number of story points per sprint, and in total, based upon their skills, experience, staff size, budget, and other productivity factors. Story points therefore can, at any time, be the basis of comparing a planned percent of story points to be completed with the percent of story points actually completed. {Alternatively, stories may form the basis of determining BCWS and BCWP but all stories are not equal and therefore need to be weighted by their assigned story points (difficulty)}.
5. The number of story points planned and the number completed should be the basis of BCWS (BCWS = percent * BAC) and BCWP (BCWP = percent * BAC) since this represents accomplishment.
6. Sprint teams form the basis of control accounts because story point values are unique to each sprint team. It is not possible to add story point values across all sprint teams due to each team’s valuation of a story point. As control accounts each team’s plan and progress will be converted to BCWS and BCWP and can then be added with other teams’ control accounts as we sum totals moving up the OBS or WBS.
7. A sprint team’s sprints can easily become their control account’s work packages. Due to the short nature of sprints, often two weeks in duration, it is not useful nor necessary to collect costs by sprint (work package) and it is not required by EIA 748. (See EIA 748 paragraph 3.5.10. where ACWP is only required at control accounts.) However, a budget must be assigned to each sprint to meet EIA-748 guidelines. The budgets will be equal since the team size is fixed and so is the duration and pace of sprints. If and how this budget is used in determining BCWS and BCWP will be discussed shortly.
8. Because of the agility of agile development, the detailed planning of sprints/releases should not go beyond the next few sprints. Planning packages are appropriate for downstream sprints.
9. It’s likely that not all planned story points or stories will be completed at the end of the project. The planned scope may have exceeded the budget (perform best effort), some stories were more difficult to complete than planned (underestimated scope), or added stories (scope) did not remove sufficient prior scope or add enough budget.
08 The Measurable News 2016.02 | mycpm.org One of the values of agile development is the ability to respond to emerging requirements (features). Given a fixed budget and team size, the new requirements are introduced and replace one or more previous requirements (features). The new features and their stories are added to list of work to be performed and are allocated to future sprints during sprint planning.
SPRINT TEAM WORK PACKAGE EVM MEASUREMENT EIA-748 requires us to assign all control account budget to the account’s work packages. Why? In general not all work packages are of equal value or measured in the same way. Work package budgets are a metric for us to know the significance of each work package toward completing the control account scope. By multiplying the work package percent planned or percent complete by the work package budget we obtain a dollarized value of its contribution to the control account’s progress. After adding all the work packages’ BCWS and BCWP, we then include control account ACWP to create our EVM metrics for analysis and reporting.
But all sprints are of uniform duration and effort and therefore equal budgets. So all story points are of equal dollar value across all sprints within a control account. We don’t need work package budgets to learn the significance of each work package (but we need budgets to meet EAI-748). Therefore we can just add all the story points planned and completed across all the sprint work packages to create a percent planned and completed at the control account level. Which is what we were after in the first place. Analysis is not done, nor required by 748, at the work package level.
EXAMPLE With the above listed statements and processes in mind, it’s possible to create an EVM example of planning and execution for an agile project. We’ll use a project that everyone can relate to. We are going to implement a state-of-the-art self-serve gas station with Europay, MasterCard, Visa (EMV) ATM capabilities. (EMV, not EVM, a potential source of confusion.) Here is our feature list: • Accept stripe and chip EMV Credit Cards • Accept stripe and chip EMV Debit Cards • Accept Cash (common worldwide currencies) • Dispense Fuel • Dispense Cash (various worldwide currencies)
In order to plan the project we need a budget and schedule and resources: • Costs- Ten Engineers, $123/hour • Schedule – 24 weeks • Budget: $1,180,800 • Pace – Three week sprints, 8 sprints • Estimated Average Throughput – 11 story points per sprint
Our goal is to spend all the time and all the budget, and no more, and deliver the most highly desired features; all of them if possible.
Our sprint team decomposed each of our features into stories:
• Accept Credit Cards • Accept chip cards • Scan mag stripe • Validate card • Accept chip cards • Reject card • Validate card • Pin entry • Reject card • Validate pin • Pin entry • Reject pin • Validate pin • Dispense fuel • Reject pin • Select grade • Accept Cash, various Currencies • Select quantity • Accept bills • Dispense • Accept coins • Pump shutdown • Determine currency • Dispense cash • Determine denominations • Select currency • Scan for counterfeit • Input amount • Accept Debit Cards • Input demonization • Scan mag stripe • Dispense
The Measurable News 2016.02 | mycpm.org 09 Next our sprint team estimates the number of story points per story. For example, table 2 shows how story points are used to estimate the effort for the “Accept Credit Cards” stories, and shows how they are assigned to sprints in order of need or priority:
Continuing through theTable rest of 2, the Stories, stories Story yields Points, eighty -andeight Planned total story Sprint points. This equates to our estimated throughput of eleven story points per sprint and eight sprints over the twenty-four Continuing through the rest of the stories yields eighty-eight total story points. This equates weekContinuing schedu throughle. The numberthe rest of thestory stories points yields per sprint eighty is- eightnot constant total story but points. does average This equates eleven to per to our estimated throughput of eleven story points per sprint and eight sprints over the sprint.our estimated The first throughput sprint is lower of eleven due tostory an expectedpoints per learning sprint and curve. eight Our sprints team overof eleven the twenty engineers-four twenty-four week schedule. The number of story points per sprint is not constant but does willweek spend schedu thele. total The budget number ($1,180,800) of story points over per the sprint scheduled is not time.constant Figure but 1does shows average how eleventhe 88 per average eleven per sprint. The first sprint is lower due to an expected learning curve. Our storysprint. points The first are plannedsprint is tolower be completed due to an expectedover time. learning curve. Our team of eleven engineers team of eleven engineers will spend the total budget ($1,180,800) over the scheduled time. Figurewill 1 showsspend the how total the budget 88 story ($1,180,800) points overare plannedthe scheduled to be time. completed Figure 1 shows over howtime. the 88 story points are planned to be completedTotal over Points time. Planned 100 90 Total Points Planned 10080 7090 6080 5070 4060 Story Points 3050 2040 Story Points 1030 200 0 5 10 15 20 25 10 0 Weeks 0 5 10 15 20 25 Total PointsWeeks Planned
Figure 1, PlannedTotal Story Points Points Planned versus Time
From this planning we can create an EVM PMB using the percent of story points planned to be FigureFigure 1, Planned 1, Planned Story Story Points Points versus versus Time Time completed each sprint as a percent of the total, and convert it to BCWS by multiplying the percent by the BAC. Figure 2 shows the PMB created from computing BCWS via the story point FromFrom this thisplanning planning we we can can create create anan EVM EVM PMB PMB using using the the percent percent of story of storypoints pointsplanned planned to be to be completedplan.completed eacheach sprint sprint as aas percent a percent of the of total, the and total, con andvert itconvert to BCWS it byto multiplyingBCWS by multiplyingthe the percentpercent by by the the BAC. BAC. Figure Figure 2 shows 2 shows the PMB the PMBcreated created from computing from computing BCWS via BCWSthe story via point the storyplan. point plan.
10 The Measurable News 2016.02 | mycpm.org PMB 1200000
1000000
800000
600000
Budget BCWS
400000
200000
0 0 5 10 15 20 25 Weeks
Figure 2,Figure PMB 2, PMBBased Based Upon Upon Story Points Points
So ourSo PMB our isPMB based is based on the on thecompletion completion of of story story points,points, not not LOE LOE or sprintsor sprints.. SPRINT FIVE IS DONE SPRINT FIVE IS DONE SprintsSprints one through one through five five are are done done withwith somesome variation variation from from plan. plan. In some In some cases storiescases werestories not were notcompleted completed as planned as planned and others and substituted. others substituted. Table 3 shows Table which 3 storiesshows were which completed stories and were in completedwhich and sprint. in whichIn some sprint. cases the In storiessome werecases done the before stories or wereafter the done planned before sprint or (replanned) after the . planned sprint (replanned). Table 3 Status at End of Sprint Five
Table 3 Status at End of Sprint Five The real measure of progress is not features or stories completed, but story points. Furthermore, The real measurethe completed of progress stories are partis not of various features features. or Nostories one feature completed, is complete but but somestory points. Furthermore,functionality the completed can be demonstrated. stories areWe trust part that of the various stories were features. selected byNo their one importance feature or is complete the required story precedence. Table 4 shows how the first five sprints progressed on a per sprint basis. The Measurable News 2016.02 | mycpm.org 11
Table 4 Summary of Story Point Planned Vs. Completed at Sprint Five but some functionality can be demonstrated. We trust that the stories were selected by their importance or the required story precedence. Table 4 shows how the first five sprints progressed on a per sprint basis.
Sprint 1 2 3 4 5 6 7 8 Points Planned 8 12 11 13 10 13 10 11 SprintSprint 11 22 33 44 55 66 77 88 Points Completed 8 10 7 10 12 PointsPoints PlannedPlanned 88 1212 1111 1313 1010 1313 1010 1111 Points CompletedTable 4 Summary8 of Story10 Point Planned7 Vs.10 Completed12 at Sprint Five EVMPoints measureCompleted of progress is based8 upon10 the story7 points 10planned and12 completed. For a given sprint team all story points are equal in value so they can be the basis of a percent complete. We EVMEVM EVMmeasure measuremeasure of progressofof progressprogress is isis based basedbased uponuponupon thethe the storystory story pointspoints points plannedplanned planned andand completecomplete and completed.dd.. ForFor aa givengiven For a givencansprint sprint use team cumulative team all story all story story points pointspoints are equal planned are in equal value and completed inso valuethey can so as be athey basisthe basiscan of cumulative beof athe percent basis percent complete. of a percent We sprintcomplete team. Table all story 5 summari points arezes equalthe total in valuestory sopoints they plan can nedbe the and basis completed of a percent through complete. sprint 5. We complete.cancan useuse We cumulativecumulative can use storystory cumulative pointspoints plannedplanned story andand points completedcompleted planned asas aa and basisbasis completed ofof cumulativecumulative as percentpercent a basis of cumulativecompletecomplete percent.. TableTable 55 complete. summarisummariTablezzeses 5Table ,thethe Total totaltotal Number 5 summarizesstorystory of Story pointspoints Points planplan thePlannednedned total andand Completed storycompletedcompleted points throughthrough planned sprintsprint and 5.5. completed through sprint 5. Table 5, Total Number of Story Points Planned and Completed Sprint Table0 5, Total Number1 of Story2 Points Planned3 and4 Completed5 6 7 8 Week 0 3 6 9 12 15 18 21 24 Sprint 0 1 2 3 4 5 6 7 8 SprintTotal Points Planned 00 18 202 313 444 545 676 777 888 WeekWeek 00 33 66 99 1212 1515 1818 2121 2424 Total Points Completed 0 8 18 25 35 47 TotalTotal PointsPoints PlannedPlanned 00 88 2020 3131 4444 5454 6767 7777 8888 Total Points Completed 0 8 18 25 35 47 UsingTotal Points the Completed percent planned and0 percent8 complete18 , each25 multiplied35 by the47 control account budget, gives us the cumulativeTable 5, BCWSTotal Number and BCWP. of Story The Pointsorder in Planned which we and complete Completed story points is not UsingUsing thethe percentpercent plannedplanned andand percentpercent completecomplete,, eacheach multipliedmultiplied byby thethe controlcontrol accountaccount budgetbudget,, important,gives us the they cumulative are simply BCWS the means and BCWP. to compute The orderthe percent in which of workwe complete planned story and work points is not Usinggivescompleted the us percent the. Incumulative the planned end we BCWS hopeand thatpercentand allBCWP. 88 complete,story The points order each willin which be multiplied completed, we complete by representing the story control points all theisaccount not budget,important,important, gives theytheyus the areare cumulativesimplysimply thethe meansmeans BCWS toto computecompute and BCWP. thethe percentpercent The order ofof workwork in plannedplannedwhich weandand complete workwork featurescompleted in. theIn thescope end st weatement hope (SOW).that all 88 Table story 6 pointsshows willthe controlbe completed, account representing’s EVM data all for the the storycompletedfirst points five sprints.is. Innot the important, end we hope they that allare 88 simply story points the means will be tocompleted, compute representing the percent all theof work plannedfeaturesfeatures and inin work thethe scopescope completed. ststatementatement In (SOW).(SOW). the end TTableable we 66 hope showsshows that thethe control controlall 88 accountaccountstory points’s’s EVMEVM will datadata be forfor completed, thethe representingfirstfirst fivefive sprints.sprints. all the features inTable the 6, BCWSscope and BCWPstatement Determined (SOW). By Story Points Table 6 shows the control account’s EVM data for the firstTable 6five, BCWS asprints.nd BCWP Determined By Story Points Table 6, BCWS and BCWP Determined By Story Points
Readers will note that in our first sprint our control account SV is zero, eight ($107,345) of eight storyReaders points will were note completed.thatTable in our 6, BCWS firstBut spwe rand inthave our BCWP a controlnegative Determined account control SV accountBy is Story zero, CV Points eight of $ ($107,345)40,255. Why? of eightWe Readersplanned willfor a note “fixed” that costin our of first10 engineers sprint our at control $123/hour account for eachSV is three zero, week eight sprint. ($107,345) The average of eight storystory pointspoints werewere completed.completed. ButBut wewe havehave aa negativenegative controlcontrol accountaccount CVCV ofof $$4040,,255.255. Why?Why? WeWe Readersnumber will of note story that points in ourper sprintfirst wassprint planned our control as eleven account. But we anticipatedSV is zero, aeight learning ($107,345) curve so of plannedplanned forfor aa “fixed”“fixed” costcost ofof 1010 engineersengineers atat $123/hour$123/hour forfor eacheach threethree weekweek sprint.sprint. TheThe averageaverage eightwenumber story planned points of story for wereonly points eight completed. per story sprint points was But planned on we our have first as eleven asprint negative., Buandt wecompleted control anticipated account eight. a learning So CV we ofhave curve $40,255. an so Why?numberexpected We planned of negative story forpoints CV a “fixed” dueper sprintto the cost learningwas ofplanned 10 curve engineers as. (Thiseleven is.at Busimilar $123/hourt we anticipatedto an expectedfor each a learning negative three curve weekCV so sprint. wewe plannedplanned forfor onlyonly eighteight storystory pointspoints onon ourour firstfirst sprintsprint,, andand completedcompleted eight.eight. SoSo wewe havehave aann The averagewhenexpected it’s number negativethe first monthCVof story due of to apoints the0/100% learning per work sprint curve package .was (This whenplanned is similar budget as to waseleven. an expectedspent, But work negativewe was anticipated done, CV but a learningexpectednot completed.) curve negative so we It CV’planneds easier due to to forthe just onlylearning explain eight curvethe story variance. (This points isor similar better on our yetto an havefirst expected thesprint, variance negative and thresholdscompleted CV whenwhen it’sit’s thethe firstfirst monthmonth ofof aa 0/100%0/100% workwork packagepackage whenwhen budgetbudget waswas spent,spent, workwork waswas done,done, butbut eight.setnot So highcompleted.) we enough have an toIt ’expectednots easier make to this justnegative tempor explain arCV ythe CV due variance “significant” to the or learningbetter. yet curve.have the (This variance is similar thresholds to an expectednot completed.) negative CVIt’s wheneasier toit’s just the explain first themonth variance of a or0/100% better yet work have package the variance when thresholds budget was Ssetince high our enough sprint teamto not is make of fixed this sizetempor andar sety CV rates “significant” the ACWP. grows uniformly each sprint. The spent,set work high enoughwas done, to not but make not this completed.) temporary CV It’s “significant” easier to just. explain the variance or better yet only variables are the number of stories points planned each sprint and the number completed. haveS Stheinceince variance ourour sprintsprint thresholds teamteam isis ofof fixedfixed set highsizesize andand enough setset ratesrates to thethenot ACWPACWP make growsgrowsthis temporary uniformlyuniformly each eachCV “significant”. sprint.sprint. TheThe onlyByonly sprint variablevariable fivess we’veareare thethe spent numbernumber $738,000, ofof storiesstories planned pointspoints for plannedplanned $724 , each582each worth sprintsprint o andandf story thethe points,numbernumber and completed.completed. completed Since our sprint team is of fixed size and set rates the ACWP grows uniformly each sprint. The $630,655By sprint fiveworth we’ve of story spent points. $738,000, So we planned have cumulative for $724,582 cost worth and cumulative of story points, schedule and problemscompleted only Byvariablesas shownsprint fivein are the we’ve the follow number spenting PMB$738,000, of storieschart ,planned Figure points 3for. planned $724,582 each worth sprint of story and points, the number and completed completed. $630,655$630,655 worthworth ofof storystory points.points. SoSo wewe havehave cumulativecumulative costcost andand cumulativecumulative scheduleschedule problemsproblems By sprintasas shownshown five inin thethewe’ve followfollow spentinging PMBPMB$738,000, chartchart,, Figure Figureplanned 33.. for $724,582 worth of story points, and completed $630,655 worth of story points. So we have cumulative cost and cumulative schedule problems as shown in the following PMB chart, Figure 3.
12 The Measurable News 2016.02 | mycpm.org
Figure 3, Cost and ScheduleFigure 5, Final Performance Project EVM Record Based on Story Points
Clearly,At theat thefinal present data point rate the ofBCWS spending and ACWP and accomplishmentare equal. All the budget we will was not spent. be Theable to complete all storyuncompleted points when scope theis shown budget as BCWP and time less thanruns BCWS. out. In agile development we’ll continue to prioritize the remaining stories based on their “utility”, but realize now that all features, CONCLUSION stories, and their story points will not be completed. At this point some functionality of AcceptThis Credit example Cards, has illustrated Accept Cash,a means and to implement Accept Debit EVM Cardson agile has development been completed. programs using(The agile developmentstory points term’s as a means “velocity” of setting is used BCWS to and measure determining the rateprogress at which (BCWP). story The points story points are being are completed,used as abut unit is of independent work planned ofand the completed cost involved.) to derive a percent planned and a percent completed on a work package (sprint) basis. These values may be multiplied by the work EMERGENTpackage (sprint) REQUIREMENT! budget but can also just be summed for the whole control account since all story We havepoints just are learnedof equal valuethat ourwithin major a control competitor account. has announced a new feature in their self-serve Gas Pump/ATM. Customers will be able to review their last ten debit/credit card transactions.In our example We need, the total to include of story pointsthis feature planned if and we completed are to be were competitive. summed to the control Agileaccount development to create allowsa percent us complete to provide at the redirection control account so that level. new These features percents can are beconverted to implementeddollarized inBCWS the remainingand BCWP bysprints. multiplication But to dowith so, the we control need account to remove budget. some ACWP existing is featuresrecorded (scope). at the control account level. This example has also shown how an emergent requirement can be incorporated into the One wayplanning to implement and the final this product change by substituting is to estimate it for equivalentthe number scope of and story then points replanning in the as new featureneeded. and remove the same number from the existing project. We can do this by zeroing the story points for the deleted stories and adding in the new features and their stories and storyWhile points. some Some long previousestablished features “rules” of may EVM have have only been been cast aside, partially such completedas SPI = 1 at project’sbut there is someend, functionality the author believes provided. that EIAOnce 748 again, Guideline the spriority have been is tomet. provide the most value (utility) for the budget spent, and not necessarily completing all functionality initially stated. Table 7 shows the zeroed stories, added stories and story point changes, and planned sprints.
The Measurable News 2016.02 | mycpm.org 13 Table 7,, RevisedRevised StoriesStories andand StoryStory PointsPoints Table 7, Revised Stories and Story Points Table 7, Revised Stories and Story Points
Table 7, Revised Stories and Story Points We have zeroed the stories related to multiple currencies. This has freed five story points, which isWe the have teams’ zeroed estimate the stories for the related story pointsto multiple related currencies. to the new This feature has freed of recalling five story ten points,recent which We havetransactions.isWe the have zeroed teams’ zeroed Theseestimate the the stories stories stories for the are relatedrelated story assigned topoints to multiple multipleto relatedsprints currencies. tocurrencies.7 andthe new8 asThis featureshown Thishas freed in ofhas Tablerecalling fivefreed 8. story tenfive points, recent story which points, whichtransactions.is isthe the teams’ teams’ Theseestimate estimate stories for the are for story assigned the points story to related sprints points to7 andrelatedthe new8 as featureshownto the in ofnew Tablerecalling feature 8. ten ofrecent recalling ten recentOurtransactions. transactions. revised status These Theseis: stories stories are assigned are assigned to sprints 7to and sprints 8 as shown 7 and in 8 Table as shown 8. in Table 8. Our revisedOur revised status status is: is: Our revised status is: Table 8,, ReplanningReplanning HasHas RemovedRemoved SomeSome PlannedPlanned WorkWork inin SprintSprint FiveFive Table 8, Replanning Has Removed Some Planned Work in Sprint Five Table 8, Replanning Has Removed Some Planned Work in Sprint Five
Table 8, Replanning Has Removed Some Planned Work in Sprint Five This revises our EVM BCWS and BCWP as shown in Table 9: This revises our EVM BCWS and BCWP as shown in Table 9: This revisesThis revises our ourEVM EVM BCWS BCWS andTable and BCWP 9 ,BCWP, RevisedRevised as Plan Planas shown shownChangesChanges inthethein Table BCWSBCWSTable andand 9 :9: BCWPBCWP Table 9, Revised Plan Changes the BCWS and BCWP Table 9, Revised Plan Changes the BCWS and BCWP
Compared to our original plan in Table 10: Compared to our Tableoriginal 9, plan Revised in Table Plan 10: Changes the BCWS and BCWP Compared to our original plan in TableTable 1010,, :OriginalOriginal PlanPlan andand ProgressProgress Compared to our original plan in TableTable 10 10:, Original Plan and Progress Table 10, Original Plan and Progress
Table 10, Original Plan and Progress
This has removed $40,255 of previously planned but uncompleted work (54 versus 51 story points) in sprint 5, and redistributed some work in sprints 6 and 7. The BCWP remains unchanged since the removed story points had not yet been completed. Otherwise an adjustment to BCWP would be needed as well. Or course the ACWP remains unchanged.
We now have a new PMB, as shown in Figure 4, however the endpoint is still based upon the original 88 story points, our budget, and eight sprints.
14 The Measurable News 2016.02 | mycpm.org
Figure 4, RevisedFigure PMB 5, Final and Project Status EVM RecordThrough Sprint Five
ENDAt OF the finalPROJECT data point the BCWS and ACWP are equal. All the budget was spent. The We wereuncompleted able to scopecomplete is shown 80 asof BCWP the 88 less story than points BCWS. before the budget and time ran out. The oneCONCLUSION uncompleted story was “Scan for Counterfeit” planned for sprint 6 but never completed. The team and customers’ involvement in planning the sprint deferred this and ultimatelyThis example it did not has getillustrated addressed. a means to implement EVM on agile development programs using story points as a means of setting BCWS and determining progress (BCWP). The story points are The customerused as a unit did of get work their planned most and highly completed desired to derive features a percent and plannedwas able and to a implementpercent the abilitycompleted to recall on the a work ten mostpackage recent (sprint) ATM basis transactions.. These values Themay beproject multiplied completed by the work on budget and schedule,package (sprint) with budgetsome unaddressedbut can also just features be summed the for customer the whole deemedcontrol account “minor” since scope. all story (A modificationpoints are ofto equalthe contractvalue within and a controladditional account. time and budget could address this if needed.) The final PMB is shown in Figure 5: In our example, the total of story points planned and completed were summed to the control account to create a percent complete at the control account level. These percents are converted to dollarized BCWS and BCWP by multiplication with the control account budget. ACWP is recorded at the control account level. This example has also shown how an emergent requirement can be incorporated into the planning and the final product by substituting it for equivalent scope and then replanning as needed. While some long established “rules” of EVM have been cast aside, such as SPI = 1 at project’s end, the author believes that EIA 748 Guidelines have been met.
Figure Figure5, Final 5, Final Project Project EVM EVM Record Record
At theAt final the final data data point point the the BCWSBCWS andand ACWP ACWP are are equal. equal. All theAll budgetthe budget was spent. was Thespent. The uncompleteduncompleted scope scope is is shown shown as BCWPBCWP less less than than BCWS. BCWS. CONCLUSION
The Measurable News 2016.02 | mycpm.orgThis example has illustrated a means to implement EVM on agile development programs using 15 story points as a means of setting BCWS and determining progress (BCWP). The story points are used as a unit of work planned and completed to derive a percent planned and a percent completed on a work package (sprint) basis. These values may be multiplied by the work package (sprint) budget but can also just be summed for the whole control account since all story points are of equal value within a control account. In our example, the total of story points planned and completed were summed to the control account to create a percent complete at the control account level. These percents are converted to dollarized BCWS and BCWP by multiplication with the control account budget. ACWP is recorded at the control account level. This example has also shown how an emergent requirement can be incorporated into the planning and the final product by substituting it for equivalent scope and then replanning as needed. While some long established “rules” of EVM have been cast aside, such as SPI = 1 at project’s end, the author believes that EIA 748 Guidelines have been met. CONCLUSION This example has illustrated a means to implement EVM on agile development programs using story points as a means of setting BCWS and determining progress (BCWP). The story points are used as a unit of work planned and completed to derive a percent planned and a percent completed on a work package (sprint) basis. These values may be multiplied by the work package (sprint) budget but can also just be summed for the whole control account since all story points are of equal value within a control account.
In our example, the total of story points planned and completed were summed to the control account to create a percent complete at the control account level. These percents are converted to dollarized BCWS and BCWP by multiplication with the control account budget. ACWP is recorded at the control account level.
This example has also shown how an emergent requirement can be incorporated into the planning and the final product by substituting it for equivalent scope and then replanning as needed.
While some long established “rules” of EVM have been cast aside, such as SPI = 1 at project’s end, the author believes that EIA 748 Guidelines have been met. An open mind toward the use of EVM and the use of agile development, where all scope might not be completed, is needed to allow EVM to work in agile development. The benefit is the power of agile development and the power of EVM are brought together.
As Gary Bliss, Director of PARCA, said last spring, “If we don’t figure out how to apply EVM to agile development, we don’t have a tool to manage agile development.” The author hopes this paper and example has shown one way to gain the value of using EVM while also gaining the value of agile development. Your comments and ideas are welcome.
About the Author Ray W. Stratton, EVP, PMP is the president and founder of Management Technologies. His firm provides EVM process engineering, third party certification, EVP exam preparation products and workshops, and EIA-748 EVMS solutions, specializing in wickedly challenged EIA-748 EVM implementation. Ray is the author of the Earned Value Management Maturity Model, “Ray Stratton’s EVP Exam Study Guide”, and is the editor of The EVM Newsletter. He served on the College of Performance Measurement governing board for almost ten years. Ray can be reached at raystratton@ mgmt-technologies.com.
16 The Measurable News 2016.02 | mycpm.org THE MEASURABLE NEWS 2016.02
IMPLEMENTING PROJECT CONTROLS: PREPARING FOR THE ESTABLISHMENT OF THE INTEGRATED (COST AND SCHEDULE) PERFORMANCE MEASUREMENT BASELINE By Matthew T. Gonzales
Failing to prepare, is preparing to fail’. John Wooden
‘John Robert Wooden was an American basketball player and coach. Nicknamed the "Wizard of Westwood," as head coach at UCLA he won ten NCAA national championships in a 12-year period, including a record seven in a row.’ Wikipedia.
His 29-year college head coaching career resulted in a 664-162 record and an amazing .804 winning percentage, as well as a record 10 national championships.
John Wooden was an English teacher first and coach second. As a teacher/coach, he developed, over many years, a teaching approach that evolved into a systematic, repeatable process, which would make W. Edward Deming proud. The concept of statistical process controls was many years ahead, as was ‘big data’ and ‘Sabermetric’s’ concepts, thus winning percentage was his metric of success.
But he never taught to win. Rather, he taught the execution of the process; winning would be a by-product. Opponent teams would comment ‘it was as if we weren’t even on the court, they just executed their game plan’.
So he taught his process. That process started at the first practice of each season. Every season, before the start of the first practice, all players (seniors to freshmen) are told to remove their shoes and socks. He then instructed the players the appropriate way to put on their socks and then their shoes. He did this because he knew the importance of a sound foundation. For a basketball player, the foundation is the feet. He knew performance would be impacted negatively if the player were to experience blisters or other foot maladies due to poor ‘planning’ of putting on their shoes incorrectly (details matter).
For a project, the sound foundation is the project integrated cost and schedule baseline. Effort and attention need to be applied to the development of the project plan the same way effort and attention are applied to putting on one’s socks and shoes correctly.
The analogy is that the start of any project is similar to the start of a new season. A project team needs to go through the process of establishing a sound foundation by assessing all aspects of developing a sound, robust project integrated cost and schedule baseline plan.
This article is about ‘preparing to succeed’ by putting your socks and shoes on correctly. Doing the due diligence of looking at all parts of the planning process that ensure a sound and realistic project cost and schedule baseline plan is put in place at the start of the project.
PREAMBLE The conversation of planning and preparing for the development of the integrated cost and schedule baseline started with an assignment to participate in a NASA agency level Earned Value Management System (EVMS) implementation on a project at Johnson Space Center. At the time, EVMS as an agency core competency was still a work in progress. On this particular project the earned value implementation was the responsibility of a contractor hired to meet the NASA requirement that projects above a certain dollar threshold do earned value. His struggles were many, but what was evident at the first engagement was that the core EVMS planning products were coming together in an ‘ad hoc’ fashion. Having come from over 20 years of DoD EVMS project planning experience, and having implemented performance measurement baselines on at least a dozen projects, it was clear that this important phase of planning was missing. This paper was a response to that experience, and therefore is a bit NASA centric, but the core tenets of project planning described here should be considered universal to all projects requiring an EVMS Performance Measurement Baseline.
The Quarterly Magazine of the College of Performance Management | mycpm.org 17 INTRODUCTION The establishment of the Integrated (Cost and Schedule) Performance Measurement Baseline is the result of a systematic approach that steps the project through each phase of the planning process, with each phase resulting in a set of tangible products. Each subsequent phase builds on the previous phase such that at the end of the planning cycle, all required documents are completed and integrated.
The responsibility of leading the project team through the planning of a project usually falls on the Project Business Manager, a task delegated by the Project Manager (PM). The approach is documented in Project Planning Guidelines (also referred to as Project Directives), a project specific document that describes programmatic, cost and schedule assumptions, constraints and planning guidelines. Guidelines are developed as early as possible in planning and issued to the project team. Conducting a briefing to the entire team outlining the approach is highly recommended for best results.
STARTING WITH THE BASICS: WHAT IS? Providing context is important when communicating and leading a group of project control account managers and other project leadership. Also, it is not uncommon for project team members to have diverse backgrounds. Starting with basic level sets the team, provides a common language and reduces miscommunications. Assume nothing.
What is Project Management: The discipline of planning, organizing, and managing resources to bring about the successful completion of specific project goals and objectives.
What areWha Projectt are ProjectControls Controls (Cost (Costand Schedule):and Schedule): Consists Consists of thoseof those processes processes performed to observe performedproject execution to observe so project that potential execution problems so that potential can be problemsidentified can in be a identifiedtimely manner and correctivein a timely action manner can andbe taken. corrective action can be taken. Projects employ the Triple Constraint model, where the goals of the planning are to Projectsachieve employ balance the Triple between Constraint cost, schedule model, andwhere scope. the goals Once achieved,of the planning during theare to achieve balance executionbetween andcost, control schedule phase, and the scope. goal is Once to maintain achieved, that balanceduring theas each execution constraint and control phase, thein the goal model is to is maintain pulling and that pushing balance in differentas each constraintdirections whilein the also model reacting is pulling to the and pushing impactsin different from externaldirections influences. while also reacting to the impacts from external influences.
Scope
Quality
Cost Schedule
The Project Management Triangle (Triple Constraint model)
The ProjectThe Controls Project Control functions function is constantly is constantly asking: asking:Where are we relative to our plan? Where should weWhere be? Can are wewe relativeget on track?to our Ifplan? so, how? Where What should is the we impactbe? Can to we cost get and on track schedule? If reserves? so, how? What is the impact to cost and schedule reserves? BUDGETING IS NOT FUNDING Project controlsBudgeting focus is NOT on Fundingthe planning of budgets (costs) that fall within project funding constraints.Project The controls difference focus betweenon the planning the project of budgets cost (costs)plan and that the fall projectwithin projectfunding limits is the availablefunding cost constraints. reserves. TheWhen difference developing between the theproject project cost cost baseline, plan and analysis the project needs to be conductedfunding to assure limits thatis the at available no time cost budgets reserves. exceed When available developing funds the andproject that cost sufficient cost reservesbaseline, are always analysis available. needs to be conducted to assure that at no time budgets exceed available funds and that sufficient cost reserves are always available. Budgeting is the time-phased planning of the total resources required to satisfy the project’s contractualBudgeting requirements. is the time-phased planning of the total resources required to satisfy the project’s contractual requirements.
18 The Measurable News 2016.02 | mycpm.org ‘If you can't describe what you are doing as a process, you don't know what you're doing.’ W. Edward Deming
The End-to-End Planning Process ‘If you can't describe what you are doing as a process, you don't know what you're doing.’ W. Edward Deming The Project Business Manager usually develops the overall process and obtains THE END-TO-END PLANNING PROCESS Theconcurrence from Project Business Managerthe Project usuallyManager. develops The documented process the overall process and obtainsis a key concurrence fromcommunication vehicle to the entire project team. the Project Manager. The documented process is a key communication vehicle to the entire project team. • Keep it simple ThreeThree rules to follow when developing the planning process: rules to follow when developing the planning process: • Keep• Keep it serial it simple. The . processThe process is the road is the road map frommap from Authorization to Proceed Authorization to Proceed, to , to establishmentestablishment of a performance measurement baseline. of a performance measurement baseline. • Keep it serial. The . The recipe is simple when each the phase is executed in the recipe is simple when each the phase is executed in the correct order. Modifying• Keep it realcorrect order. Modifying the sequence will result in “redo’s” or a non the sequence will result in “redo’s” or a non integrated baseline. integrated baseline • Keep it real. Although each project is unique, the process to develop a baseline is not. Adapt the core serial. Although each project is unique, the process to develop a process to your specific application. baseline is not. Adapt the core serial process to your specific application. Following are two samples of documenting the process in simple flow diagrams. Benefits of documenting your process are many, but the key benefits are organization and communications.Following are two samples of documenting the process in simple flow diagrams. Benefits of documenting your process are many, but the key benefits are organization and communications
Figure 1. Project that employed Integrated Product Teams and Integration Master Plans and Integrated Master Schedules Figure 2. Project that employed tradition matrix approach
THE PLANNING PROCESS TheThe Planning Process process for developing an integrated Performance Measurement Baseline has been distilled into nine discrete steps. Each step looks at a specific planning process and the resulting planning product. Each product demonstrates the due diligence of the planning and is an auditable document. The process for developing an integrated Performance Measurement Baseline has Planningbeen distilled into nine discrete steps. Ea is an iterative process, so during planning,ch step looks at a specific planning it is expected to have to revise and revisit products of the plan and adjust based on project dynamics and project management direction.process and the resulting planning product. Each product demon Just go back to the appropriate step and continue through the nextstrates the due sequence of processdiligence of the planning and steps. is an auditable document.
Planning is an iterative process, so during planning, it is expected to have to revise and revisit products of the plan and adjust based on project dynamics and project The Measurable News 2016.02 | management direction. Just go back to the appropriate step and mycpm.org continue through 19 the next sequence of process steps. Major planning phase/emphasis Product
1. Scope of the project Statement of Work Integrated Management Plan
2. Development Approach Integrated Product Team (IPT) Organization Breakdown Structure
3. Organize the work Work Breakdown Structure (WBS) WBS Dictionary
4. Assign the Work Responsibility Assignment Matrix
5. Schedule the Work Integrated Critical Path Networks Integrated Master Schedule Key Interfaces (Receivables/Deliverables)
6. Identify Resources Work Packages/Planning Packages Labor, Material, ODC, Subcontract,
7. Estimate the Cost the Work Current forward pricing rates, Time-phased (monthly) cost profile
8. Negotiate and approve plan Control Account Plan concurred by Project Control Account Manager (PCAM), Project Manager and Line Manager (or IPT lead)
9. Develop Earning Methodology BCWP ‘algorithmic earning’ consistent with BCWS profile
TheThe Planning Planning ProcessProcess
Comment omment on step on 9, step Developing e elopin Earning arnin Methodology. et o olo When planning en plannin a work a package or pac a e or control or control account, account earned earne value alue technique tec nique is is a a consideration during theconsi eration planning process. urin t e Depending plannin process on the Elements epen in of on Cost t e lements(Labor, ODC, o ost Matl, Subcontracts) a or certain atl earning u contracts techniques certain are earnin preferred, tec niques for example, are pre erre in-house or labor scope is best trackede ample through in ouse schedule la or scope performance, is est trac e where t rou subcontract sc e ule effort per ormance may use ere CPR reports, or paymentsu contract milestones. e ort Therefore, ma use keep reports the earning or pa ment approach milestones in your ere ore mind as eep the planningt e proceeds.earnin approac in our min as t e plannin procee s is step is at t e en ecause re ar less o t e earne alue tec nique t e earnin This stepplan is at as the to end e consistent because it regardless t e u et of the plan earned value e technique, test or t is the is i earning t e plan has to besc e ule consistent is procee in with the tobudget plan t e plan earn (BCWS).e alue The s oul test re lect for this t is is it if the a eroschedule is proceedingcumulati to plan,e c e ule the earned ariance value sshould t e reflect is lui this urin with aplannin zero cumulative it is est toSchedule Variance. ait As orthe t e BCWS is to fluid e appro e during planning,an t en e elopit is best t e to earnin wait for approac the BCWS on ato static be approvedtar et and then develop the earning approach on a static target.
‘In preparing for battle I have always found that plans are useless, but planning is indispensable.’ Dwight D. Eisenhower
SCHEDULE THE PROCESS A critical planning and communication document is the end-to-end schedule for the planning phase. Develop an end-to-end schedule for the planning cycle with interdependencies between planning phases and phase products. Determine appropriate periods of performance for the phases based on customer requirements such as the first submittal of performance reports, an Integrated Baseline Review (IBR) date, etc.
First and foremost, the schedule is a communication vehicle that clearly delineates responsibilities, identifies due dates and includes data review and approval cycle in the planning process.
20 The Measurable News 2016.02 | mycpm.org ‘In preparing for battle I have always found that plans are useless, but planning is indispensable.’ wight . isenhower
Schedule the Process critical plannin an communication ocument is t e en to en sc e ule or t e plannin p ase e elop an en to en sc e ule or t e plannin c cle it inter epen encies et een plannin p ases an p ase pro ucts etermine appropriate perio s o per ormance or t e p ases ase on customer requirements suc as t e irst su mittal o per ormance reports an nte rate aseline e ie ate etc