Kunagi - reviewed on: July 14, 2011 - rating: 10
I use kunagi from begining of 2011. At first I used it to internal projects now it is also used in our company in commercial projects with success. We have tried other products like versionOne (very heavy, not intuitive and slow interface, lots of popups) and other heavy applications - but we have found Kunagi to be most simple, fast and effective Scrum focused tool. I like it most for intuitive user interface and SCRUM support. Kunagi helps much in team member collaboration with: - comments mechanism - which is enabled for all managed elements (i.e. story, task, issue, idea, bug, sprint, release, quality etc) - live chat - forum, wiki - calendar with possibility to set events and automatic start/end of sprints - RSS notifiers for events - great dashboard with information about who is working od what, last events, next work for each SCRUM role... - great impediments mechanism - mechanism of themes (tags) for groupping purposes. Interface has some drag and drop elements (in backlogs, whiteboard) which is nice Input in most cases is autosubmit, with no popups Interface is autorefreshable - after other user changes they are immidiately visible to others without any hand work. Kunagi has support for all SCRUM development phases (planning, doing, review, retrospective) and help to have real focus on work. It has nice find text box which finds It is free and opensource - so if one wants to - can easy develop custom features (GWT). Kunagi is WEB 2 application - users can send feedback (bugs reports or features requests) immediatelly from application. Kunagi team response is fast - they manage Kunagi project with Kunagi - so they use it continuosly. Development process is very transparent. You can even generate your project site with development progress and other important information. So these were beautilfull pages of Kunagi. Now very few things that I do not like in Kunagi. It has still problems with stability - sometimes small bugs occurs (hopefully there is automatic error handler which restart session). As I know Kunagi team is working on stability and it is high priority for them. Lack of sorting and filtering (only product backlog can be filtered) Lack of real splitting stories with estimation handling. Kunagi is sometimes to much SCRUM pure and team is quite resist to add some features which do not fit their idea of Kunagi. So when your project is not developed in pure SCRUM you will lack of features which takes into consideration all project scope, i.e. product burndown/up chart, or product backlog done work (only current sprint work done is shown, and historic sprint PDF reports). Nevertheless as I said we use Kunagi with success and we really like this tool. We have used it in teams not greater than 6-7 members. I can with no doubt recommend this product.