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:

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