We are back again with some exciting feature updates to SwiftKanban. In this release, we have strengthened the support of SCRUM in SwiftKanban with Time-Tracking capability, Burndown and velocity charts and the much-awaited tablet interface for SwiftKanban. Here’s a quick peek into the new features that you can experience live, on our production servers this weekend:-
iPad and Tablet Support
Experience Swift Kanban on the go with new SwiftKanban boards supported for iPads and all other Tablets devices. Hassle-free and instant access, as there is “no app” to be downloaded, “no special configuration” rigmarole to be followed to make it work. You can view your Kanban board, view and edit cards, add comments, and move cards by just swiping your fingers. This is an early version and we are constantly adding rest of the board features, but while we are at it, do enjoy the experience and tell us if it has come out as the way you wanted it to be.
We present you with our new Time-Tracking plug-in, which allows you to enter Actual/Remaining hours against the card To-dos that are accounted in the newly added Burndown/Burn-up charts. This is an initial beta version of the feature and we could not resist releasing it to all of you to try it out and provide your valuable feedback. For more information on the feature, see Logging Effort for To-Dos page.
Release Burndown Charts
The SCRUM teams using SwiftKanban can now track the progress of their releases using the newly defined Burndown/Burn-up charts, which retain all the benefits that a Kanban CFD (Cumulating Flow Diagram) provides, and enable the best of both worlds/methodologies in a single solution i.e. SwiftKanban. See Release Planning page for help on Release Burndown Chart.
Throughput/ Velocity Charts
Throughput is a key metric in Kanban for tracking productivity in a given period and identifying process improvement opportunities. We now have this key metric in SwiftKanban that allows Kanban teams to measure throughput in terms of number of cards delivered for a specified period. It also allows SCRUM teams to measure throughput in terms of card estimates/points delivered in a Release/Iteration (also known as Velocity) and enables better Release/Iteration planning. For details on the metiric, see Throughput section in Metrics help page.
New API Service
We have shared the API for getting the project details i.e. name and Id of each project in SwiftKanban. See Get Project Name and ID section in the API Documentation page.
Last but not the least, we heartily thank all our users who have motivated us and provided their valuable feedback to bring out the above features.
Do send us your feedback and suggestions at firstname.lastname@example.org. You may even post them on the SwiftKanban Community page.