As soon as you and your team reach a point where you are comfortable with Kanban, you should do a detailed horizontal mapping of all important steps of your work process. The logic here is simple.
For example, it would be wise to break down every major step of the development process into several smaller steps. Stick to the end to see how you can optimize every step of every distinct team process on a team board without creating a confusing mess.
Subscribe to our industry email notices? You need to Register an InfoQ account or Login or login to post comments. Visualizing the most important steps in your process is enough to optimize your workflow but not to advance it.
If we get back to our software development board, it is easy to see that the columns presented a few paragraphs above are perfect for mapping a new feature development swimlane. Nonetheless, it is great for establishing flow management by introducing your team to pulling work on their own.
As soon as you are past the stage of familiarizing, you will start noticing some limitations of the 3-column Kanban board, especially if you are practicing Kanban in a knowledge-work environment. Like Print Bookmarks. After you advance your board layout with additional columns, it would be appropriate to add a few swimlanes to make your workflow visualization even more precise.
The top swimlane contains the most important type of cards that our developers work on. So in this case, you can just merge Tech design, Coding, and Testing.
Mastering the method and making the most of what Kanban can give you requires plenty of practice and experimentation. Subscribe to our newsletter? Company size: See our privacy notice for details.
You may even break down the last step of software development - deployment into multiple steps like:. Here comes an important question.