Many software development organizations have picked up Kanban based on the approach to speed up their growth. There are several great Kanban specific tools available for personal and professional use, e.g. Trello, Taiga, and even Visual Studio by Microsoft. So, what makes Kanban such a great way to manage software development - and why should you give it a thought.
Photo by JD Hancock
Let’s start with the official definition of Kanban. Wikipedia says:
“Kanban (literally signboard or billboard in Japanese) is a scheduling system for lean and just-in-time (JIT) production. Kanban is a system to control the logistical chain from a production point of view, and is not an inventory control system. Developed by Taiichi Ohno, at Toyota, Kanban aimed to improve and maintain a high level of production.”
In layman terms - Kanban lets you write everything going on in the project on a board. Writing everything at one place gives you a bigger picture of things going on. It also lets you identify the bottlenecks plaguing the project. So, yes, a signboard, a big todo list for the whole project, but incredibly simple, and incredibly useful.
Lets consider a typical scenario - there are 8 tasks lined up for the release next week. All the tasks were added to the Kanban board and assigned to the relevant team members. A day before the release, 6 tasks related to development of features are all done. Remaining 2 tasks for documentation are still in the “In Progress” phase. The issue - developers focused on the coding part and neglected the documentation. Solution - focus on the parallel/inline documentation and learn a lesson for future. Not that this solution was difficult to arrive at, but the visual representation makes it much more easy to conclude and identify the bottlenecks.
Here are few important reasons why you should consider Kanban :
- No training needed: Unlike other software development/management methodologies, e.g. Agile, Waterfall, RAD, etc. Kanban doesn’t need any specific training or knowledge to get started. This is because it doesn’t have any technical jargon that can confuse the team members - people can just get started. This is specially useful for non tech teams
- Ease of use and adoption: Not only free from technical jargon, Kanban is also extremely easy to implement at project level. You just need a board - if you have issues with online tools, you can set it up with few sticky notes pasted on a white board!
- Applicable to almost any field: In one of the previous blog posts, we talked about adoption of Agile in non technical projects. On similar lines, Kanban is a perfectly fit approach to be taken up in almost any field.
- Dynamic status: If updated regularly, Kanban is very handy in giving you a clear cut picture of the overall project status - no scrolling through huge excel sheets or trying to find the meaning of a complex graph! Just a glance and you already know what’s wrong with the project.
Taiga is one of the few open source Kanban tools, designed to keep usability in mind. It is dead easy to get started with - unlike almost all the big names out there, you don’t need a credit card or agree to a long EULA (end user license agreement). You can even close your account anytime - no questions asked. So, there’s nothing to lose - but a lot of things to gain. Just create your account (it takes less than a minute) and select the project template (Scrum or Kanban) you’d like to use.
If you want a Kanban only project, just select Kanban as the template and click next. The next page shows you the Kanban board, just fill up the tasks and you are ready to go!
Taiga also allows you to follow Kanban style project tracking even if you are using a Scrum template. To enable Kanban in you Scrum based project, go to Project >> Modules >> Kanban >> Enable. Then click save below. Now you have a Kanban link on the left side bar. Click on it to see your project on a Kanban board.