33
Managing Software Development @PeterBell SVP Engineering Wednesday, May 16, 12

"Managing software development" by Peter Bell

Embed Size (px)

DESCRIPTION

 

Citation preview

Page 1: "Managing software development" by Peter Bell

ManagingSoftware Development

@PeterBellSVP Engineering

Wednesday, May 16, 12

Page 2: "Managing software development" by Peter Bell

Agenda

Deliberate discoveryMeasuring scopeEstimates and commitmentsManaging the backlogDefining "Done"Iterative vs incremental

Wednesday, May 16, 12

Page 3: "Managing software development" by Peter Bell

DeliberateDiscovery

Wednesday, May 16, 12

Page 4: "Managing software development" by Peter Bell

Deliberate discovery

Iteration 0: Beyond story de-composition

Wednesday, May 16, 12

Page 5: "Managing software development" by Peter Bell

Deliberate discovery

Iteration 0: Reducing risk

Wednesday, May 16, 12

Page 6: "Managing software development" by Peter Bell

Deliberate discovery

Iteration 0: Dimensions of risk

Wednesday, May 16, 12

Page 7: "Managing software development" by Peter Bell

Deliberate discovery

Gant charts suckFocus on risk- Modeling- Tech spikes- Process

Takeaways:

Wednesday, May 16, 12

Page 8: "Managing software development" by Peter Bell

MeasuringScope

Wednesday, May 16, 12

Page 9: "Managing software development" by Peter Bell

Measuring scope

Evolving estimating

• Ideal days (load factor)

• Story points

• 1,2,3,5,8

• 0?

• 10,20,30,51?

• T-shirt sizes

• Story count

Wednesday, May 16, 12

Page 10: "Managing software development" by Peter Bell

Measuring scope

Trend towards story counts

Takeaways:

Wednesday, May 16, 12

Page 11: "Managing software development" by Peter Bell

EstimatesCommitments

and

Wednesday, May 16, 12

Page 12: "Managing software development" by Peter Bell

Why Estimate?

• 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?

Wednesday, May 16, 12

Page 13: "Managing software development" by Peter Bell

Estimates and probabilityWednesday, May 16, 12

Page 14: "Managing software development" by Peter Bell

Estimates

Alternatives

Wednesday, May 16, 12

Page 15: "Managing software development" by Peter Bell

Estimates

When estimate?

Wednesday, May 16, 12

Page 16: "Managing software development" by Peter Bell

Estimates

Don’t estimateEstimate != commitmentInvestment based budgeting

Takeaways:

Wednesday, May 16, 12

Page 17: "Managing software development" by Peter Bell

ManagingBacklog

the

Wednesday, May 16, 12

Page 18: "Managing software development" by Peter Bell

Backlog

The problem: the shrinking story

Wednesday, May 16, 12

Page 19: "Managing software development" by Peter Bell

Backlog

Avoid the problem: Small backlog, lean, WIP limits

Wednesday, May 16, 12

Page 20: "Managing software development" by Peter Bell

Backlog

Manage the problem: Story maps

Wednesday, May 16, 12

Page 21: "Managing software development" by Peter Bell

Backlog

Manage the problem: Magic/affinity estimating

Wednesday, May 16, 12

Page 22: "Managing software development" by Peter Bell

Backlog

WIP limits Bigger storiesStory mapsMagic/affinity estimating

Takeaways:

Wednesday, May 16, 12

Page 23: "Managing software development" by Peter Bell

Defining“Done”

Wednesday, May 16, 12

Page 24: "Managing software development" by Peter Bell

Defining Done: Q&A

How do you “define Done”?

Wednesday, May 16, 12

Page 25: "Managing software development" by Peter Bell

Defining Done

The three C’s

card, conversation, confirmation

Wednesday, May 16, 12

Page 26: "Managing software development" by Peter Bell

Defining Done

The fourth “C”

cucumber

Wednesday, May 16, 12

Page 27: "Managing software development" by Peter Bell

Defining Done

Problems with “flow”

Wednesday, May 16, 12

Page 28: "Managing software development" by Peter Bell

Defining Done

Pre-agreedExecutable

Takeaways:

Wednesday, May 16, 12

Page 29: "Managing software development" by Peter Bell

IterativeIncrementalvs

Wednesday, May 16, 12

Page 30: "Managing software development" by Peter Bell

Iterative vs. incremental

Incremental is great

Wednesday, May 16, 12

Page 31: "Managing software development" by Peter Bell

Iterative vs. incremental

Iterative is better

Wednesday, May 16, 12

Page 32: "Managing software development" by Peter Bell

Iterative vs. incremental

Iterative dev with incremental estimate

Wednesday, May 16, 12

Page 33: "Managing software development" by Peter Bell

Managing s/w development

Deliberate discoveryMeasuring scopeEstimates and commitmentsManaging the backlogDefining "Done"Iterative vs incremental

@PeterBellSVP Engineering

Wednesday, May 16, 12