Forward Looking Kanban Board

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp
The Kanban method is built around improving the flow of product development. It works very well when you work according to priority. It also works well when some items have schedule constraints. When many items have schedule constraints this becomes an issue.

The Motive

I was having a discussion with one of my clients and they raised the issue that what was going on wasn’t clear. Immediately I thought of setting up a kanban board. However, when we started to do that it became clear that the main issue is how to commit to clients about deliveries. Deliveries to my client’s clients include installation of software, configuration, training, and beta testing. As a matter of fact, my client was managing many small projects and they needed to commit to the various due dates. In a Utopian world, my client’s clients would all be agile and due dates were less of an issue, however, this was not the case, so we needed to come up with some solution. After some discussion, we came up with a scheme for visualizing my clients’ commitments. We call it a Forward Looking Kanban. You can see it at the top of the post.

How Does it Work?

This is a Kanban board (remember that “Kanban” means “signal card” in Japanese) showing what we plan to do each month. Each column represents a month. The idea is to constantly look several months ahead (this means that when we move to a new month we need to add another month/remove an old month). Each row represents a main step in the process, maybe like we would do on a regular kanban board, but I believe it should be less detailed. Each card, like cards on a regular kanban board, shows something we are doing. The main difference here is that the same card may appear in several places on the board. For example, we can see that Feature A appears under “Dev” in October and under “Deploy” in November. Another thing to notice is that each cell contains a WIP limit (well actually, it is more a PW – Planned Work limit, but I’ll leave that at WIP to make it simple). This is critical to the success of this kanban board. The main use of this board is that when something comes up we can try to schedule it, according to available capacity in the various cells. If there’s no capacity we may try to move some things. My client decided to add a red point to a card each time it is moved from cell to cell to get an indication of things that are getting postponed all the time. It should be noted that WIP limits may be different in different rows: in the example above the first row limits the number of deployments per month, while the development row has WIP limits manifested in points. The initial WIP limit should take into account both future events and buffers for changes. In the example above December has lower values (due to holidays). The buffers are not shown here but the people working with this board should know not to use the entire capacity of January when we are in September – that is a promise that will not hold. The client decided that at this stage we will not build an additional kanban board (the regular one). We will indicate whether items are done or not directly on this board. It’s been some time since I’ve been hearing clients raise issues about making commitments with a kanban board. There are solutions: indicating the date on the card, and using the lead time to estimate when items will be done. However, I hope this scheme I described here will bring a more comprehensive solution.
Subscribe for Email Updates:

Categories:

Tags:

Scrum Master Role
Coaching Agile Teams
Agility
Slides
Releases Using Lean
Managing Risk on Agile Projects
Enterprise DevOps
Engineering Practices
Agile Techniques
Agile Program
agileisrael
Lean Agile Basics
Jira
Spotify
Agile Mindset
Certification
SAFe
Kaizen Workshop
predictability
Program Increment
Hybrid Work
Agile Testing Practices
IT Operations
Sprint Retrospectives
Retrospectives
Agile Games and Exercises
Lean Startup
Change Management
Story Slicing
Risk Management on Agile Projects
AI
Scaled Agile Framework
Agile Delivery
Managing Projects
Continuous Planning
Agile in the Enterprise
Certified SAFe
RTE
Scrum With Kanban
System Archetypes
PI Objectives
Covid19
PI Planning
Kaizen
Agile Development
Advanced Roadmaps
ARTs
Lean and Agile Techniques
Agile Community
Agile Israel
Agile for Embedded Systems
GanttBan
Continuous Integration
QA
Tips
Lean-Agile Budgeting
Limiting Work in Progress
Kanban Kickstart Example
Team Flow
SAFe DevOps
Introduction to ATDD
LAB
An Appreciative Retrospective
Value Streams
ATDD vs. BDD
Nexus vs SAFe
EOS®
Lean Software Development
Lean Agile Organization
Agile Project
Business Agility
Accelerate Value Delivery At Scale
WIP
Risk Management in Kanban
Professional Scrum Product Owner
speed @ scale
Applying Agile Methodology
Jira Cloud
Implementation of Lean and Agile
Legacy Enterprise
LPM
ALM Tools
Amdocs
Kanban Basics
Achieve Business Agility
Frameworks
Tools
System Team
Self-organization
Lean Risk Management
What Is Kanban
Agile Product Development
Built-In Quality
DevOps
Principles of Lean-Agile Leadership
Acceptance Test-Driven Development
Code
Lean and Agile Principles and Practices
Confluence
Elastic Leadership
Agile Games
User stories
Portfolio for Jira
Software Development Estimation
AgileSparks
NIT
Test Driven Development
Continuous Deployment
Development Value Streams
lean agile change management
transformation
Continuous Delivery
Agile Israel Events
Large Scale Scrum
Agile Release Management
Iterative Incremental Development
ROI
Rovo
Introduction to Test Driven Development
Atlaassian
Product Management
Manage Budget Creation
Kanban 101
Kanban
Scrum
Systems Thinking
speed at scale
LeSS
Agile Exercises
Agile and DevOps Journey
RTE Role
Product Ownership
The Agile Coach
Effective Agile Retrospectives
Lean Agile Leadership
Agile
Sprint Planning
Scrum Values
Reading List
Nexus and Kanban
Keith Sawyer
Risk-aware Product Development
Agile Project Management
SA
Games and Exercises
BDD
Nexus
Agile Contracts Best Practices
AI Artificial Intelligence
Presentation
POPM
Scrum Primer
Implementing SAFe
Pomodoro Technique
Atlassian
Lean Budgeting
Webinar
ART Success
Continuous Improvement
Agile Risk Management
Nexus Integration Team
Legacy Code
Scrum Guide
Planning
Agile India
Scrum.org
Release Train Engineer
A Kanban System for Software Engineering
Agile Marketing
Rapid RTC
Entrepreneurial Operating System®
RSA
Agile Release Planning
ScrumMaster Tales
Sprint Iteration
Lean Agile Management
Professional Scrum with Kanban
Operational Value Stream
System Integration Environments
Scrum Master
Agile Outsourcing
Quality Assurance
Agile Basics
Video
Nexus and SAFe
Professional Scrum Master
Jira Plans
Software Development
TDD
The Kanban Method
Jira admin
Lean-Agile Software Development
SAFe Release Planning
Scrum and XP
Process Improvement
Agile Product Ownership
Agile Assembly Architecture
Artificial Intelligence
ATDD
SPC
Daily Scrum
Lean Agile
chatgpt
Perfection Game
AgileSparks
Logo
Enable registration in settings - general

Contact Us

Request for additional information and prices

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

This website uses Cookies to provide a better experience
Shopping cart