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:

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