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:

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