How to use SwiftKanban @swiftkanban #WebToolsWiki

- Last Update:


SwiftKanban is a web-based electronic Enterprise/ Portfolio Kanban and Visual Management tool for both collocated and distributed teams and enterprises. Kanban and Visual Management represent the latest and the best way of collaboration on a wide variety of business and technology functions.

Whether you are a software team or an IT/ Ops/ DevOps team, a Project Manager/ team or a business function such as HR, sales, marketing, procurement, legal, construction, insurance or ANY other, you can use SwiftKanban to visualize your team’s processes and work and improve overall flow, efficiency and delivery of value to your customers. SwiftKanban combines the best of Visual Management, Kanban and Scrum to give you a powerful tool for Lean/ Agile software development, visual project management and business collaboration and improvement.

SwiftKanban is available on SaaS as well as On-Premise models and comes with a free Team version as well as Group and Enterprise options.

Visualize Your Workflow

Visualize Your Workflow using SwiftKanban and quickly define your processes as lanes and sub-lanes on a Kanban board, representing a workflow stage through which you can flow your work.

Define Custom Work Cards and Card Templates

Define Work Cards of various types e.g. User Stories, Defects and Issues using a rich text editor, configurable template to define your backlog, which can feed work into the Kanban board. You can also set default TODO list for cards which can act as DOD (Definition of Done) or a generic checklist.

Smart Lanes

Smart-Lanes add tremendous flexibility and visualization to the Kanban board. ‘Smart Lanes’ can be associated with various card attributes such as Class Of Service, or Team Members, or even your own ad-hoc labels. As you move cards from one Smart Lane to another, the associated attribute value is also reset accordingly and vice-versa!

The following quick actions are available directly on the card.
Archive Card – Archive user story card from any lane to mark it done or if the user story has become obsolete.
Clone Card – Clone card to create an exact replica of existing card to start a new user story with current settings of the card. E.g. A team is working on an issue for London factory and a similar issue is discovered for Tokyo factory.
Convert Card – Convert a defect/bug into a user story or change request without losing details of existing card. Convert card can be used to convert any card type to other card type. This helps when the work type changes for a user story.
Move To (Backlog) – Skip lanes and move the user story card to Backlog or any other lane on the board.
Linked Cards – This will allow you to trace several cards for future reference

Get different level of details using board zoom!
Select your role and check how the board looks for you: Developer Product Owner Business Executive
Teams β
SwiftKanban allows grouping members in ‘Teams’ and filtering the Kanban board/reports by Teams to track the progress of various cards assigned to a specific teams and enable focused collaboration.

SwiftKanban encourages communication amongst the team and provides capability for threaded discussions, instant chat with card owners and group discussion with team of entire board.

Analytics and Reports
Track key performance metrics such as Lead Time, Cycle Time and Wait Times in SwiftKanban and identify improvement opportunities using Cumulative Flow diagrams, which are generated based on the work item count, as well as work item estimates, to indicate the progress of work being executed/ flowing through the board over a period of time.

Board Playback
Board PlayBack is a unique feature that allows teams to simply ‘play back’ their Kanban board to review what happened over the review period and get a powerful, visual feedback of their board’s ‘health’.

Scrum Release Planning
Release Planning view in SwiftKanban enables team to plan release scope in an easy-to-use drag-drop interface, as well as, track the release progress using various visual indicators and charts available in the same view.

User Story Hierarchy
User Story Hierarchy is useful in situations where a larger (or parent) user story needs to be broken down into several smaller (or child) user stories for better planning and execution. Defining relationships is through a highly visual interface that enables creation of child stories as well as linking existing stories to parent user stories.

Burn-down Charts
Burn-down charts are provided in SwiftKanban to enable SCRUM teams to track the release progress in the good old way by tracking the hours remaining to be burned or how many actual hours have already being spent( Burn-up chart )before release is ready to be shipped.

Older cards tend to fade
See where the action is! The new Aging icon on the board menu enables you to see which cards have and have not been updated recently. The older the card updates, the more faded it will appear!

Do you have any tips for using SwiftKanban? Please add them to this list.
Please vote up or down any tips that are already here. Thank you!

Do you know any SwiftKanban alternatives?
Please add the names of each tool to this list and help others to find them and try them out.
Please vote up or down any alternative so we find the most popular ones. Thank you!

We hope you enjoy SwiftKanban. To search for any other online tool please use our search box at the top of the page.
If you have benefited from what you have learned here we hope you will consider sharing this page with your social media friends by using one of the sharing buttons out on the left. Thank you!

If you have any questions about SwiftKanban please ask in the comment boxes below either Google+ or click over to Facebook. If you know lots about SwiftKanban or any other tool featured in The Web Tools Wiki then please let us know in the comments as well. We will connect with you and give you editing rights. We often pay regular editors for their time.

Loading Facebook Comments ...

Leave a Reply

Your email address will not be published. Required fields are marked *