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:

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