DDevelopment & Design

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!

Kiedyś programista, obecnie PM i ewangelista metod zwinnych.

— Previous article

Confitura 2013 afterthoughts

Next article —

Nasze zdjęcia z planu filmowego

You May Also Like
DDevelopment & Design

Open IMS Core Mr interface

Open IMS Core does’t have standard way to define connection to MRF (Media Resource Function) on Mr interface.In IMS Mr interface is based on SIP and is similar to ISC used by Application Server (AS). Because of that we can define MRF as IMS AS and just add Wildcard PSI that has trigger on that AS. That [...]
DDevelopment & Design

Multi phased processing in scala

Last time in our project we had to add progress bar for visualization of long time running process. Process was made of a few phases and we had to print in which phase we currently are. In first step we conclude that we need to create a class of Progre...
DDevelopment & Design

Grails with Spock unit test + IntelliJ IDEA = No thread-bound request found

During my work with Grails project using Spock test in IntelliJ IDEA I've encountered this error:

java.lang.IllegalStateException: No thread-bound request found: Are you referring to request attributes outside of an actual web request, or processing a request outside of the originally receiving thread? If you are actually operating within a web request and still receive this message, your code is probably running outside of DispatcherServlet/DispatcherPortlet: In this case, use RequestContextListener or RequestContextFilter to expose the current request.
 at org.springframework.web.context.request.RequestContextHolder.currentRequestAttributes(RequestContextHolder.java:131)
 at org.codehaus.groovy.grails.plugins.web.api.CommonWebApi.currentRequestAttributes(CommonWebApi.java:205)
 at org.codehaus.groovy.grails.plugins.web.api.CommonWebApi.getParams(CommonWebApi.java:65)
... // and few more lines of stacktrace ;)

It occurred when I tried to debug one of test from IDEA level. What is interesting, this error does not happen when I'm running all test using grails test-app for instance.

So what was the issue? With little of reading and tip from Tomek Kalkosiński (http://refaktor.blogspot.com/) it turned out that our test was missing @TestFor annotation and adding it solved all problems.

This annotation, according to Grails docs (link), indicates Spock what class is being tested and implicitly creates field with given type in test class. It is somehow strange as problematic test had explicitly and "manually" created field with proper controller type. Maybe there is a problem with mocking servlet requests?