Post on 13-Dec-2015
KANBAN Dashboard – DEFINITIONKanban is a lean approach to agile software development.
At Toyota, Kanban is the term used for the visual & physical signaling system that ties together the whole Lean Production system.Most agile methods such as Scrum and XP are already well aligned with lean principles.
There are many flavors, but the core of Kanban means:
Visualize the workflowSplit the work into pieces, write each item on a card and put on the wall. Use named columns to illustrate where each item is in the workflow.Limit WIP (work in progress) Assign explicit limits to how many items may be in progress at each workflow state.Measure the lead timeAverage time to complete one item, sometimes called “cycle time”, optimize the process to make lead time as small and predictable as possible.
Kanban is a Japanese word that means “Visual Card“ or “Visual Signal”.
KANBAN Dashboard – DEFINITION
Lead Time = Custom ViewCycle Time = Internal View
BackLog
Analysis
ReadyIn
Progress
Development
ReadyIn
Progress
Test
ReadyIn
Progres
Documentation
ReadyIn
Progress
Training
ReadyIn
Progres
Acceptance
Doing Done
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
EXPEDITE
LEAD TIME
CYCLE TIME
KANBAN Dashboard – DEFINITIONWhat are the benefits of Kanban?Some commonly observed benefits are:
• Bottlenecks become clearly visible in real-time. This leads people to collaborate to optimize the whole value chain rather than just their part.
• Kanban avoids Mudas because it focuses more on delivery than on plans. Those delivery are Minimal Markatable Features (MMF) instead of stories.
• Provides a more gradual evolution path from waterfall to agile software development, thereby helping companies that previously have been unable or unwilling to try agile methods.
• Provides a way to do agile software development without necessarily having to use time-boxed fixed-commitment iterations such as Scrum sprints. Useful for situations where sprints don’t make much sense, such as operations and support teams with a high rate of uncertainty and variabilty.
• Quality issues become clearly visible.
(1) Muda (無駄 ) is a traditional Japanese term for an activity that is wasteful and doesn't add value or is unproductive
KANBAN Dashboard – DEFINITIONMinimum Marketable Feature
An MMF is different than a typical User Story in Scrum or Extreme Programming. Where multiple User Stories might be coalesced to form a single marketable feature, MMFs are a little bit bigger. Often, there is a release after each MMF is complete.
An MMF doesn’t decompose down into smaller sub-feature, but it is big enough to launch on its own.
A MMF can be represented as a User Story — a short, one-sentence description.
But in contrast to how a User Story is typically used, the team would not break down the User Story into smaller User Stories when using MMFs. Think of it this way: *Gather up all the stories that share the same so that clause — that’s your MMF*.
BackLog
Analysis
ReadyIn
Progress
Development
ReadyIn
Progress
Test
ReadyIn
Progress
Documentation
ReadyIn
Progress
Training
ReadyIn
Progres
Acceptance
Doing Done
EXPEDITE BUG X
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
REQ 1
BUG 123
KANBAN DASHBOARD ANATOMY Available resources
Expedite Work Items: must be processed with a Very High Priority. It uses Red (or pink) Post-its.
Each column has a clear definition about what it contains
Work items to process (Requirements, Change Requests, Bugs, Issues, Tasks…).It uses yellow Post-its.
WORK ITEMS FLOW COLUMNS
333 3 3
Work In Progress (WIP)Setting the WIP helps to focus to deliver what’s matter based on available resources.
ID: Created: / / Started: / /
Developed: / / Tested: / / Completed: / /
Author: Hard Deadline: / /
KANBAN Dashboard – Post-it Anatomy and Conventions
Two colors:• Red: expedite, those items must be processed before anything else• Yellow: normal priority work item. The priority can be overridden by
small red (pink) post itFor temporary work items, the ID comes from this generator:
http://sz-nas/IDGenTempWI.php
WORKITEM CARD
Stack Rank
Priority
123 …
Est.:
KANBAN Dashboard – Post-it Anatomy and ConventionsINDICATOR CARDS
Lore
m ip
sum
dolo
r si
t am
et,
con
sect
etu
r ad
ipis
cin
g e
lit.
Cu
rab
itu
r lib
ero
nis
i,
laore
et
ac
dic
tum
a,
ult
rici
es
id m
etu
s.
Inte
ger
ut
en
im lib
ero
URGENT
CH
RIS
TIA
N
RESOURCE
8163
PENDING ON SOMETHING
8163
BLOCKED
CH
RIS
TIA
N
PAUSED
Workitem Number or a
short description
when it applies
Workitem Number or a
short description
when it applies
Resource Name
Optional: the reason of the emergency
Resource Name – Who
is in charge of the paused workitem
KANBAN Dashboard – Post-it Anatomy and ConventionsPost-its can be combined
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse pharetra sapien eget
leo congue vitae bibendum neque lobortis. Praesent convallis odio tempor felis accumsan
ullamcorper. Nunc et nunc in odio facilisis placerat. Pellentesque nibh magna, consequat ut sagittis at, lobortis sed risus. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos. Integer ipsum ligula, porta non fermentum eu, imperdiet gravida
metus. Nunc varius, lectus a tempus molestie, tellus massa tincidunt velit, ac malesuada turpis
nulla ut augue.
RES
OU
RC
E 1
8163
Lore
m ip
sum
d
olo
r si
t am
et,
co
nse
ctetu
r ad
ipis
cing
elit
. C
ura
bit
ur
libero
nis
i, laore
et
ac
dic
tum
a, ult
rici
es
id
ID: 1234Lorem ipsum dolor sit amet, consectetur
adipiscing elit. Suspendisse pharetra sapien eget leo congue vitae bibendum neque lobortis.
Praesent convallis odio tempor felis accumsan ullamcorper. Nunc et nunc in odio facilisis
placerat. Pellentesque nibh magna, consequat ut sagittis at, lobortis sed risus. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos. Integer ipsum ligula, porta non fermentum eu, imperdiet gravida
metus. Nunc varius, lectus a tempus molestie, tellus massa tincidunt velit, ac malesuada turpis
nulla ut augue.
ID: 2354Aliquam risus enim, bibendum sed pellentesque
et, ullamcorper quis sem. Sed justo lacus, tempor at blandit sit amet, fermentum eget justo. Suspendisse sed nibh in nibh elementum
ullamcorper eleifend vel lorem. Aliquam vitae diam metus, a gravida lectus. Quisque vulputate dictum turpis, eget vulputate lorem sodales at.
Donec condimentum sagittis lorem ut ullamcorper. Suspendisse potenti. Sed ante
augue, aliquet at accumsan ut, aliquam quis ante. Vestibulum id venenatis augue. Fusce luctus faucibus libero eu faucibus. Nam turpis dolor, ultrices scelerisque viverra eget, bibendum eu
erat. Aenean pulvinar ultricies blandit.
RES
OU
RC
E 2
RES
OU
RC
E 1
BackLog
Analysis
ReadyIn
Progress
Development
ReadyIn
Progress
Test
ReadyIn
Progres
Documentation
ReadyIn
Progress
Training
ReadyIn
Progres
Acceptance
Doing Done
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
BUG 123
KANBAN Dashboard – SIMPLE WORKFLOW (1 BUG)
EXPEDITE
A Workitem is prioritized in TFS and ready to be processed in order of Priority and Stack Rank
Daily priorization : the bug is prioritized and ready to be fixed in order of Priority, Stack Rank and Available slots
The bug fix is started and assigned to a resource
BackLog
Analysis
ReadyIn
Progress
Development
ReadyIn
Progress
Test
ReadyIn
Progres
Documentation
ReadyIn
Progress
Training
ReadyIn
Progres
Acceptance
Doing Done
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
BUG 123
KANBAN Dashboard – SIMPLE WORKFLOW (1 BUG)
EXPEDITE
The bug is “Resolved”. Pending for QA validation
Daily priorization : the bug is prioritized and validated by QA
The bug is rejected and is high priority. Any bug rejected must be fixed ASAP.
BackLog
Analysis
ReadyIn
Progress
Development
ReadyIn
Progress
Test
ReadyIn
Progres
Documentation
ReadyIn
Progress
Training
ReadyIn
Progres
Acceptance
Doing Done
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
BUG 123
KANBAN Dashboard – SIMPLE WORKFLOW (1 BUG)
EXPEDITE
Daily priorization : the bug is prioritized and ready to be fixed in order of Priority, Stack Rank and Available slots
The bug fix is started and assigned to a resource
BackLog
Analysis
ReadyIn
Progress
Development
ReadyIn
Progress
Test
ReadyIn
Progres
Documentation
ReadyIn
Progress
Training
ReadyIn
Progres
Acceptance
Doing Done
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
BUG 123
KANBAN Dashboard – SIMPLE WORKFLOW (1 BUG)
EXPEDITE
The bug is “Resolved”. Pending for QA validation
Daily priorization : the bug is prioritized and validated by QA
Bug is closed!!!
BackLog
Analysis
ReadyIn
Progress
Development
ReadyIn
Progress
Test
ReadyIn
Progres
Documentation
ReadyIn
Progress
Training
ReadyIn
Progres
Acceptance
Doing Done
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
KANBAN Dashboard - WORKFLOW
EXPEDITE
A Workitem is prioritized and ready to be processed in order of Priority and Stack Rank
Daily priorization : the workitem is prioritized and ready to be procesed in order of Priority, Stack Rank and Available slots
It results in a task break down(smaller tasks). The Requirement goes to the Acceptance step pending completion of tasks.
High Level Analysis is started
Task11
Task12
Task13
REQ 1
T 1 1
Blue Post-it means “Paused” or pending on other items.
T 1 2T 1 3
BackLog
Analysis
ReadyIn
Progress
Development
ReadyIn
Progress
Test
ReadyIn
Progres
Documentation
ReadyIn
Progress
Training
ReadyIn
Progres
Acceptance
Doing Done
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
KANBAN Dashboard - WORKFLOW
EXPEDITE
REQ 1
Task13
DEV
QA
DOC
Analysis started
Ready for coding
Analysis started
Pending to perform tests
Coding
Documentation can be started
Task12
Task11
T 1 1
Ready to perform tests
Testing
T 1 1T 1 2T 1 3
CodeTeste
d
Start Documentation
Ready to validate
Validating
Green Post-it means “Done”.
BackLog
Analysis
ReadyIn
Progress
Development
ReadyIn
Progress
Test
ReadyIn
Progres
Documentation
ReadyIn
Progress
Training
ReadyIn
Progres
Acceptance
Doing Done
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
KANBAN Dashboard - BUGS on Requirements or Change Requests
EXPEDITE
REQ 1
Task13
Task12
Task11
T 1 2T 1 3
7 2 6 7
Task72
BUG 67
The tests are pending on the bug #72 &67. #67 is a show stopperBefore
Releasing Bug #72 and 67
must be fixed
BackLog
Analysis
ReadyIn
Progress
Development
ReadyIn
Progress
Test
ReadyIn
Progres
Documentation
ReadyIn
Progress
Training
ReadyIn
Progres
Acceptance
Doing Done
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
KANBAN Dashboard – PAUSED WORKITEMS & EXPEDITES
EXPEDITE
REQ 1
Task13
Task12
Task11
T 1 2T 1 3
7 2 6 7
Task72
BUG 67
BUG X
A very high priority workitem
appearsA A
A resource is assigned to the expedite and
his/her current task is paused.
When the expedite if done, all comes back to normal.
KANBAN Dashboard – Post-it Anatomy and ConventionsHow to use resources when in a “In progress” column
ID: 1234Lorem ipsum dolor sit amet, consectetur
adipiscing elit. Suspendisse pharetra sapien eget leo congue vitae bibendum neque lobortis.
Praesent convallis odio tempor felis accumsan ullamcorper. Nunc et nunc in odio facilisis
placerat. Pellentesque nibh magna, consequat ut sagittis at, lobortis sed risus. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos. Integer ipsum ligula, porta non fermentum eu, imperdiet gravida
metus. Nunc varius, lectus a tempus molestie, tellus massa tincidunt velit, ac malesuada turpis
nulla ut augue.
ID: 2354Aliquam risus enim, bibendum sed pellentesque
et, ullamcorper quis sem. Sed justo lacus, tempor at blandit sit amet, fermentum eget justo. Suspendisse sed nibh in nibh elementum
ullamcorper eleifend vel lorem. Aliquam vitae diam metus, a gravida lectus. Quisque vulputate dictum turpis, eget vulputate lorem sodales at.
Donec condimentum sagittis lorem ut ullamcorper. Suspendisse potenti. Sed ante
augue, aliquet at accumsan ut, aliquam quis ante. Vestibulum id venenatis augue. Fusce luctus faucibus libero eu faucibus. Nam turpis dolor, ultrices scelerisque viverra eget, bibendum eu
erat. Aenean pulvinar ultricies blandit.
LA
UM
AN
CH
RIS
TIA
N
JAC
KY
ID: 2784Aliquam risus enim, bibendum sed pellentesque
et, ullamcorper quis sem. Sed justo lacus, tempor at blandit sit amet, fermentum eget justo. Suspendisse sed nibh in nibh elementum
ullamcorper eleifend vel lorem. Aliquam vitae diam metus, a gravida lectus. Quisque vulputate dictum turpis, eget vulputate lorem sodales at.
Donec condimentum sagittis lorem ut ullamcorper. Suspendisse potenti. Sed ante
augue, aliquet at accumsan ut, aliquam quis ante. Vestibulum id venenatis augue. Fusce luctus faucibus libero eu faucibus. Nam turpis dolor, ultrices scelerisque viverra eget, bibendum eu
erat. Aenean pulvinar ultricies blandit.
1 resource assigned
2 resources assigned
Not task can be in progress without an assigned resource except if there is a signal (paused, blocked…) that can explain why
KANBAN Dashboard – Post-it Anatomy and ConventionsHow to use resources when in a “Ready” column
ID: 1234Lorem ipsum dolor sit amet, consectetur
adipiscing elit. Suspendisse pharetra sapien eget leo congue vitae bibendum neque lobortis.
Praesent convallis odio tempor felis accumsan ullamcorper. Nunc et nunc in odio facilisis
placerat. Pellentesque nibh magna, consequat ut sagittis at, lobortis sed risus. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos. Integer ipsum ligula, porta non fermentum eu, imperdiet gravida
metus. Nunc varius, lectus a tempus molestie, tellus massa tincidunt velit, ac malesuada turpis
nulla ut augue.ID: 2784
Aliquam risus enim, bibendum sed pellentesque et, ullamcorper quis sem. Sed justo lacus, tempor
at blandit sit amet, fermentum eget justo. Suspendisse sed nibh in nibh elementum
ullamcorper eleifend vel lorem. Aliquam vitae diam metus, a gravida lectus. Quisque vulputate dictum turpis, eget vulputate lorem sodales at.
Donec condimentum sagittis lorem ut ullamcorper. Suspendisse potenti. Sed ante
augue, aliquet at accumsan ut, aliquam quis ante. Vestibulum id venenatis augue. Fusce luctus faucibus libero eu faucibus. Nam turpis dolor, ultrices scelerisque viverra eget, bibendum eu
erat. Aenean pulvinar ultricies blandit.
No resource assigned
Task “ready” cannot have an assigned resourceL
AU
MA
N
BackLog
Analysis
ReadyIn
Progress
Development
ReadyIn
Progress
Test
ReadyIn
Progres
Documentation
ReadyIn
Progress
Training
ReadyIn
Progres
Acceptance
Doing Done
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
KANBAN Dashboard – Resource Overloaded
EXPEDITE
BUG 123
BUG 234
BUG 345
BUG 789
One resource must be able to focus and
cannot have too much task assigned.
BackLog
Analysis
ReadyIn
Progress
Development
ReadyIn
Progress
Test
ReadyIn
Progres
Documentation
ReadyIn
Progress
Training
ReadyIn
Progres
Acceptance
Doing Done
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
KANBAN Dashboard – Unbalanced Work / Bottlenecks
EXPEDITE
QA is overloaded
BUG 123
BUG 234
BUG 345BUG 987
BUG 876
BUG 765
BUG 654
BUG 456
BUG 567
BUG 101
BUG 789
BUG 202
DEV is underloaded
BackLog
Analysis
ReadyIn
Progress
Development
ReadyIn
Progress
Test
ReadyIn
Progres
Documentation
ReadyIn
Progress
Training
ReadyIn
Progres
Acceptance
Doing Done
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
ColumnDefinition
KANBAN Dashboard – Help to identify Quality Issues
EXPEDITE
BUG 123 BUG
456
BUG 567
BUG 789
BUG XXX
BUG XXXBUG XXX
BUG XXX
BUG XXX
BUG XXX
BUG XXX
BUG XXXBUG XXX
BUG XXX
BUG XXX
BUG XXX
BUG XXX
BUG XXXBUG XXX
BUG XXX
BUG XXX
BUG XXX
BUG XXX
BUG XXXBUG XXX
BUG XXX
BUG XXX
BUG XXX
BUG XXX
BUG XXXBUG XXX
BUG XXX
BUG XXX
BUG XXX
BUG XXX
BUG XXXBUG XXX
BUG XXX
REQ 444
BUG XXX
BUG XXXBUG XXX
BUG XXX
BUG XXX
BUG XXX
BUG XXX
BUG XXXBUG XXX
BUG XXX
BUG XXX
BUG XXX
BUG XXX
BUG XXXBUG XXX
BUG XXX
BUG XXX
BUG XXX
BUG XXX
BUG XXXBUG XXX
BUG XXX
BUG XXX
BUG XXX
REQ 444
X X X X X X X X
X X X X X X X X
X X X X X X X X
X X X X X X X X
X X X X X X X X
X X X X X X X X
X X X X X X X X
X X X X X X X X
Too many bugs. Causes:• Specs unclear• Hardware issues• Legacy Code• Too short delays• Lack of reporting
(issues, impediments…)
• Test Plan not appropriate
• Lack of Good Practices (coding, review, …)
• Lack of Design• No test programs• …