Posts

Showing posts with the label velocity

Respect the Team's Capacity

Image
Many times I have watched scrum teams ignore their historic capacity and proceed to add more work than they can possibly do to a sprint. Sometimes this is because a manager insists they include " stretch goals " in the sprint. Bad idea! Other times it's coming from the product owner who is being pressed by the business to deliver multiple features in a short time frame. This simply won't work. If you have a stable scrum team, made up of regular team members who do not switch out to other teams or work, you can determine their capacity by watching their velocity. If they commit to 100 story points of work but consistently deliver around 70 story points, then you have your capacity. The only way to increase their capacity is to increase the team size, which itself presents problems. When you add members to an established team, two things happen. First, the team overall can slow down as the new members figure things out and the team relearns how to work together. Second,...

Watch Out For Stretch Goals

When a Scrum team plans a sprint, they should do so with their velocity in mind. Velocity, in the context of Scrum, refers to the average number of story points a team has completed in past sprints. This metric serves as a reliable gauge of the team's capacity and should guide the amount of work planned for each sprint. Assuming the team has been working together for a while using the Scrum methodology, their historical velocity provides a realistic benchmark for future sprints. Planning sprints based on velocity ensures that teams do not overcommit or undercommit. Overcommitting by adding more work than what the team's velocity supports can lead to incomplete sprints, while undercommitting may result in underutilization of the team's potential. It is essential to strike a balance, and the team's average velocity helps achieve that balance. Temptation to include additional work beyond the team's velocity often arises, particularly from product owners who may see str...

Essential Scrum Metrics

Image
Some of my most rewarding professional experiences have been in leading teams through Agile transformations, adopting scrum. I've guided not only engineering teams through this transition, but even business and operations groups such as the archivists at a major media company. Very early at a publishing company a supervisor told me that "we won't do Agile" because people with our brands "need deadlines." He believed that Agile meant 'loosey-goosey' and inefficient. He also believed that we wouldn't get good metrics from a scrum team. That's definitely not the case, and in this piece I'll provide a brief overview of 3 metrics that I believe should be observed and reported. First, the sprint and release burndown will provide a view of the team's progress at a glance. This chart is a representation of the effort remaining over a period of time, and if updated on a daily basis it can help the scrum master to predict whether the team will ...

Individual Velocity in Scrum

Image
Early on in a brief stint as a project manager with a startup in New York, the product manager told me we needed to track individual velocities on the team. We had only just begun an Agile transformation, with me as the Scrum Master and her as the Product owner. She said it was just for our own tracking purposes, but having been told before by someone in senior management that he wanted to know which of the developers were 'slacking off,' I knew why she was really asking. The short answer to a request for individual velocity tracking, in an Agile environment, is ‘ no .’ This is actually a big no-no, for at least a couple of reasons. First, story points (or whatever method is used to weigh effort on user stories) are not precise. A team might look at a story and call it a ‘5’ (using Fibonacci, considering ‘8’ the largest) when it turns out to be a ‘3.’ Another ‘5’ could turn out to be an ‘8’. In the first case, the developer could end up looking like a whiz. In t...