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:

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