Your SlideShare is downloading. ×
"Managing software development" by Peter Bell
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

"Managing software development" by Peter Bell

2,042
views

Published on

Published in: Technology, Business

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,042
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
11
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Managing Software Development @PeterBell SVP EngineeringWednesday, May 16, 12
  • 2. Deliberate discovery Measuring scope Estimates and commitments Managing the backlog Defining "Done" Iterative vs incrementalAgendaWednesday, May 16, 12
  • 3. Deliberate DiscoveryWednesday, May 16, 12
  • 4. Iteration 0: Beyond story de-compositionDeliberate discoveryWednesday, May 16, 12
  • 5. Iteration 0: Reducing riskDeliberate discoveryWednesday, May 16, 12
  • 6. Iteration 0: Dimensions of riskDeliberate discoveryWednesday, May 16, 12
  • 7. Takeaways: Gant charts suck Focus on risk - Modeling - Tech spikes - ProcessDeliberate discoveryWednesday, May 16, 12
  • 8. Measuring ScopeWednesday, 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 countMeasuring scopeWednesday, May 16, 12
  • 10. Takeaways: Trend towards story countsMeasuring scopeWednesday, May 16, 12
  • 11. Estimates and CommitmentsWednesday, 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 probabilityWednesday, May 16, 12
  • 14. AlternativesEstimatesWednesday, May 16, 12
  • 15. When estimate?EstimatesWednesday, May 16, 12
  • 16. Takeaways: Don’t estimate Estimate != commitment Investment based budgetingEstimatesWednesday, May 16, 12
  • 17. Managing the BacklogWednesday, May 16, 12
  • 18. The problem: the shrinking storyBacklogWednesday, May 16, 12
  • 19. Avoid the problem: Small backlog, lean, WIP limitsBacklogWednesday, May 16, 12
  • 20. Manage the problem: Story mapsBacklogWednesday, May 16, 12
  • 21. Manage the problem: Magic/affinity estimatingBacklogWednesday, May 16, 12
  • 22. Takeaways: WIP limits Bigger stories Story maps Magic/affinity estimatingBacklogWednesday, May 16, 12
  • 23. Defining “Done”Wednesday, May 16, 12
  • 24. How do you “define Done”?Defining Done: Q&AWednesday, May 16, 12
  • 25. The three C’s card, conversation, confirmationDefining DoneWednesday, May 16, 12
  • 26. The fourth “C” cucumberDefining DoneWednesday, May 16, 12
  • 27. Problems with “flow”Defining DoneWednesday, May 16, 12
  • 28. Takeaways: Pre-agreed ExecutableDefining DoneWednesday, May 16, 12
  • 29. Iterative vs IncrementalWednesday, May 16, 12
  • 30. Incremental is greatIterative vs. incrementalWednesday, May 16, 12
  • 31. Iterative is betterIterative vs. incrementalWednesday, May 16, 12
  • 32. Iterative dev with incremental estimateIterative vs. incrementalWednesday, May 16, 12
  • 33. Deliberate discovery Measuring scope Estimates and commitments Managing the backlog Defining "Done" Iterative vs incremental @PeterBellManaging s/w development SVP EngineeringWednesday, May 16, 12