Category Archives: Nokia Test

Minimum Definition of ‘Agile’: Scrum-Butt Test

First, let’s assume that we believe that our firm needs a good agile transformation to achieve important business goals. Perhaps these goals are: (a) faster time to market, (b) more creativity in the product, and (c) greater productivity.  (In any case, not ‘Agile’ for agile’s sake.) One method to achieve more success from the agile […]

Nokia Test: Know your velocity (7)

Another installment in explaining the Nokia Test aka The ScrumButt Test. Background: There are far too many teams doing “Scrum, but…[eg, we don’t have a ScrumMaster]”.  This is not “full-out” Scrum, and almost always means that the team is not getting impressive results. My original blog post is here.  And I have other blog posts […]

The Nokia Test (6): Estimates created by the team

Another installment on the Nokia Test. Before we begin, a quick mention that Jeff Sutherland has done an improved scoring on the Nokia Test. See here. So, the next item on the test says: “The Product Backlog has estimates created by the team.” Why is this important and what does it mean? Meaning first: So, […]

The Nokia Test (5): A prioritized Product Backlog is essential

We started a series on The Nokia Test some time ago. This is the fifth explanatory post about the test. To find the others, search above (left), and here is the original post. The second item in the second section of The Nokia Test is this: There is a Product Backlog prioritized by Business Value […]

The Nokia Test (4): You know who the Product Owner Is

In this series, we are going over each question in the Nokia Test. The first section of the Nokia Test is a quick determination: are you doing incremental development? Then second section is: are you doing Scrum? We are now up to the first question in the second section is: Do you know who your […]

Two cheers for the Nokia Test (2)

A comment by Kelly Waters and a discussion yesterday with Peter Smith prompts me to comment. Some are attempted to come up with a long list of all the practices involved with Scrum (or Scrum plus other parts of Agile), and then score each team. I don’t think the long list replaces the simple short […]

Two cheers for the Nokia Test

I am an advocate of the Nokia Test, up to a point. Why do I like it? I think it is a simple way to set some sort of lower boundary on Agile (Scrum) and it tends to make two problems more visible: Cowboy Agile on one side and Agilefall (aka Wagile) on the other […]

The Nokia Test (3): Agile Specifications

The third line in the Nokia Test is: “The Iteration must start before the specification is complete.” What does this mean? The first practical goal was to eliminate the analysis paralysis and delay associated with waiting until the specification was “complete.” I don’t know all the details at Nokia, but I have lived them at […]

The Nokia Test (2): Working Software

The second line in the Nokia Test says: Software must be tested and working by the end of each iteration. This is the second of three items that confirms the team (project) is “iterative.” There is a series of small tests (within the Nokia Test) if the team is really doing Scrum (in Nokia’s opinion). […]

The Nokia Test (1): Iterations must be timeboxed

I will be doing a series of posts that discuss each element in the Nokia Test (see earlier post). In this first post, we will focus on the first element in the Nokia Test: “Iterations must be timeboxed to less than six weeks.” First, remember that the first section of the test is to determine […]