Home

Quick Access

Contents are grouped into different sections a.k.a Books. See all books here.

Blogs

 

Edit this page | Go to Top

Scrum and XP from the Trenches


Scrum and XP from the Trenches - 2nd Edition Henrik Kniberg

The book can be downloaded for free from here.

Table of Content

Forward

Nokia Requirements for Iterative Development

Part One - Intro

Part Two - How we do product backlogs

Product Backlog Example

ID Name Estimate How to demo Notes
1 Deposit 5 Log in, open deposit page, deposit €10, go to my balance page and check that it has increased by €10 Need a UML sequence diagram. No need to worry about encryption for now.
2 See your own transaction history 8 Log in, click on “transactions”. Do a deposit. Go back to transactions, check that the new deposit shows up. Use paging to avoid large DB queries. Design similar to view users page.

How we keep the product backlog at a business level

Part Three - How we prepare for sprint planning

Part Four - How we do sprint planning

Why the product owner has to attend

Why quality is not negotiable

Sprint planning meetings that drag on and on…

Scrum is like any other tool – you can use a hammer to build something or to smash your thumb. Either way, don’t blame the tool.

Sprint-planning-meeting agenda

Backlog Refinement

   
10:30-11:30 Team time-estimates, and breaks down items as necessary. Product owner updates importance ratings as necessary. Items are clarified. “How to demo” is filled in for all high-importance items.

Sprint Planning

   
13:30-14:00 Product owner goes through sprint goal and summarizes product backlog. Demo place, date, and time is set.
14:00-15:00 Team selects stories to be included in sprint. Do velocity calculations as a reality check.
15:00-16:00 Select time and place for daily scrum (if different from last sprint). Further breakdown of stories into tasks.

Defining the sprint length

Short sprint Long sprint
short feedback cycle 
more frequent deliveries 
more frequent customer feedback 
less time spent running in the wrong direction 
learn and improve faster
The team gets more time to build up momentum 
they get more room to recover from problems and still make the sprint goal 
you get less overhead in terms of sprint planning meetings, demos, etc.
Product owners like Devlopers like

Defining the sprint goal

Deciding which stories to include in the sprint

This raises two questions:

1. How can product owner affect which stories make it to the sprint?

   
The product owner is disappointed that story D won’t be included in the sprint. What are his options during the sprint planning meeting?
Add D and remove C.
Reduce the scope of A.
Split the scope of A.

2. How does the team decide which stories to include in the sprint?

1) Gut Feel
2) Velocity calculations

Which estimating technique do we use?

Why we use index cards