Agile Kanban

A retrospective that borrows the familiar Kanban board to review the team's flow of work. Items move across to do, doing and done, making bottlenecks and stalled tasks easy to see. It's a natural fit for teams that already think in terms of flow and want their reflection to mirror how they actually work.
To Do

Agreed work not started yet

Roman

Roman

Write the rollback steps for the payments deploy
Maria

Maria

Update the onboarding doc after the new CI setup
Doing

In progress right now, with a name attached

Anna

Anna

Cache the reports endpoint — Dana, since Tuesday
Daria

Daria

Split the migration ticket — Tom, in review
Done

Finished and verified — proof the team moves

Maria

Maria

Smoke test after deploy is running in CI
Kirill

Kirill

Support rep added to the sprint review invite

Kanban is a simple and effective method for tracking the work being done in a project. It is typically used in agile software development teams but can be applied to any project. Kanban is excellent for tracking the list of tasks that need to be done, tasks that are currently in development, and tasks that are completed.

Introduction to Kanban

Kanban (Japanese for "visual board") helps a team visualize the work process and manage it more effectively. The main elements of Kanban include:

  • Task Cards: Each task or work item is represented as a card.

  • Kanban Board: The board is divided into several columns, each representing a stage of the work process.

  • Work-in-Progress (WIP) Limits: Limits on the number of tasks in each column help prevent overloading and focus on completing current tasks.

Key Benefits of Kanban

Kanban offers numerous benefits for teams and projects:

  • Transparency: All team members see the current status of tasks and can easily track progress.

  • Flexibility: The method is easily adaptable to changes and allows for quick responses to new requirements.

  • Workflow Management: WIP limits help avoid overloading and improve the quality of the work being done.

  • Continuous Improvement: Regular reviews and retrospectives help the team constantly improve processes.

How to Use Kanban in a Retrospective

A retrospective is an important stage in the Agile process that allows the team to analyze the past period, identify problems, and find solutions. Here's how to use Kanban in a retrospective:

Preparing for the Retrospective

  1. Create a Kanban Board: Divide the board into columns such as "What Went Well," "What Can Be Improved," and "What Needs to Be Changed."

  2. Gather Feedback: Ask all team members to write their thoughts and ideas on cards and place them in the appropriate columns.

Conducting the Retrospective

  1. Discuss Each Column: Discuss each card in each column. Ensure that all team members have the opportunity to speak.

  2. Prioritize Tasks: Determine which tasks and improvements are most important and require immediate attention.

  3. Action Plan: Create an action plan to address the identified problems and improve processes.

Completing the Retrospective

  1. Document Results: Record all key points and decisions made during the retrospective.

  2. Assign Tasks: Assign responsible persons for completing each task from the action plan.

  3. Review and Adjust: Conduct a brief review after some time to ensure that all tasks are completed and processes are improved.

Examples of Kanban Usage

Kanban can be used in various scenarios and projects. Here are a few examples:

  • Software Development: Development teams use Kanban to track tasks related to development, testing, and deployment.

  • Marketing: Marketing teams use Kanban to manage campaigns, create content, and analyze results.

  • Project Management: Project managers use Kanban to track tasks related to planning, execution, and completion of projects.

Kanban is a powerful tool for managing projects and improving work processes. It helps teams visualize work, manage the flow of tasks, and continuously improve processes. Using Kanban in a retrospective allows the team to analyze the past period, identify problems, and find solutions. Implementing Kanban in your project can significantly enhance its efficiency and the quality of the work being done.

Similar templates

Other formats teams pair with this one — open any of them as a board in one click.
Six Thinking Hats
Based on Edward de Bono's method, this format has the team look at the sprint through six distinct mindsets. Each hat directs attention to one angle — facts, feelings, caution, optimism, creativity and process — so the discussion stays balanced and no perspective is missed. It's a powerful way to break out of habitual thinking and explore an issue from every side.
Post Mortem Retro
A reflective format for looking back on a finished project or major milestone. The team gathers what it liked, what it missed, what individuals learned and what to do differently next time, closing with appreciations. The wider lens makes it ideal for drawing lasting lessons rather than tweaking the last sprint.
Rose Bud Thorn
A gentle, well-balanced format that gives equal weight to the good, the painful and the promising. The rose marks what went well, the thorn what hurt or got in the way, and the bud what shows potential and is worth nurturing. Including the bud keeps the conversation forward-looking instead of dwelling only on the past.
Hopes and Fears
A forward-looking format best used at the start of a project, quarter or initiative. The team shares its hopes for what could go right alongside its fears about what might go wrong. Naming both early builds shared understanding and surfaces risks while there's still time to act on them.
Good Bad Better Best
A four-column format that turns reflection into a ladder of improvement. The team names what was good and what was bad, then pushes further to what could be better and recognizes the very best results, performances and people. Ending on the high note of best keeps the energy positive and celebrates standout contributions.
Likes / Wishes / Wonders
A concise, exploratory format that blends feedback with curiosity. Participants share what they liked, what they wish were different and what they wonder about going forward. The wonders column invites open questions and fresh ideas, making it a great fit for teams exploring new ways of working.
Try Template