Skip to main content

Scrum Management Tool Poll Results: Moving Away From Cards?

The poll on Scrum / Agile tools usage was the most popular Scrum Breakfast poll to date — 100 responses, of which 63 were using a dedicated agile project management tool. A market leader seems to be emerging in the agile project management space. I've finally gotten a chance to compare the results of this Poll with those of the Scrumdevelopment poll on the same subject from December 2006. The results indicate significant changes in what tools agile teams are using to manage their work. I wanted the results to be comparable with the Scrumdevelopment poll, so respondants could only pick one tool. So even though they might use several tools, they had to choose which one was the most important.
The data indicates a significant shift towards dedicated agile project management software (from 7 to 63%), away from Spreadsheets ( down 38% to 9%) and Wiki &Other/Homegrown tools (together down from 33% to 6%), and to a lesser extent cards (down from 36 to 18%). Open Source solutions and traditional project management software(with 4% of the respondants) do not appear to play a significant role in this market. Dominant Player? Under the commercial suppliers, VersionOne was the most top ranked response (54% of those voting for a commercial tool), followed by ScrumWorks at 17%, and TargetProcess and Scrum for Team System (8% each).
The question was raised in the comments whether one manufacturer might have orchestrated a high response rate. It's hard to know for sure, but I don't think so. Three reasons:
  • Representative of two suppliers other than the winner left comments on the blog while the poll was running and so were aware of the results as they developed. If they had wanted to orchestrate a get-out-the-vote campaign, they could have (and maybe they did!).
  • I did put out a get-out-the-vote reminder on the scrumdevelopment list. It produced little if any effect.
  • As I watched the voting progress, the development seemed organic: the pattern was established early and subsequent voting did not change the percentages much.
It will be interesting to see how these results compare with VersionOne's study, which will be published next month.

P.S. For those of you who want the details: the poll data can be downloaded as an ODF spreadsheet.
[Update: July 7: I have published a Directory of Scrum Management Tools with links to all the suppliers]


Michael Dubakov said…
The main surprise for me is very low numbers for Rally. According the last year surveys it had market share comparable with VersionOne. Also maybe results are SCRUM oriented in general. What do you think?
Peter said…
Hmm. I think this question is best posed to the Scrumdevelopment list.

Maybe XP users have different thoughts on the subject?

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…