Getting Started with Kanban Software Development

We have so far looked at introducing Kanban systems and what are different things that has changed. Ok, now let us get into the actual thing.

I am new team who wants to do Kanban. How do i get started?

Following are the steps which i will do for my teams to get started with the Kanban Process.
Step 0 : Identifcation and Definition of Minimum Marketable Features and building the Backlog queue : Without this, no process or system works. It makes the product owner work. i know, this might look very basic, but i am sure most of us work with that the backlog ready even for some period of time.
Step 1: Define and visualize your process : Kanban is about the Visual Task board. You have to decide how the process will work and how do we move items, what is our SLA at every stage and how do we accept a feature. I am not sure, whether you have used a Task board in Scrum. In my teams we have used a Scrum Task board which helps in Navigating items from one step to other. Kanban Task boards are bit more detailed. It defines a limit of WIP per Stage, SLAs per Stage, Definition of Done per Stage.
Step 2: Limit work in progress (WIP) : This is the most important thing i learnt from Kanban. Just reducing the number of items in progress, will help us get to the done as quickly as possible. Also, the team completes a feature and moves to the next one, which makes sure that we are developing features which are absolutely required and not wasting time. Eventhough, in Scrum it restricts the number of items being developed per sprint, it doesnt restrict how many can be in a workflow state any point of time.
Step 3: Promote the new model. Pull – Don’t Push – Pull model is new to the team (atleast not every team is used to it).
Step 4: Measure the Lead Time : Lead time is the average time to complete one MMF, a.k.a “cycle time”. Measuring the average time to complete one MMF will help in understanding what it takes for the completion (To Avoid Complacency, Set the Right SLAs in Stages)
Step 5: PDCA (Plan Do Check Act): Pay attention to the work that is flowing through your system – or more importantly, the work that is not flowing – and fix the problems in the system. This is perhaps the single most under-utilized principle in just about every agile methodology in existence. So many teams and managers are begging to be told what to do and how to do it, so that they don’t have to think and don’t have to take responsibility for the process and its problems. If the work is not flowing and SLAs are not met, Task board has to become Red and the whole team has to focus their attention on the item which is not flowing before completing any thing else.

In a nutshell, Kanban is just a scheduling system. The way it works is, Team pulls a feature from the Backlog Queue, complete the development, testing, acceptance and ships it as soon as it is done. Then the team moves to the next one, the Backlog Queue, complete the development, testing, acceptance and ships the feature. Work is shipped as soon as it’s ready, and the team only works on one (Queue Length) at a time.
Reference URL:
Kanban Systems
How to get started with Kanban Software Development
Happy Reading!!!


Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s