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

Complex flows with Apache Camel

At work, we're mainly integrating services and systems, and since we're on a constant lookout for new, better technologies, ways to do things easier, make them more sustainable, we're trying to Usually we use Apache Camel for this task, which is a Swis...At work, we're mainly integrating services and systems, and since we're on a constant lookout for new, better technologies, ways to do things easier, make them more sustainable, we're trying to Usually we use Apache Camel for this task, which is a Swis...