Agile Zone is brought to you in partnership with:

By day I'm a build and release engineer in London, but by night I'm a normal person! If anyone ever asks me what I do, I usually generarlise and say "I'm in I.T." and then check to see if they've already stopped listening. When I'm not working or blogging I can be found playing rugby or cycling around the countryside on my bike, in an attempt to keep fit and fool myself into thinking I'm still young. James is a DZone MVB and is not an employee of DZone and has posted 54 posts at DZone. You can read more from them at their website. View Full User Profile

Changes to Scrum

  • submit to reddit

Ken Schwaber and Jeff Sutherland, the original guys who came up with the whole concept of Scrum back in about 1995 have recently posted a video on the interwebs, explaining some changes to the scrum model based on their experiences over the last few years. The video can be found here.

If you don’t have the time to watch the video, here’s my summary of the bits I found most interesting:

1. We should do more prep before our sprint planning, so that all stories are sufficiently prepared before the sprint planning session. This has come about because many sprint planning sessions take many hours. They have suggested having a “ready” status for backlog items that are ready to be discussed in the planning session.

2. We should always have a sprint goal, and during our daily stand-ups we should talk about how we are helping the team progress towards our sprint goal

3. We should talk about “value” in our sprint reviews. With hindsight, did we deliver as much value as we could have? If not, what could we do next time to ensure we deliver greater value?

Published at DZone with permission of James Betteley, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)


Luka Matovic replied on Mon, 2014/07/28 - 1:24am

I couldn't agree more. At my current company, we've adopted a pre-sprint planning  work flow. When the end of the sprint approaches, the PM has some user stories prepared in a backlog. Scrum master sends an email with a link to a google spreadsheet doc, containing listed user stories ready to be discussed. Then all developers, back and frontenders, testers read for them-selves those USs and write down questions about things not so nicely described, things they didn't understand or just some advice to the PM. After that pm goes through all these questions and tries to answer them and clarify the situation in a user story. This causes that when we all come to a sprint planning there are no more (or very little) things to discuss about requirements in the US. Symptomatic is that (in our case) all 6 of us ask 80% of the same questions :) Good thing to notice after few sprints planned like  this is that PMs now see what is important to us, developers and can focus on defining those things more clearly.

Luka Matovic

Senior Java Developer

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.