The document describes a visualization called the "Volcano Kanban Board" which plots product backlogs, teams, and ongoing work in a volcano-shaped diagram. It shows teams in "swim lanes" pulling stories from prioritized product backlogs to mark as ongoing work. As teams complete stories, their capacity opens to pull new work and replenish the volcano. This maintains a continuous flow of work to teams based on priority while visualizing overall progress.

1. The Volcano - Enterprise
kanban board
2015-11-23, Tomas Rybing, Aptilo Networks

2. My other visualizations
https://theagileist.wordpress.com/2015/06/22/the-arrow-advanced-kanban-board/
The Arrow - Advanced kanban boardPriority pyramid
https://theagileist.wordpress.com/2014/12/08/priority-pyramid/
Mirrored kanban board
https://theagileist.wordpress.com/2015/08/31/mirrored-kanban-board/
Product radar
https://theagileist.wordpress.com/2015/10/05/product-radar/

3. The Volcano - Design for kanban board
TEAM 1 - EXPEDITE (FAST LANE)
ANALYS.DES.DEV.TESTDEPL.
Visible DoDs for each step
ONGOING
TEAM 2 - EXPEDITE (FAST LANE)
ANALYS.DES.DEV.TESTDEPL.
Visible DoDs for each step
ONGOING
TEAM 3 - EXPEDITE (FAST LANE)
ANALYS. DES. DEV. TEST DEPL.
Visible DoDs for each step
ONGOING
TEAM 4 - EXPEDITE (FAST LANE)
ANALYS. DES. DEV. TEST DEPL.
Visible DoDs for each step
ONGOINGP1 - ”next”
PRODUCT A PRODUCT B PRODUCT C
P2 - ”soon”
P3 - ”later, maybe”
= System improvements
= Features
= Bugs
SERVICE CLASSES

4. The Volcano - Example
TEAM 1 - EXPEDITE (FAST LANE)
ANALYS.DES.DEV.TESTDEPL.
Visible DoDs for each step
ONGOING
TEAM 2 - EXPEDITE (FAST LANE)
ANALYS.DES.DEV.TESTDEPL.
Visible DoDs for each step
ONGOING
TEAM 3 - EXPEDITE (FAST LANE)
ANALYS. DES. DEV. TEST DEPL.
Visible DoDs for each step
ONGOING
TEAM 4 - EXPEDITE (FAST LANE)
ANALYS. DES. DEV. TEST DEPL.
Visible DoDs for each step
ONGOINGP1 - ”next”
PRODUCT A PRODUCT B PRODUCT C
P2 - ”soon”
P3 - ”later, maybe”
= System improvements
= Features
= Bugs
SERVICE CLASSES

5. The Volcano - Explained
P1 - ”next”
PRODUCT A PRODUCT B PRODUCT C
P2 - ”soon”
P3 - ”later, maybe”
TEAM 2 - EXPEDITE (FAST LANE)
ANALYS. DES. DEV. TEST DEPL.
Visible DoDs for each step
ONGOING
TEAM 1 - EXPEDITE (FAST LANE)
ANALYS.DES.DEV.TESTDEPL.
Visible DoDs for each step
ONGOING
= System improvements
= Features
= Bugs
SERVICE CLASSES
The volcano is empty and needs
to be filled, for example from a
visual planning meeting.

6. The Volcano - Explained
TEAM 2 - EXPEDITE (FAST LANE)
ANALYS. DES. DEV. TEST DEPL.
Visible DoDs for each step
ONGOING
TEAM 1 - EXPEDITE (FAST LANE)
ANALYS.DES.DEV.TESTDEPL.
Visible DoDs for each step
ONGOING
= System improvements
= Features
= Bugs
SERVICE CLASSES
Ok, now the teams can move
stories to their ”swim lanes” to
mark them as ”ongoing”. Note! I
will only use two ”swim lanes” per
team in this example to keep it
simple.
P1 - ”next”
PRODUCT A PRODUCT B PRODUCT C
P2 - ”soon”
P3 - ”later, maybe”

