add use

electronic
column to
tool to
board
enforce
1
WiP and make group training -
the team discussions tools or
accountable of why? framework?
Both WIP's are
there needs to be
over. What can discussion about
we do to move enforcing/maintaining
WiPs
these along? Add
Acceptance
Add better

2 Revisit, or be Column
discovery
explicit with upfront
your policies (feedback
how many team column?)
no item members? should
WiP be recalculated? Add
aging or is this WiP/person,
maybe not a pure
kanban thought, but
isn't this why we love Refinement
information rather than per
column?
product owners and
scrum masters, to
column
protect the team from
requests?

what do the Do any of the

What action is What's the teams
different colors team's What is in What are
CFD1 expected How important How big is progress
characteristics of existing
mean? so much this Is this ready to confidence
urgent? policies cover
information, from UA to is this
work? Met level in taking right now?  this?
unplanned unplanned this on?
without a key! Prod? item? item?
entry criteria

Any historical
What are we How do we what is the data, or past
NOT going to What is the
comm. to What's our similar situations,
Funnel, Disc do if we do cost of criteria of we can look at? 
customer of current WIP?
this work? delaying the "urgent"?
& Build are likelihood of
completion?
Can we do
release?
this?
higher WIP
than UA GROUP 1 if this comes
in, what
GROUP 1
comes out?

Why is one What is the state of

story left in the items in User
Acc?  Will all these
the Input items make it in the
release?
Q?
CFD2

Are there
what's wrong
Colors add'l steps
with the item
indicate? to release
in Input?

Tools can enable and/or inhibit us. Consider what

the items?

There are 5 items in Lack of flow.  Not

tools you use now for your Agile adoption and how
User Acc.  The WIP much in progress
what is the
Limit is 1. Why? Is behind User Acc. It team doing?
something blocking could be awhile nothing is in
the ability to before the next
release? release. progress...

they might help/hinder your Kanban implementation.

List the Pros and Cons you have experienced. GROUP 2
GROUP 2

Pros Cons
Forces you Jira doesnt
Streamline to follow a
specific have the
our decision workflow best report
making tools
process
Blocked
Column
Lots of
No release
blocked
Jira - very or done? 
stories
Automated particular with
Customisable
Not always
generation metrics by
workflow easy to use
of charts / visualisation
framework (can't Why
metrics get kanban metrics how does what
happens to
blocked?
on scrum board) "blocked" fit into
the overall items in What
process flow?
Blocked? stage?
Make work See it from Constrains
visible anywhere improvement Jira - more
not a clear view really wish we Gives the Why does the WIP
teams, seems of flow -- what had item impression
limit of Discovery
exceed User Acc? 
to cause issues happens after aging -- just we can start These things A funnel is created. 
"user not enough Bottleneck
new work. are going
and acceptance"? info! are WIP
1 source of In these times, hinderences Limits.
truth we need
electronic tools Questions to the team
to sync-up Where are they blocked?
Can we use a visual marker to show it's blocked GROUP 3 GROUP 3

Maybe cancel
the release if
nothing
Why are the  why are there comes out
so many blocks?
WiPs being needs
ignored?  conversation!

what is the since every active

work work item is
blocked, is there a
agreement for larger story -- is
handling there an external
blocks? factor?

GROUP 4
GROUP 4