1 / 13

Software Engineering Process I

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

beck
Download Presentation

Software Engineering Process I

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Software Engineering Process I • SE-2800-06 • Product backlog, estimation, velocity

  2. Product Backlog Items What are these PBI types?

  3. Product Backlog Characteristics • Detailed appropriately • Emergent • Estimated • Prioritized (ordered? positioned?) • Estimated size vs position?

  4. 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?

  5. 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”?

  6. 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 (!)

  7. Ch. 7: Estimation in Scrum Story points Ideal hours More on task estimation later . . .

  8. 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

  9. Planning Poker • What is this all about? • Consensus • Expert opinion • Discussion • Relative size • Accurate grouping • Use of history Why the funny values?0, ½, 1, 2, 3, 5, 8, 13, 20, 40, 100, ∞, ? How do we play?

  10. Velocity • What is it? • How is it calculated? • How do we use the velocity value? • For planning? • As a diagnostic?

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

  12. Checkpoint • Turn to your partner… • What is good about Scrum planning? • What seems not so good? • What questions do you have?

  13. Estimation Exercise Don’t lose your card deck! • 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

More Related