Commitment in ScrumCommitment in Scrum

Short note taken long time ago from Henrik Kniberg’s slides about a few aspects of commitment in Scrum

This is a note to self. Note taken long ago from Scrum beyond trenches slides by Henrik Kniberg. Just for myself not to forget.

The sprint commitment – misconceptions

”We promise to achieve this goal”
“We promise to deliver all stories included in the sprint backlog”

I’ll repeat!. These are misconceptions!

 Team’s commitment to the product owner

We promise that:

“… we believe we can reach the sprint goal.”
“… we will do everything in our power to reach the sprint goal, and will let you know immediately if we no longer believe we can reach it.”
“… we believe that we can complete all stories included in the sprint backlog.”
“… we will demonstrate releasable code at the end of the sprint.”
“… if we fall behind schedule we will talk to you and, if necessary, remove the lowest priority stories first.”
“… if we get ahead of schedule, we will add stories to the sprint from the product backlog, in priority order.”
“… we will display our progress and status on a daily basis.”
“… every story that we do deliver is Done.”

Hmm, the opposite of misconceptions should be conceptions, right :D?

Your experience

Would you add any more to these lists? Do you have any experience being hit by wrongly understood commitment? Share!

You May Also Like

Devoxx 2012 review


I'm sitting in a train to Charleroi, looking through a window at the Denmark landscape, street lights flashing by, people comming home from work, getting out for a Friday night party, or having a family dinner. To my left, guys from SoftwareMill are playing cards.
I don't really see them. My mind is busy elsewhere, sorting out and processing last two days in Antwerp, where 3400 developers, from 41 different countries, listened to 200 different sessions at the Devoxx, AFAIK the biggest Java conference this year.