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

New HTTP Logger Grails plugin

I've wrote a new Grails plugin - httplogger. It logs:

  • request information (url, headers, cookies, method, body),
  • grails dispatch information (controller, action, parameters),
  • response information (elapsed time and body).

It is mostly useful for logging your REST traffic. Full HTTP web pages can be huge to log and generally waste your space. I suggest to map all of your REST controllers with the same path in UrlMappings, e.g. /rest/ and configure this plugin with this path.

Here is some simple output just to give you a taste of it.

17:16:00,331 INFO  filters.LogRawRequestInfoFilter  - 17:16:00,340 INFO  filters.LogRawRequestInfoFilter  - 17:16:00,342 INFO  filters.LogGrailsUrlsInfoFilter  - 17:16:00,731 INFO  filters.LogOutputResponseFilter  - >> #1 returned 200, took 405 ms.
17:16:00,745 INFO filters.LogOutputResponseFilter - >> #1 responded with '{count:0}'
17:18:55,799 INFO  filters.LogRawRequestInfoFilter  - 17:18:55,799 INFO  filters.LogRawRequestInfoFilter  - 17:18:55,800 INFO  filters.LogRawRequestInfoFilter  - 17:18:55,801 INFO  filters.LogOutputResponseFilter  - >> #2 returned 404, took 3 ms.
17:18:55,802 INFO filters.LogOutputResponseFilter - >> #2 responded with ''

Official plugin information can be found on Grails plugins website here: http://grails.org/plugins/httplogger or you can browse code on github: TouK/grails-httplogger.