Search
Close this search box.
Search
Close this search box.
Search
Close this search box.

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:

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