SCRUM Sprint Planning Gone Wrong

One of the things that is a hallmark of the SCRUM method of Agile development is that you have a unit of time during which you commit to accomplishing some amount of work before that unit of time has elapsed. In order to commit to how much work should be accomplished during the “sprint”, all members of the team meet at the beginning of each sprint for a sprint planning meeting.

The purpose of a sprint planning meeting is to estimate the difficulty and complexity of completing each task that is in your list of potential work items. At the end of sprint planning, a subset of these items will be picked as the set of items that the team commits to completing by the end of the sprint. While this all sounds straightforward and simple to most people, I have been in some sprint planning meetings that lose their focus.

Since there are typically quite a few items to estimate during a sprint planning meeting, time spent discussing implementation and testing details should be kept to a minimum. The SCRUM Master is responsible for ensuring the meeting moves at a reasonable timeframe so that the sprint planning meeting does not exceed the scheduled timeframe, typically 1 hour.

There have been several sprint planning meetings I have attended that had members of the team determining how the issue would be resolved during the meeting, instead of just estimating the difficulty and complexity of the task. It would not be unusual to still be discussing the merits of the first task more than 30 minutes into the meeting. Unsurprisingly, the projects this team was supposed to deliver were always behind schedule if they were ever considered feature-complete.

Tags:
comments powered by Disqus

Related Posts

Compass Makes Writing CSS Fun Again

One of the things that has always annoyed me about web development is that writing CSS generally becomes a task that has a major lack of the features that you would expect in a programming language, even one as simple as JavaScript. These features that would be wonderful to have when working with CSS are the ability to use variables to define a set of basic colors that are in use across the site in one place, and then use the variable name throughout the stylesheet.

Read More

Laravel Removed The QuickStart For Version 5

To start out, I want to be clear that what follows should not be interpreted to be a criticism of the software framework that those that work on Laravel publish, nor an indictment of open-source software as a whole. Rather, it is a look at how some projects, open or closed source make it harder than it should be for new users/developers to utilize their terrific products. It seems experts conveniently “forget” the tips and tricks and tribulations it takes to learn a new technology, covering it all with, “It’s just so easy”.

Read More

Another Micro-Optimization Provides Useless Results

One of the things to remember about performance optimizations performed in isolation is that their results are rarely representative of real-world performance results. This article outlines the “findings” of the students at a couple of Canadian universities, and comes to the conclusion that string concatenation in memory is slower than writing the same total number of bytes to disk, one after the other. String concatenation is a slow and CPU-heavy operation.

Read More