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.

Managing Projects/Releases using Lean/Agile techniques

4,819 views

Published on

Learn how to plan, manage and measure Projects/Releases using Lean/Agile techniques
Emphasis on visibility, estimation techniques, different approaches to commitments and buffering.

Published in: Technology

Managing Projects/Releases using Lean/Agile techniques

  1. 1. Managing Projects/Releases<br />Using Lean/Agile Techniques<br />Yuval Yeret<br />Lean/Kanban/Agile Coach @ AgileSparks<br />
  2. 2. Brief Intro<br />AgileSparksis an elite firm focused entirely on helping companies improve their product development operations, by leveraging Lean/Agile/Scrum thinking and techniques. Find us at www.agilesparks.com<br />Yuval Yeret – Lean/Kanban/Agile Consultant/Coach, coming from R&D leadership background, specializing in Kanban and scaling agile through Lean. <br />
  3. 3. Agenda<br />Agile Release Planning in the Real world<br />Managing Agile Releases<br />Agile End Game<br />Agile Program/Release Trains<br />Measuring Agile Release<br />
  4. 4. Agile has no Buffers<br />Must Scope<br />4<br />Average<br />Velocity?<br />Finish Date<br />Planned Capacity?<br />Priority<br />Worst case Velocity<br />
  5. 5. “In Agile the Team Commits”<br /><ul><li>“As a manager, I cannot commit”
  6. 6. “I cannot commit to Scope/Timeline, I’m Agile!”</li></li></ul><li>Commitments<br />
  7. 7. “There are no<br />Buffers in Agile”<br />TASK<br />
  8. 8. Fit Scope to Timeline<br />8<br />Worst<br />Average<br />
  9. 9. Fit Timeline to Scope<br />Stretch Scope<br />Must Scope<br />9<br />Stretch Velocity<br />Finish Date<br />Priority<br />Safe/ Committed Velocity<br />
  10. 10. The Chicken and Egg problem(aka Bootstrapping Velocity…)<br />http://www.truthandscience.net/chicken_or_egg.%202gif.jpg<br />
  11. 11. History 101<br />Compare current features/stories to previous releases (even if before Agile)<br />Look at actual effort and time of previous releases<br />Derive approximate Velocity<br />
  12. 12. Flash Forward<br />Plan the few upcoming Features/Stories in detail<br />Guesstimate the ratio between estimate time and actual time on tasks (Ideal to Actual)<br />Derive the velocity<br />
  13. 13. Team Commitments within Release Commitments<br />13<br />Committed scope<br />DELIVERED<br />Teams commit to what they CAN<br />BUT stretch and able to close gap<br />Finish Date<br />Trend shows Exceeding release stretch goals!!!<br />Priority<br />Back on track<br />Committed Scope in risk!!!<br />
  14. 14. Managing the Release<br />
  15. 15. Release Burnup<br />https://wiki.rallydev.com/display/rlyhlp/Release+Burnup+Chart<br />
  16. 16. Release Cumulative Flow<br />https://wiki.rallydev.com/display/rlyhlp/Release+Cumulative+Flow+Chart<br />
  17. 17. Release Burndown<br />https://wiki.rallydev.com/display/rlyhlp/Release+Burn+Down+Chart<br />
  18. 18. Risk Burndown<br />http://leadinganswers.typepad.com/leading_answers/2007/09/agile-risk-mana.html<br />
  19. 19. Tracking Dark Matter<br />David Anderson - http://agilemanagement.net/index.php/Blog/revealing_dark_matter/<br />
  20. 20. AgileEVM<br />Courtesy Amdocs Process Eng group<br />
  21. 21. The Endgame<br />
  22. 22. Alistair Cockburn<br />
  23. 23.
  24. 24.
  25. 25. How do we minimize Buffering for the next Project/Release?<br />
  26. 26. Better Predictability<br />Must Scope<br />26<br />Finish Date<br />Priority<br />
  27. 27. Stable Velocity<br />
  28. 28. Which is Better?<br />
  29. 29. Managing Agile Programs<br />
  30. 30.
  31. 31.
  32. 32.
  33. 33. Focus on a “Train service” rather than “Taxis”<br />“Project” requirements delivered on main product releases<br />Product Roadmap delivered on main product releases<br />Key? Delivering a frequent and reliable main product release. <br />Build Quality In – Focus on making these releases bulletproof<br />Improve Customer Satisfaction<br />Solution for “Give it to me on the stable release”<br />How to escape this Vicious Cycle?<br />
  34. 34. Product or Project<br />Release<br />Iteration<br />Story<br />
  35. 35. Measures for effective Releases<br />
  36. 36.
  37. 37. Release Cost Breakdown Trend<br />Reduced overheads lead to more budget for New Features<br />
  38. 38. Ask us how<br />“Managing Agile Projects/Programs” Workshop – Coming Soon…<br />(Contact me to be notified about next public workshop)<br />yuval@agilesparks.com<br />@yuvalyeret<br />www.linkedin.com/in/yuvalyeret<br />http://www.slideshare.net/yyeret/<br />

×