Kanban Tool is a good entry point to managing agile software development
Overall Satisfaction with Kanban Tool
Kanban Tool is being used in places around our org to support agile-esque activities for remote teams. Our primary process is very stand-up meeting focused and the principles of the Kanban Tool are pretty close to in line with what we want to accomplish. It shows the movement of model-based activities across a project timeline.
Pros
- It provides a good basic overview of where tasks are on a timeline (particularly helpful for a pull-based approach).
- It provides a good collaborative space to have multiple folks commenting on multiple tasks.
- It does a good job of managing very basic visual elements of an agile development cycle.
Cons
- There isn't a strong UI on the tool. Customizations can be difficult to make.
- There isn't a very robust communications component on the tool to facilitate conversations—it's WYSIWYG.
- The mobile story isn't fully developed yet. It could stand to be stronger on mobile devices.
- It was a good experiment, but not robust enough to manage both hardware and software.
- It's a great software tool for distributed teams running an agile environment.
- It has given us a more clear understanding of what we actually need to do HW/SW agile.
JIRA is more robust and more connected. Kanban Tool is a good basic tool to do basic tasks. At an enterprise level, JIRA has more to offer a mixed discipline team that has hardware and software builds (model-based design). For small teams doing just software development in an agile methodology, Kanban Tool is as good as anything at managing the basic burn-down activity.
Comments
Please log in to join the conversation