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:

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