Managing Projects/Releases using Lean/Agile techniques
Download as PPTX, PDF9 likes2,776 views
The document discusses managing projects and releases using lean and agile techniques, emphasizing the importance of agile release planning, team commitments, and measuring agile release velocity. It highlights the need for minimizing buffers and maintaining predictability while focusing on product roadmaps and customer satisfaction. The resource also promotes an upcoming workshop on managing agile projects and programs.
Managing Projects/Releases using Lean/Agile techniques
- 1. Managing Projects/ReleasesUsing Lean/Agile TechniquesYuval YeretLean/Kanban/Agile Coach @ AgileSparks
- 2. Brief IntroAgileSparksis 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.comYuval Yeret – Lean/Kanban/Agile Consultant/Coach, coming from R&D leadership background, specializing in Kanban and scaling agile through Lean.
- 3. AgendaAgile Release Planning in the Real worldManaging Agile ReleasesAgile End GameAgile Program/Release TrainsMeasuring Agile Release
- 4. Agile has no BuffersMust Scope4AverageVelocity?Finish DatePlanned Capacity?PriorityWorst case Velocity
- 5. “In Agile the Team Commits”“As a manager, I cannot commit”
- 6. “I cannot commit to Scope/Timeline, I’m Agile!”Commitments
- 7. “There are noBuffers in Agile”TASK
- 8. Fit Scope to Timeline8WorstAverage
- 9. Fit Timeline to ScopeStretch ScopeMust Scope9Stretch VelocityFinish DatePrioritySafe/ Committed Velocity
- 10. The Chicken and Egg problem(aka Bootstrapping Velocity…)http://www.truthandscience.net/chicken_or_egg.%202gif.jpg
- 11. History 101Compare current features/stories to previous releases (even if before Agile)Look at actual effort and time of previous releasesDerive approximate Velocity
- 12. Flash ForwardPlan the few upcoming Features/Stories in detailGuesstimate the ratio between estimate time and actual time on tasks (Ideal to Actual)Derive the velocity
- 13. Team Commitments within Release Commitments13Committed scopeDELIVEREDTeams commit to what they CANBUT stretch and able to close gapFinish DateTrend shows Exceeding release stretch goals!!!PriorityBack on trackCommitted Scope in risk!!!
- 19. Tracking Dark MatterDavid Anderson - http://agilemanagement.net/index.php/Blog/revealing_dark_matter/
- 20. AgileEVMCourtesy Amdocs Process Eng group
- 21. The Endgame
- 25. How do we minimize Buffering for the next Project/Release?
- 26. Better PredictabilityMust Scope26Finish DatePriority
- 27. Stable Velocity
- 28. Which is Better?
- 33. Focus on a “Train service” rather than “Taxis”“Project” requirements delivered on main product releasesProduct Roadmap delivered on main product releasesKey? Delivering a frequent and reliable main product release. Build Quality In – Focus on making these releases bulletproofImprove Customer SatisfactionSolution for “Give it to me on the stable release”How to escape this Vicious Cycle?
- 35. Measures for effective Releases
- 37. Release Cost Breakdown TrendReduced overheads lead to more budget for New Features
- 38. Ask us how“Managing Agile Projects/Programs” Workshop – Coming Soon…(Contact me to be notified about next public workshop)yuval@agilesparks.com@yuvalyeretwww.linkedin.com/in/yuvalyerethttp://www.slideshare.net/yyeret/