To Tool or Not to Tool
A recurring question in my coaching engagements and training classes is about tools for Scrum (Product Backlog, Sprint Backlog, Taskboard, Burndown Charts). My recommendation is always the same: try index cards, pens, post it’s, card walls etc. My collegues at it-agile do the same.
Sometimes have the impression that we are very dogmatic when it comes to tools. I don’t think that I or my collegues are dogmatic. We simply base our recommendations on our experiences. Over the last 10 years we tried a lot of different tools and we have seen even more tools at our clients and the experience so far was always the same: for agile teams physical tools like index cards worked better than software tools.
But why work physical tools better than software tools?
Software tools are used with another focus than physical tools. Software tools are used for managing (e.g. for managing the Sprint Backlog). Physical tools facilitate communication and cooperation. When somebody moves an index card at a card wall, the other team members can see that directly and step into a discussion. When somebody changes the status of a ticket in an issue tracker nobody notices immediately and starting a discussion is unlikely.
And facilitating communication is more important than easy management?
This question is easy to answer with a look at the agile manifesto: The first value statement of the agile manifesto reads “Individuals and interactions over processes and tools”. And principle number six says: “The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.”
Yes, communication and cooperation is king.
So whatever tool is used communication and cooperation should be the goal, not management. And I think that this goal is easier to achieve with physical tools than with software tools. But in the end the decision is up to the team.
Things to try
- The team should at least try physical tools for one Sprint to make an informed decision.
- As ScrumMaster shield the team from existing tools and do the mapping from the physical tool to the software tool during the trial period.