Skip to main content

Story Points and the Heart of Scrum

Last week I wrote, "Story Points are not uncontroversial" and lo, and behold, not a week after I made the comment, I posted essentially the same arguments to the Scrum Development mailing list in response to question about how many man days are there in a story point. Dave Rooney of Mayford Technologies wrote back:
"I generally agree with Peter's points..., except that estimating any development effort in hours is a mistake, plain and simple. You are mistaking 'precision' with 'accuracy' in that case, and any estimation is bound to be incorrect.

"What you need to do is to measure the team's *actual* output, and feed that back into the measurements as the velocity. These measurements need to begin as soon as development starts, and need to be made continuously. That's the only way to introduce any accuracy into your estimates."
I think there are two perspectives here.

On the one hand, I'm totally in agreement with Dave that estimating in story points as an abstract unit is the right way to go and with his observation about the importance of measuring the team's actual output.

But on the other hand, Project Management is always about the Art of the Possible. Getting the project to a satisfactory conclusion under the circumstances, particularly if you are rescuing a project in crisis. I have seen a number of attempts to a implement a pure agile approach fail due to lack of flexibility on the part of the Agile champions or due to resistance from the team.

So we have stick to our principles: Continuous Improvement, Self-organization, Commitment Driven. Taking exactly what you can eat. Eliminate Impediments. These Principles define the practices at the Heart of Scrum. The Plan - Do - Review - Improve Sprint Cycle. A fixed length Sprint with a fixed (or at least predefined) team. A negotiated Sprint Contract between Product Owner and Team. A Definition of Done. If you're not doing these things, you're not doing Scrum.

We can comprimise on practices if we are true to our principles and to the heart of Scrum. User Stories are a practice. Story Points are a practice. We can use them or not if they make sense for our project. (They are also very good practices, and where I haven't used them from the beginning, I have migrated to them as the projects moved forward).

Once you start doing Scrum, the Scrum Master can start prodding in the team to adopt the Agile practices that fully unleash their potential. But I've written why a coach is more effective than a bulldozer and how it took the Team exactly one meeting to raise the contradiction of being told what to do while being told they are self-organizing. So compromise and accommodation is part of the game.

Which brings us to the project at hand. But that is tomorrow's post.

Comments

Popular posts from this blog

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

What is the role of a Business Analyst in Scrum?

When I teach a CSM class, my goal is that my participants go home delighted (and of course that they learn about Scrum, that they are motivated to do Scrum, and can pass the online CSM exam). So after every class, I ask for feedback, in particular what could I do to get a better score. And for the next class, I strive to implement or address two or three of the points raised by my participants.

One issue that was raised was unanswered questions. It is annoying to ask questions and not get answers! Time is limited, so it is not always possible to answer all questions, so I thought, why not answer them on my blog? So here goes, first question:
What is the role of a Business Analyst in Scrum? This question is a challenge because Scrum doesn't answer this question! Scrum is a simple, team-based framework for solving complex problems. The roles and ceremonies in Scrum are designed to ensure that inspect and adapt can occur regularly with complete and correct information. Scrum does not…