7. The Volcano - Explained
TEAM 2 - EXPEDITE (FAST LANE)
ANALYS. DES. DEV. TEST DEPL.
Visible DoDs for each step
ONGOING
TEAM 1 - EXPEDITE (FAST LANE)
ANALYS.DES.DEV.TESTDEPL.
Visible DoDs for each step
ONGOING
= System improvements
= Features
= Bugs
SERVICE CLASSES
Team 1 takes two in P1 from
product A. Team 2 takes one
each from Product B & C.
P1 - ”next”
PRODUCT A PRODUCT B PRODUCT C
P2 - ”soon”
P3 - ”later, maybe”

8. The Volcano - Explained
TEAM 2 - EXPEDITE (FAST LANE)
ANALYS. DES. DEV. TEST DEPL.
Visible DoDs for each step
ONGOING
TEAM 1 - EXPEDITE (FAST LANE)
ANALYS.DES.DEV.TESTDEPL.
Visible DoDs for each step
ONGOING
= System improvements
= Features
= Bugs
SERVICE CLASSES
Team 1 and 2 starts working.P1 - ”next”
PRODUCT A PRODUCT B PRODUCT C
P2 - ”soon”
P3 - ”later, maybe”

9. The Volcano - Explained
TEAM 2 - EXPEDITE (FAST LANE)
ANALYS. DES. DEV. TEST DEPL.
Visible DoDs for each step
ONGOING
TEAM 1 - EXPEDITE (FAST LANE)
ANALYS.DES.DEV.TESTDEPL.
Visible DoDs for each step
ONGOING
= System improvements
= Features
= Bugs
SERVICE CLASSES
Work continues… I fast forward a
bit now.
P1 - ”next”
PRODUCT A PRODUCT B PRODUCT C
P2 - ”soon”
P3 - ”later, maybe”

10. The Volcano - Explained
TEAM 2 - EXPEDITE (FAST LANE)
ANALYS. DES. DEV. TEST DEPL.
Visible DoDs for each step
ONGOING
TEAM 1 - EXPEDITE (FAST LANE)
ANALYS.DES.DEV.TESTDEPL.
Visible DoDs for each step
ONGOING
= System improvements
= Features
= Bugs
SERVICE CLASSES
Team 2 has finished first story
and have capacity free (empty
”swim lane”). They continue to
work with product B and pick that
story from P1.
P1 - ”next”
PRODUCT A PRODUCT B PRODUCT C
P2 - ”soon”
P3 - ”later, maybe”

11. The Volcano - Explained
TEAM 2 - EXPEDITE (FAST LANE)
ANALYS. DES. DEV. TEST DEPL.
Visible DoDs for each step
ONGOING
TEAM 1 - EXPEDITE (FAST LANE)
ANALYS.DES.DEV.TESTDEPL.
Visible DoDs for each step
ONGOING
= System improvements
= Features
= Bugs
SERVICE CLASSES
The weekly priority meeting
replenish the volcano.
P1 - ”next”
PRODUCT A PRODUCT B PRODUCT C
P2 - ”soon”
P3 - ”later, maybe”

12. The Volcano - Explained
TEAM 2 - EXPEDITE (FAST LANE)
ANALYS. DES. DEV. TEST DEPL.
Visible DoDs for each step
ONGOING
TEAM 1 - EXPEDITE (FAST LANE)
ANALYS.DES.DEV.TESTDEPL.
Visible DoDs for each step
ONGOING
= System improvements
= Features
= Bugs
SERVICE CLASSES
Team 1 continues to work with
product A and pick that story
from P1. And then it continues
like this…
P1 - ”next”
PRODUCT A PRODUCT B PRODUCT C
P2 - ”soon”
P3 - ”later, maybe”