Pitfalls of Scrum Software Tools
The main problem with V1 is that it is not a specific scrum tool. It tries to fit into a variety of niches, which could cause your teams to have some problem using the tool. If you do plan on using this tool, you will probably need a scrum trainer to teach your team how to adequately use this software. Finally, the templates that V1 uses are of a different type than are generally used in the industry.
Besides the obvious glitches listed above, there are additional problems with using software tools.
1. The team spirit can fall by the wayside. Software tools can cause your teams to stop communicating. Since a particular team member is simply inputting his/her own work into the computer system, they may just focus on their own tasks and stop sharing with the rest of the group.
2. Software tools can break down. While it's true that whiteboards can accidentally be erased, whole software systems can break down on a dime. If you need a particular tool and it stops working, you could be ,to quote a cliché, up the creek without a paddle. What if it's the software administrator's day off or he/she is on a cruise to Africa? It could be quite a long time before you can get back to work.
A software tool could be a time suck. You could waste nearly half of your sprint trying to fix your tool as opposed to completing your main project. So, you should be careful when deciding to adopt a particular scrum software tool. The old whiteboard and sticky may still be your best bet.