"Managing software development" by Peter Bell
2 likes1,893 views
This document summarizes a presentation on managing software development. It discusses topics like deliberate discovery during iteration 0 to reduce risk, using story counts to measure scope, making estimates to inform budgeting decisions but not as commitments, using techniques like WIP limits and story maps to manage backlogs, defining "Done" with pre-agreed upon criteria, and taking an iterative development approach with incremental estimates. The overall presentation provides guidance on processes and practices for effectively planning and managing a software development project.
"Managing software development" by Peter Bell
- 1. Managing Software Development @PeterBell SVP Engineering Wednesday, May 16, 12
- 2. Deliberate discovery Measuring scope Estimates and commitments Managing the backlog Defining "Done" Iterative vs incremental Agenda Wednesday, May 16, 12
- 3. Deliberate Discovery Wednesday, May 16, 12
- 4. Iteration 0: Beyond story de-composition Deliberate discovery Wednesday, May 16, 12
- 5. Iteration 0: Reducing risk Deliberate discovery Wednesday, May 16, 12
- 6. Iteration 0: Dimensions of risk Deliberate discovery Wednesday, May 16, 12
- 7. Takeaways: Gant charts suck Focus on risk - Modeling - Tech spikes - Process Deliberate discovery Wednesday, May 16, 12
- 8. Measuring Scope Wednesday, May 16, 12
- 9. Evolving estimating • Ideal days (load factor) • Story points • 1,2,3,5,8 • 0? • 10,20,30,51? • T-shirt sizes • Story count Measuring scope Wednesday, May 16, 12
- 10. Takeaways: Trend towards story counts Measuring scope Wednesday, May 16, 12
- 11. Estimates and Commitments Wednesday, May 16, 12
- 12. • Good reasons to estimate: • Go/no go based on cost • Market window • ROI comparison • Bad reasons to estimate • Because . . . • Ask whether: • Time, price or both? • Will estimate matter? • Accuracy required? Why Estimate? Wednesday, May 16, 12
- 13. Estimates and probability Wednesday, May 16, 12
- 15. When estimate? Estimates Wednesday, May 16, 12
- 16. Takeaways: Don’t estimate Estimate != commitment Investment based budgeting Estimates Wednesday, May 16, 12
- 17. Managing the Backlog Wednesday, May 16, 12
- 18. The problem: the shrinking story Backlog Wednesday, May 16, 12
- 19. Avoid the problem: Small backlog, lean, WIP limits Backlog Wednesday, May 16, 12
- 20. Manage the problem: Story maps Backlog Wednesday, May 16, 12
- 21. Manage the problem: Magic/affinity estimating Backlog Wednesday, May 16, 12
- 22. Takeaways: WIP limits Bigger stories Story maps Magic/affinity estimating Backlog Wednesday, May 16, 12
- 23. Defining “Done” Wednesday, May 16, 12
- 24. How do you “define Done”? Defining Done: Q&A Wednesday, May 16, 12
- 25. The three C’s card, conversation, confirmation Defining Done Wednesday, May 16, 12
- 26. The fourth “C” cucumber Defining Done Wednesday, May 16, 12
- 27. Problems with “flow” Defining Done Wednesday, May 16, 12
- 28. Takeaways: Pre-agreed Executable Defining Done Wednesday, May 16, 12
- 29. Iterative vs Incremental Wednesday, May 16, 12
- 30. Incremental is great Iterative vs. incremental Wednesday, May 16, 12
- 31. Iterative is better Iterative vs. incremental Wednesday, May 16, 12
- 32. Iterative dev with incremental estimate Iterative vs. incremental Wednesday, May 16, 12
- 33. Deliberate discovery Measuring scope Estimates and commitments Managing the backlog Defining "Done" Iterative vs incremental @PeterBell Managing s/w development SVP Engineering Wednesday, May 16, 12