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:

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