The first thing to do on BananaScrum should be to create a project and to register the people who are going to work on it, very little information is necessary, only the essentials to start working. After that you can start creating your Product Backlog, in a very easy way. You only need to type Name, Description and Estimate. The estimate part can be a bit of a problem if you don’t use the Fibonacci based scale that normally appears on planning poker cards. This scale is mandatory on BananaScrum but as Fibonacci is probably the most used scale by scrum teams, it can be useful for most of the situations. Another problem is that BananaScrum doesn’t have a release planning feature, so it is not clear when the team reaches the point desired for a release.
The prioritization is the best part of the backlog management feature. It allows one to drag and drop the items to prioritize them, as if you are working with cards on a big table – really, really easy. It´s also possible to mark your backlog items with tags, so that you can create a huge a amount of tags and associate them to your items. These tags work as a kind of filter, you can see only those items which have a particular tag, or two tags, or don´t have any tag, etc. This feature allows you to generate a very complex set of views for your backlog.
With your backlog in place it is time to start a sprint. Just create a new sprint and drag the stories from the backlog that the team thinks will fit into the sprint. This is an appropriate time to create the tasks from each story but it is also possible to create the tasks when the story is still in the backlog. Creating tasks is also an easy job, just type the description, estimate and assign it to someone if you like. The estimate of task time is made in hours and again, there’s no way to change it, but there is no fixed scale, so you can use any value. Task estimation is mandatory for seeing the burndown chart working, so if you don’t estimate your tasks you can use the 1hour-for-everything trick, and track the progress by the amount of tasks.
On BananaScrum it’s also possible to register your impediments in an impediment backlog the same way you create the stories of the product backlog. You cannot assign a response for the impediment but you can mark them as closed with a comment of how it is to be solved. For the burndown chart there is only one option, the hours X sprint days for the sprint tasks, there is no release burndown or a velocity chart so as far as tracking goes, there is something missing from this tool. Another thing missing is a clearer way one sets the status of the tasks, visually you cannot say if a task is open or in development, the only visual aid is a green mark saying that a task is done when you report there are no more hours left to work on it.