Skip to main content

Nokia Test Results: Is anybody really doing Scrum?

Last week, I challenged the Scrum community to take the Nokia Test: a Scrum litmus test to deterimine whether a team is agile and doing Scrum. How did the Scrum community fare?

Protecting Team Members from Management is clearly the biggest challenge faced by Scrum Teams. Only 51% of the respondants claimed that their team members were well protected from Project Managers or others disrupting work.

Prioritized product backlog and burn down charts are second and third from the bottom at 72% and 74% respectively.

Interestingly, all three points are issues relating to managment and the product owner (who is likely part of management), suggesting that management buy-in is a challenge. Either Scrum adoption is coming bottom-up or management is "talking the talk" but not "walking the walk".

On the total test score, only 26% of the respondants claimed an 8 on the Nokia scale. 36% claimed 7 points (total of 62% for 7 or 8 points). At least 7% did not meet the minimum definition of "agile"

Without question, doing Scrum is difficult. There was some discussion on the Scrum development group as to whether the Nokia test is hard enough. But even with this simple test, 3/4 of the teams in question are not doing Scrum. Or are they?

I have three issues with the Nokia test:

  1. "Software tested" is too specific to software development. I would ask the question "Is there a definition of 'done' which is consistently applied'?

  2. Continuous improvement is completely missing. Iterations don't necessarily imply retrospectives. I would add a question "Does the team perform retrospectives every sprint and implement top priority improvements?"

  3. Intent is also missing - Is the team actively trying to use Scrum to better realize the project? I think even if a team had to compromise on some points for tactical reasons (e.g. "the customer said no"), it should earn points for trying.


Unknown said…
As some have previously pointed out, the so-called Nokia test is about the bare basics.

Nevertheless, I miss a key criterion for all Agile and Scrum teams: there is no test of collaborative working by the team.

In my experience this is the hardest lesson for Scrum teams to learn. Although smaller teams find it easier.

What do others think?

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…

Explaining Story Points to Management

During the February Scrum Breakfast in Zurich, the question arised, "How do I explain Story Points to Management?" A good question, and in all honesty, developers can be an even more critical audience than managers.

Traditional estimates attempt to answer the question, "how long will it take to develop X?" I could ask you a similar question, "How long does it take to get the nearest train station?

The answer, measured in time, depends on two things, the distance and the speed. Depending on whether I plan to go by car, by foot, by bicycle or (my personal favorite for short distances) trottinette, the answer can vary dramatically. So it is with software development. The productivity of a developer can vary dramatically, both as a function of innate ability and whether the task at hand plays to his strong points, so the time to produce a piece of software can vary dramatically. But the complexity of the problem doesn't depend on the person solving it, just …

Money for Nothing, Changes for Free

“Money for Nothing, Changes for Free” encourages both customers and suppliers to focus on value.

A key advantage of Scrum projects is that at least once per sprint you have something that could be shipped and no work in progress. You can change direction every sprint, and you can reevaluate whether the project is a good investment or if your money could be better spent elsewhere. Abrupt cancellation is risky for the supplier.

While the concept of an early-exit penalty is not new, Jeff Sutherland gave it a unique allure with his allusion to the Dire Straits hit.
Desired Benefit Incentivize both customers and suppliers to focus on functionality that provides genuine value.
Structure This works with Agile software projects because there is little or no work in progress. After each Sprint, functionality is either complete or not started. Work is basically on a Time and Materials basis with a cost target, often with the intention that the project should not use up the entire project budge…