MG Software.
HomeAboutServicesPortfolioBlogCalculator
Contact Us
MG Software
MG Software
MG Software.

MG Software builds custom software, websites and AI solutions that help businesses grow.

© 2026 MG Software B.V. All rights reserved.

NavigationServicesPortfolioAbout UsContactBlogCalculator
ServicesCustom developmentSoftware integrationsSoftware redevelopmentApp developmentSEO & discoverability
Knowledge BaseKnowledge BaseComparisonsExamplesAlternativesTemplatesToolsSolutionsAPI integrations
LocationsHaarlemAmsterdamThe HagueEindhovenBredaAmersfoortAll locations
IndustriesLegalEnergyHealthcareE-commerceLogisticsAll industries
MG Software.
HomeAboutServicesPortfolioBlogCalculator
Contact Us
  1. Home
  2. /Templates
  3. /Kanban Board Template - Free Visual Workflow Management Guide

Kanban Board Template - Free Visual Workflow Management Guide

Set up your kanban board with this free template. Covers columns, WIP limits, swimlanes, policies and metrics for lead time and cycle time measurement.

A kanban board is a visual management tool that makes the workflow visible and helps the team keep work in balance. By moving work items as cards through columns representing different phases of the process, everyone can see at a glance what is happening, where bottlenecks form and how much work is simultaneously in progress. This template provides a complete framework to set up your kanban board effectively: from defining the right columns and Work In Progress (WIP) limits to setting up swimlanes, documenting policies per column and measuring lead time and cycle time. The document includes guidelines for choosing the optimal column layout based on your work process and team size. The template also covers the use of explicit policies, such as the Definition of Ready and Definition of Done per column, that clarify when a card is allowed to move to the next phase. Additionally, it contains sections for establishing feedback loops (daily standup, replenishment meeting, delivery review) and analysing flow using cumulative flow diagrams and control charts. By consistently applying the kanban system you improve predictability, reduce overload and shorten the lead time of work. The template also addresses common pitfalls when introducing kanban, such as ignoring WIP limits when pressure increases, lacking explicit policies so cards shift between columns without clear criteria, and not measuring flow metrics so improvement opportunities remain invisible. By recognising and addressing these pitfalls you get the maximum benefit from your kanban implementation.

Variations

Software Development Kanban

Board focused on software development with columns for Backlog, Ready, In Development, Code Review, Testing and Done. WIP limits per column and a separate expedite lane for urgent bugs.

Best for: Suited for development teams that deliver continuously without fixed sprints and want to optimise their workflow for lead time and quality.

Support Team Kanban

Board focused on support tickets with priority swimlanes (P1 to P4), columns for Triage, In Progress, Waiting on Customer and Resolved, and SLA indicators per priority.

Best for: Ideal for support and helpdesk teams that prioritise work by urgency and need to monitor SLA compliance.

Personal Kanban

Simple board with three columns (To Do, Doing, Done) and a strict WIP limit of two to three items. Focused on individual productivity without team overhead.

Best for: Perfect for individuals who want to organise their personal tasks and deliberately limit how much work they have in progress simultaneously.

Portfolio Kanban

Management-level board visualising projects and initiatives instead of tasks. Columns for Proposed, Approved, In Flight, Review and Completed with WIP limits per capacity group.

Best for: Suited for management and PMO teams needing an overview of ongoing projects and the distribution of capacity across initiatives.

DevOps Kanban

Board covering the full delivery process from feature request to production, including columns for Build, Deploy to Staging, Verification and Deploy to Production.

Best for: Essential for DevOps teams wanting to visualise the full value stream from idea to production and identify bottlenecks in the deployment process.

How to use

Step 1: Map your current work process by listing all steps a work item goes through from request to delivery. This forms the basis for the column layout. Step 2: Define the board columns. Each column label represents a phase in the process. Optionally add sub-columns (for example In Progress and Done within Development) for more granularity. Step 3: Set WIP limits per column. Start with a limit equal to the number of team members working in that phase and adjust based on experience. WIP limits are the heart of kanban and prevent overload. Step 4: Define swimlanes if your team processes different work types that need to be tracked separately, such as features, bugs and technical debt. Step 5: Establish explicit policies per column. Describe the criteria a card must meet to enter the column (Definition of Ready) and to leave it (Definition of Done). Step 6: Set up a replenishment meeting to regularly add new items to the board when capacity becomes available. This replaces sprint planning in a kanban context. Step 7: Use a daily standup at the board to identify blockers and improve flow. Focus on the cards that have been stationary the longest, not on what everyone did yesterday. Step 8: Measure lead time (from request to delivery) and cycle time (from work start to delivery) per work item. Use this data to improve predictability. Step 9: Create a cumulative flow diagram to visualise the distribution of work items across columns over time. Widening bands in the diagram indicate bottlenecks. Step 10: Schedule a periodic review (delivery review) to evaluate the kanban system itself: are WIP limits working, are policies current, and is lead time improving? Step 11: Automate where possible: connect your digital board to your code repository so cards move automatically when pull requests are created or merged. Step 12: Share the metrics with the team and stakeholders so everyone has insight into the performance of the work process and can make informed decisions about improvements.

How MG Software can help

