Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Earned Value Management and Agile Tips for Success


Published on

As the Department of Defense focuses on "delivering 75% solutions in months [instead of] 100% solutions in years" Agile is finding its way into big, traditionally managed programs. This event specifically addresses Agile in Defense. This presentation was an invitation following a successful meeting at the ADAPT meeting.

Published in: Business
  • Thought-provoking material. A couple of questions if I may - Slide 16 - If you touch it only once you're not iterating: I understood the point was that functionality be developed, integrated and tested in an iteration. This slide implies subsequent iterations correct or further develop the "already-done" functionality? Slide 32 confused me - at some point in time we planned to be 108 percent complete - how does that work then? Malcolm Farrelle (
    Are you sure you want to  Yes  No
    Your message goes here

Earned Value Management and Agile Tips for Success

  1. 1. Earned  Value  Management  and  Agile   Tips  for  Success   Brent  Barton,  President,  Agile  Advantage,  Inc.    
  2. 2. !  The  Problem  !  An  Agile  Story  !  Contracts  vs  Value  !  Scrum  (An  Agile  Project  Management   Framework)  !  TradiAonal  Earned  Value  Management  !  Agile  Earned  Value  Management  (AgileEVM)  !  Project  Case  Study  !  Open  Discussion   *Slides  available  via  NDIA,  or   2  
  3. 3. !  Robert  Gates,  the  United  States  Secretary  of   Defense,  in  a  September  2008  speech,  said,   “Our  convenAonal  modernizaAon  programs   seek  a  99%  soluAon  in  years.  Stability  and   counterinsurgency  missions—the  wars  we  are   in—require  75%  soluAons  in  months.   Agile  Methods:  Selected  DoD  Management  and  AcquisiAon  Concerns,   Carnegie  Mellon  University,  October  2011,  p.  ix   ©2011  Agile  Advantage,  Inc.    All  rights  reserved.   3  
  4. 4. Focus  on  frequent   feedback  cycles  to   determine  which   75%  is  correct   ©2011  Agile  Advantage,  Inc.    All  rights  reserved.   4  
  5. 5. This  is  the  best,  simplest,  easiest  to  use   applica=on  we  have   ever  go@en  in  both    Customer  Care  and  the   Retail  Stores!    Whatever  you  all  did,  I   want  more  of  that!  
  6. 6. Cost    Employee  SaAsfacAon   Savings    Customer  SaAsfacAon   Revenue   New   RetenAon   Revenue    Cost  Savings    New  Revenue     through  efficiency   Shareholder   Value   Value   Compliance   Employee   Customer   SaAsfacAon   SaAsfacAon   7  
  7. 7. !  #  Lives  saved  !  Simple  to  Use  !  Secure  !  ?   Value   ©2011  Agile  Advantage,  Inc.    All  rights  reserved.   8  
  8. 8. The  primary  purpose  of  the  [EVMS]  system  is  to  support  program  management*   Scope   Schedule   Cost   9   *  Earned  Value  Management  Systems  ANSI/EIA-­‐748-­‐B-­‐2007  
  9. 9. !  Time  and  Materials  (T  &  M)  !  Fixed  Price  !  Cost  Plus  IncenAve  Fee  !  IDIQ/Delivery  orders   •  or  task  orders   These  are     cost-­‐based!   ©2011  Agile  Advantage,  Inc.    All  rights  reserved.   10  
  10. 10. Strategic   Value  Required  to  make  good   Informs  and   Guides   Decisions   Quality   Constraints   (Schedule,  Cost,  Scope)   Source:    Jim  Highsmith   11  
  11. 11. Focus  on  value   delivery,   informed  by  constraints  and   quality   ©2011  Agile  Advantage,  Inc.    All  rights  reserved.   12  
  12. 12. We  are  uncovering  beper  ways  of  developing   soqware  by  doing  it  and  helping  others  do  it.   Through  this  work  we  have  come  to  value:  Individuals  and  interacAons  over  processes  and  tools  Working  soqware  over  comprehensive  documentaAon   Customer  collaboraAon  over  contract  negoAaAon   Responding  to  change  over  following  a  plan   That  is,  while  there  is  value  in  the  items  on   the  right,  we  value  the  items  on  the  leq  more.   hpp://   ©2011  Agile  Advantage,  Inc.    All  rights  reserved.   13  
  13. 13. !   It  is  not  possible  to  completely  specify  an  interacAve   system.   Wegner’s  Lemma,  1995  !   Uncertainty  is  inherent  and  inevitable  in  soqware   development  processes  and  products.   Ziv’s  Uncertainty  Principle,  1996  !   For  a  new  soqware  system  the  requirements  will  not   be  completely  known  unAl  aqer  the  users  have  used   it.   Humphrey’s  Requirements  Uncertainty  Principle,  c.  1998   14  
  14. 14. !   Stack  Ranked   PrioriAzaAon  based  on   Business  Value  and  risk  !   Self  organizing,  cross-­‐ funcAonal  teams  !   DefiniAon  of  Done  !   PotenAally  Shippable   Increments  !   Velocity  !   ConAnuous  Improvement   15  
  15. 15. If  you  only  touch  it   once,  you  are  not   itera=ng.       Be@er  to  make   small  failures  and   learn  rather  than   suffering  big   failures.   ©2011  Agile  Advantage,  Inc.    All  rights  reserved.   16  
  16. 16. Total Allocated Budget! EAC   EsAmate  at  Complete   Management Reserve! PMB   Performance Management Baseline$   Planned  Value   (PV)   Actual  Cost   (AC)   (EV)   Earned  Value   Time   Time! Completion! Now! Date! 17  
  17. 17. Cost Performance Index (CPI=EV/AC) CPI < 1 CPI =1 CPI > 1 Over Budget On Budget Under Budget Schedule Performance Index (SPI=EV/PV) SPI < 1 SPI =1 SPI > 1Behind Schedule On Schedule Ahead of Schedule 18  
  18. 18. !  Integrates  cost  and  schedule  management  !  Forecasts  in  financial  units  based  on  units   used  for  actual  cost  !  Decades  of  use  !  Part  of  PMBOK  (ANSI/PMI  99-­‐001-­‐2008)  !  Part  of  EVMS  (ANSI/EIA-­‐748-­‐B-­‐2007)   19  
  19. 19. !  Typical   implementaAons   Ugh!   expect  everything  fully   defined  up  front  !  No  asserAon  of  quality  !  Claiming  value  earned   on  intermediate  work   products   20  
  20. 20. !   A  planning  package  is  a  holding  account  (within  a   control  account)  for  budget  for  future  work  that  it  is   not  yet  pracAcable  to  plan  at  the  work  package  level.   The  planning  package  budget  is  Ame-­‐phased  in   accordance  with  known  schedule  requirements  (due   dates)  for  resource  planning,  and  the  plans  are  refined   as  detail  requirements  become  clearer  and  the  Ame  to   begin  work  draws  nearer.  A  program  may  elect  to  break   the  work  assigned  to  a  control  account  into  smaller   groupings  of  tasks,  i.e.,  mulAple  planning  packages,  for   internal  planning  and  control  reasons.   -­‐Earned  Value  Management  Systems  ANSI/EIA-­‐748-­‐B-­‐2007   21  
  21. 21. !  There  is  no  standard  advance  planning  look-­‐ ahead  period  (i.e.,  a  planning  “horizon”  or   “window”)  for  conversion  of  planning   packages  into  work  packages  that  is   appropriate  for  all  programs  or  condiAons.   Each  organizaAon  must  determine  its  own   policies  in  this  regard.   -­‐Earned  Value  Management  Systems  ANSI/EIA-­‐748-­‐B-­‐2007   22  
  22. 22. Replace  (un-­‐learn)   some  company   EVMS  policies  to   support  adap=ve   planning     ©2011  Agile  Advantage,  Inc.    All  rights  reserved.   23  
  23. 23. !  MathemaAcally  proven  that  Forecasts  based   on  average  velocity  (story  points)≡  esAmate   at  complete  EAC  (dollars)  !  Key  AssumpAon:    The  raAo  of  (story  points   completed)/(total  story  points  in  a  release)  is  a   good  measure  of  Actual  Percent  Complete   Sulaiman,  Barton,  Blackburn  “AgileEVM  -­‐  earned  value  management  in   Scrum  projects,”  2006   hpp://   24  
  24. 24. !  Release  Baseline   •  Budget  (BAC)   •  IniAal  Scope   •  Start  Date  !  Each  IteraAon  (Sprint)   •  Points  accepted  by  Product  Owner     – meets  DefiniAon  of  Done   •  Points  add  or  removed  from  release  scope   •  Actual  Cost   25  
  25. 25. !  Now  we  can  focus   on  Value…   26  
  26. 26. !  Because  the  performance  measurement  baseline   (PMB)  is  expressed  as  “number  of  story  points   planned”  rather  than  at  the  level  of  specific  tasks,   it  allows  course  correcAons  to  be  made  without   disrupAon  or  re-­‐baselining  of  the  PMB.    !  This  addresses  the  criAcism  expressed  in  the   Defense  AcquisiAon  Reform  Findings  and   RecommendaAons  (DARFAR)  report  regarding  the   inability  of  tradiAonal  EVMS  to  idenAfy  issues   related  to  “contract  requirements  that  uperly   failed  to  meet  warfighter  needs”  [House  Armed   Services  Commipee  2010].   Agile  Methods:  Selected  DoD  Management  and  AcquisiAon   Concerns,  Carnegie  Mellon  Urights  reserved.   ctober  2011,  p.  627   ©2011  Agile  Advantage,  Inc.    All   niversity,  O 3  
  27. 27. 28  
  28. 28. !  Integrated  Cost  and  Schedule  informaAon   provides  beper  insights  than  schedule  alone   29  
  29. 29. 30  
  30. 30. 31  
  31. 31. 32  
  32. 32. AgileEVM  helps  balance  defined   plans  and   adap=ve   planning  for  delivering  value   ©2011  Agile  Advantage,  Inc.    All  rights  reserved.   33  
  33. 33. !  Focus  on  delivering  value  !  Constraints  inform,  not  dictate  outcomes  !  Quality  must  be  part  of  the  decision  process  !  AgileEVM  helps  communicate  by  translaAng   points  to  dollars   •  Can  provide  alternaAves  to  contracAng  challenges   34  
  34. 34. !   Focus  on  frequent  feedback  cycles  to  determine   which  75%  is  correct  !   Focus  on  value  delivery,  informed  by  constraints  and   quality  !   If  you  only  touch  it  once,  you  are  not  iteraAng.       Beper  to  make  small  failures  and     learn  rather  than  suffering     big  failures.  !   Replace  (un-­‐learn)  some     company  EVMS  policies  to     support  adapAve  planning    !   AgileEVM  helps  balance  defined     plans  and  adapAve  planning     for  delivering  value   35  
  35. 35. !   President:  Agile  Advantage,  Inc.   !   Former  CTO,  Development   Manager,  PMO  Manager,  Agile   Coach,  Mentor,  CerAfied  Scrum   Trainer,  ScrumMaster,  Product   Owner   !   AcAve  pracAAoner  delivering  value   using  Agile  and  helping  others  do   it;  from  small  Product  companies  to  Blog:   very  large  organizaAons   Twiper:  brentbarton  !   ArAcles   •  “Manage  Project  Por€olios  More  EffecAvely  by  Including  Soqware  Debt  in  the  Decision  Process”,  Cuper   Journal  2010   •  “AgileEVM  –  Earned  Value  Management  in  Scrum  Projects”,  IEEE  2006   •  “ImplemenAng  a  Professional  Services  OrganizaAon  Using  Type  C  Scrum”,  IEEE   •  “Establishing  and  Maintaining  Top  to  Bopom  Transparency  Using  the  Meta-­‐Scrum”,  AgileJournal   •  “All-­‐Out  OrganizaAonal  Scrum  as  an  InnovaAon  Value  Chain”,  IEEE