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:

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