At MG Software we help teams set up and optimise kanban systems that improve workflow and increase predictability. Our agile coaches guide the board design, help establish the right WIP limits and train the team in using flow metrics. We bring experience from teams of varying sizes and contexts and help you adapt kanban to your specific situation. Our guidance also includes setting up the initial feedback loops, facilitating the first delivery reviews and coaching the team in recognising and resolving bottlenecks based on the flow data the board generates. We also help select and configure digital kanban tooling and connect the board to your existing development workflow so cards move automatically in step with code progress.

Further reading

TemplatesSprint Planning Template - Free Download & ExampleUser Story Template - Free Download & Writing GuideScrum Explained: Sprints, Roles, Ceremonies, and When the Framework Adds ValueAgile vs Waterfall: How Your Process Shapes What You Build

Related articles

Sprint Planning Template - Free Download & Example

Run focused sprints with velocity tracking and per-member capacity matrix. Sprint planning template with goals, story selection, and definition of done for scrum teams.

User Story Template - Free Download & Writing Guide

Write effective user stories with this template: role-action-value format, Given-When-Then acceptance criteria, story points and Definition of Ready checklist.

Retrospective Template - Free Download & Facilitation Guide

Run effective agile retrospectives with this free template. Includes Start/Stop/Continue, 4L method, Sailboat format and action plan tracking for continuous improvement.

Scrum Explained: Sprints, Roles, Ceremonies, and When the Framework Adds Value

Scrum structures software development into short sprints with daily stand-ups, reviews, and retrospectives. Discover how the most widely adopted agile framework works, which roles and artifacts it includes, and when Scrum is the right choice for your team.

From our blog

What Your Business Gains from Agile Development

Jordan · 6 min read

Frequently asked questions

Scrum works in fixed sprints with a fixed team and roles (scrum master, product owner). Kanban has no fixed iterations but focuses on continuous flow, WIP limits and measuring lead time. Kanban is more flexible for unpredictable work; scrum provides more structure for plannable work. In practice many teams choose a hybrid approach (Scrumban) that combines elements of both methods to unite the benefits of structure and flexibility.
Start with a limit equal to the number of team members working in a phase and observe the effect. If the limit is too high, multitasking and longer lead times result. If too low, team members wait idle. Adjust limits gradually based on measured cycle time. The most important thing is that the WIP limit is actually enforced: a limit that is ignored when things get busy adds no value.
Popular tools include Jira, Trello, Asana, Linear and Azure DevOps. Choose a tool that supports WIP limits, swimlanes and flow metrics. For simple setups a physical whiteboard with sticky notes suffices. Also consider integration capabilities with your existing tools such as code repositories and communication platforms, so cards can move automatically based on activity in the development process.
Use an expedite lane, a separate swimlane for urgent items that may exceed regular WIP limits. Limit the expedite lane to one or two items at a time to prevent everything from becoming urgent. Define clear criteria for what qualifies as urgent and evaluate retrospectively whether the urgency was justified to prevent misuse of the expedite lane. Track how many items pass through the expedite lane per week and discuss the trend in your delivery review.
Yes, this is called Scrumban. You keep the sprint structure and ceremonies of scrum but add WIP limits and flow metrics from kanban. This works well for teams wanting the predictability of sprints combined with the flexibility of continuous flow. Start by adding WIP limits to your existing scrum board and measuring cycle time as a first step. Gradually introduce more kanban practices as the team becomes comfortable with the flow-based approach.
Measure lead time, cycle time and throughput per week. Use a control chart to analyse spread and a cumulative flow diagram to detect bottlenecks. A declining average cycle time and decreasing spread indicate an improving system. Discuss the metrics weekly with the team and use them as the basis for targeted improvement actions.
Limit columns to a maximum of seven. Use swimlanes sparingly. Archive completed items regularly. Hold a weekly cleanup round where outdated or blocked cards are discussed and either cleaned up or escalated. Ensure each card contains enough information so team members can understand the context without having to look up the ticket in another system.

Want this implemented right away?

We set it up for you, production-ready.

Get in touch

Related articles

Sprint Planning Template - Free Download & Example

Run focused sprints with velocity tracking and per-member capacity matrix. Sprint planning template with goals, story selection, and definition of done for scrum teams.

User Story Template - Free Download & Writing Guide

Write effective user stories with this template: role-action-value format, Given-When-Then acceptance criteria, story points and Definition of Ready checklist.

Retrospective Template - Free Download & Facilitation Guide

Run effective agile retrospectives with this free template. Includes Start/Stop/Continue, 4L method, Sailboat format and action plan tracking for continuous improvement.

Scrum Explained: Sprints, Roles, Ceremonies, and When the Framework Adds Value

Scrum structures software development into short sprints with daily stand-ups, reviews, and retrospectives. Discover how the most widely adopted agile framework works, which roles and artifacts it includes, and when Scrum is the right choice for your team.

From our blog

What Your Business Gains from Agile Development

Jordan · 6 min read

MG Software
MG Software
MG Software.

MG Software builds custom software, websites and AI solutions that help businesses grow.

© 2026 MG Software B.V. All rights reserved.

NavigationServicesPortfolioAbout UsContactBlogCalculator
ServicesCustom developmentSoftware integrationsSoftware redevelopmentApp developmentSEO & discoverability
Knowledge BaseKnowledge BaseComparisonsExamplesAlternativesTemplatesToolsSolutionsAPI integrations
LocationsHaarlemAmsterdamThe HagueEindhovenBredaAmersfoortAll locations
IndustriesLegalEnergyHealthcareE-commerceLogisticsAll industries