software engineering process i

13
Copyright © 2012-2014 by Mark J. Sebern Software Engineering Process I SE-2800-06 Product backlog, estimation, velocity

Upload: beck

Post on 14-Jan-2016

39 views

Category:

Documents


3 download

DESCRIPTION

Software Engineering Process I. SE-2800-06 Product backlog, estimation, velocity. Product Backlog Items. What are these PBI types?. Product Backlog Characteristics. Detailed appropriately Emergent Estimated Prioritized (ordered? positioned?) Estimated size vs position?. - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Software Engineering Process I

Copyright © 2012-2014 by Mark J. Sebern

Software Engineering

Process ISE-2800-06

Product backlog, estimation, velocity

Page 2: Software Engineering Process I

Copyright © 2012-2014 by Mark J. Sebern

Product Backlog Items

What are these PBI

types?

Page 3: Software Engineering Process I

Copyright © 2012-2014 by Mark J. Sebern

Product Backlog Characteristics

• Detailed appropriately

• Emergent

• Estimated

• Prioritized (ordered? positioned?)

• Estimated size vs position?

Page 4: Software Engineering Process I

Copyright © 2012-2014 by Mark J. Sebern

Grooming the Backlog• Grooming activities

• Creating/refining, estimating, prioritizing

• Who makes the decisions?

• Who else is involved?

• When is grooming done?

• How much time to allocate to grooming?

Page 5: Software Engineering Process I

Copyright © 2012-2014 by Mark J. Sebern

Definition of Ready• Ensure top PBI's are "good enough"

to take action on (be incorporated into a sprint)

What should be included in “good enough”?

Page 6: Software Engineering Process I

Copyright © 2012-2014 by Mark J. Sebern

Definition of Ready• Ensure top PBI's are "good enough"

to take action on (be incorporated into a sprint)

• Business value articulated

• Details understood

• Dependencies not blocking

• Staffing OK

• Estimated, small enough

• Clear criteria• Acceptance• Performance• Demo conditions (!)

Page 7: Software Engineering Process I

Copyright © 2012-2014 by Mark J. Sebern

Ch. 7: Estimation in Scrum

Estimation target Size unit

Product backlog item (PBI)

Task

Story points

Ideal hours

More on task estimation later . . .

Page 8: Software Engineering Process I

Copyright © 2012-2014 by Mark J. Sebern

Estimation Concepts

• What is meant by these concepts?

• Estimate as a team

• Estimates are not commitments

• Focus on accuracy, not precision

• Use relative versus absolute sizes

Page 9: Software Engineering Process I

Copyright © 2012-2014 by Mark J. Sebern

Planning PokerWhat is this all about?

•Consensus•Expert opinion

•Discussion•Relative size•Accurate grouping

•Use of historyHow do we play?

Why the funny values? 0, ½, 1, 2, 3, 5, 8, 13, 20, 40, 100,

∞, ?

Page 10: Software Engineering Process I

Copyright © 2012-2014 by Mark J. Sebern

Velocity

• What is it?

• How is it calculated?

• How do we use the velocity value?

• For planning?

• As a diagnostic?

Page 11: Software Engineering Process I

Copyright © 2012-2014 by Mark J. Sebern

Review

• Product Backlog Items• Item types used at MSOE• Characteristics of PBIs: DEEP• Grooming, ensuring PBIs are ready• Estimation: Planning Poker• Velocity

Page 12: Software Engineering Process I

Copyright © 2012-2014 by Mark J. Sebern

Checkpoint• Turn to your

partner…

• What is good about Scrum planning?

• What seems not so good?

• What questions do you have?

Page 13: Software Engineering Process I

Copyright © 2012-2014 by Mark J. Sebern

Estimation Exercise• In your team:

• Choose a PBI to estimate

• Discuss the item

• Each estimator privately chooses a card

• Show all cards at once

• Check for consensus; repeat if none