1 / 38

Managing Projects/Releases Using Lean/Agile Techniques

Managing Projects/Releases Using Lean/Agile Techniques. Agenda. Agile Release Planning in the Real world Managing Agile Releases Agile End Game Agile Program/Release Trains Measuring Agile Release. Agile has no Buffers. Average Velocity?. Must Scope. Finish Date. Planned Capacity?.

Download Presentation

Managing Projects/Releases Using Lean/Agile Techniques

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Managing Projects/Releases Using Lean/Agile Techniques

  2. Agenda • Agile Release Planning in the Real world • Managing Agile Releases • Agile End Game • Agile Program/Release Trains • Measuring Agile Release

  3. Agile has no Buffers Average Velocity? Must Scope Finish Date Planned Capacity? Priority Worst case Velocity

  4. “In Agile the Team Commits” • “As a manager, I cannot commit” • “I cannot commit to Scope/Timeline, I’m Agile!”

  5. Commitments

  6. Buffers in Agile” “There are no TASK

  7. Fit Scope to Timeline Worst Average

  8. Fit Timeline to Scope Stretch Scope Stretch Velocity Must Scope Finish Date Priority Safe/ Committed Velocity

  9. The Chicken and Egg problem(aka Bootstrapping Velocity…) http://www.truthandscience.net/chicken_or_egg.%202gif.jpg

  10. History 101 • Compare current features/stories to previous releases (even if before Agile) • Look at actual effort and time of previous releases • Derive approximate Velocity

  11. Flash Forward • Plan the few upcoming Features/Stories in detail • Guesstimate the ratio between estimate time and actual time on tasks (Ideal to Actual) • Derive the velocity

  12. Team Commitments within Release Commitments Committed scope DELIVERED Teams commit to what they CAN BUT stretch and able to close gap Finish Date Trend shows Exceeding release stretch goals!!! Priority Back on track Committed Scope in risk!!!

  13. Managing the Release

  14. Release Burnup https://wiki.rallydev.com/display/rlyhlp/Release+Burnup+Chart

  15. Release Cumulative Flow https://wiki.rallydev.com/display/rlyhlp/Release+Cumulative+Flow+Chart

  16. Release Burndown https://wiki.rallydev.com/display/rlyhlp/Release+Burn+Down+Chart

  17. Risk Burndown http://leadinganswers.typepad.com/leading_answers/2007/09/agile-risk-mana.html

  18. Tracking Dark Matter David Anderson - http://agilemanagement.net/index.php/Blog/revealing_dark_matter/

  19. AgileEVM Courtesy Amdocs Process Eng group

  20. The Endgame

  21. Alistair Cockburn

  22. How do we minimize Buffering for the next Project/Release?

  23. Better Predictability Must Scope Finish Date Priority

  24. Stable Velocity

  25. Which is Better?

  26. Managing Agile Programs

  27. How to escape this Vicious Cycle? • Focus on a “Train service” rather than “Taxis” • “Project” requirements delivered on main product releases • Product Roadmap delivered on main product releases • Key? Delivering a frequent and reliable main product release. • Build Quality In – Focus on making these releases bulletproof • Improve Customer Satisfaction • Solution for “Give it to me on the stable release”

  28. Product or Project Release Iteration Story

  29. Measures for effective Releases

  30. Release Cost Breakdown Trend Reduced overheads lead to more budget for New Features

  31. Ask us how “Managing Agile Releases” Workshop – Coming Soon… yuval@agilesparks.com @yuvalyeret www.linkedin.com/in/yuvalyeret Get the slides at http://www.slideshare.net/yyeret/

More Related