The first thing you notice on SpiraPlan is the tab bar, the features are grouped on tabs that give access to maintain various objects, requirements, tasks, releases, etc. Because SpiraPlan intents to be a generic agile tool it didn’t use the Scrum terminology, so don’t expect to see “Story” or “Sprint” terms, “Requirement” and “Iteration” was the chosen ones. That’s not a real problem, thinking in a more generic agile view,that was no so bad choices.
The available Tabs are: My Page, Project Home, Planning, Testing, Tracking and Reporting. My Page is a little dashboard with objects (Projects, Incidents, Tasks) associated with the logged user. Project Home is a big dashboard that show every project information and depending how big your project is, it can become an overwhelming and confusing amount of grids. It´s hard to look on that screen completely populated with data and not be afraid to start using the tool. Let’s talk a little more about the remaining tabs.
The Planning Tab is where most of the daily work will be done in SpiraPlan. The Requirements option is the closer that you can get from Product Backlog. A big grid with tons of columns and multi-level requirements, luckily you can hide and show the columns you like, but this operation is slow and annoying. A big problem with the Requirement grid is the impossibility to sort it by any column, that means you can not have a view of a prioritized backlog anywhere in the tool. The requirements have a importance property alowing a scale of 1 to 4, begin 1 for Critical and 4 for Low and the best you can do is filter the grid to see only requirements with a specific importance. Estimating requirements – you can define how may hours and MINUTES will take to develop the requirement, this shows a lot about the way Inflectra thinks about Agile projects. Creating tasks almost the same as creating requirements, and if you have lots of tasks it will take a very long time to put it all in the tool and again task estimates are made in hours and minutes.
Interations and release planning are a bit confusing too. You can have Releases with child Releases with Iterations, something no quite useful and when you see what is proposed for a release, you get a big grid with tasks, not requirement but tasks, it turns the release planning is some sort of task tracking. So the whole idea of thinking about a project from a strategic point of view is not supported.
Working on a Sprint
There’s not a particular feature to suport the daily scrum or otherh daily activities, there’s no taskboard. To update the tasks status you have edit it one-by-one, and update the status and dates too. A real nigthmare even with have a normal amount of tasks. The tracking tab is just another grid showing tasks or incidents.
SpiraPlan has big flaws, so big that it will keep a lot of teams from use it. I ask myself if there is a single Scrum team that will enjoy use it. The tool is just a collection of porly designed grids and the ideas behind it are so far away from the agile concepts that’s hard to look at it as an Agile Tool. SpiraPlan is very close to Ghant-Chart kind of tools. In the reviewers point of view it can’t be used properly for a real agile project.