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:

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