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

"Managing software development" by Peter Bell

on

  • 2,153 views

 

Statistics

Views

Total Views
2,153
Views on SlideShare
1,457
Embed Views
696

Actions

Likes
1
Downloads
9
Comments
0

3 Embeds 696

http://platform.cinchcast.com 691
http://www.linkedin.com 3
http://st.platform.cinchcast.com 2

Accessibility

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

"Managing software development" by Peter Bell "Managing software development" by Peter Bell Presentation Transcript

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