Workshop for the Database Management Services team at University of Michigan Medical school where they reviewed a strategy canvas, created a team canvas, decided on a methodology, played a lean game to learn a pull versus a push workflow and built a team kanban board.
1. @_AprilJefferson CuriousAgility.blogspot.com
Team Transformation Workshop
Working Agreements
Big
Picture
9:30
Review Strategy
Canvas
30 MINS
Create Team Canvas
60 MINS
Break
15 MINS
Style
11:15
Review Options
30 MINS
Decide
15 MINS
Lunch Break
30 MINS
Pull
Systems
12:30
Lean Simulation
60 MINS
Review Options
30 MINS
Break
15 MINS
Design Workflow
90 MINS
End
4:00
29. Scrum Kanban Scrumban
Board/Artifacts
simple board
product backlog
sprint backlog
product increment
burndown chart
board mapped on the process board mapped on the process
Ceremonies
daily Scrum
sprint planning
sprint review
sprint retrospective
none required
daily Scrum
other Scrum related ceremonies if
needed
Prioritization Part of backlog grooming. Done by PO
Out of the process. There should be a
prioritized backlog.
Out of the process. There should be a
prioritized backlog.
Who feeds the work in
progress ("brings new
work")
PO
Depends on defined roles and
necessities
Depends on defined roles and
necessities
Iterations yes (sprints) no (continuous flow)
not mandatory (continuous flow); could
have sprints
Estimations yes (in ideal days or story points) no (similar work size items) (a) no (similar work size items) (a)
Teams recommended cross functional cross functional or specialized cross functional or specialized
Roles
Product Owner
Scrum Master
Team
as needed Team + as needed
Teamwork collaborative based on pull approach based on pull approach
WIP planned for the duration of the sprint controlled by workflow state controlled by workflow state
changes to work scope should wait for next sprint added as needed (JIT) added as needed (JIT)
Product backlog
prioritized list of user stories
(estimated)
no (JIT) no (JIT)
Impediments addressed immediately addressed immediately (b) addressed immediately (b)
When does it fit?
Product development
Small value adding increments
development possible
Requirements are in good shape
Support/maintenance work
(operational level)
Product development (unclear vision)
Evolving requirements (no clear
roadmap)
Need to include support/maintenance
(event driven) work in the process
(a) team needs to comment on non-fitting work items in order to ensure readiness
(b) "stop the line" approach; teams should swarm to solve the impediment
http://www.ontheagilepath.net/2013/09/scrum-kanban-scrumban-fast-overview-and.html#sthash.zTUaNzB7.dpuf
36. @_AprilJefferson CuriousAgility.blogspot.com
Choose a Role
BA picks 6 post-its and passes them to Technical
Analyst
TA puts on yellow dots
Designer puts on red dot
UX DEV puts on green dots
DEV puts on blue dots
Tester tests putting in defect area if it doesn’t look like
sample
Project Manager times
Time it takes for first batch to be completed
Warms team when there is one minute left
Tells team when time is out (after 5 minutes)
Customer accepts or rejects
38. @_AprilJefferson CuriousAgility.blogspot.com
Round 1
5 MIN Each role should work as fast as
they can
Don’t worry if the person next to
you is keeping up
Remember you are working in
batches
Do 6 at a time then handoff all 6
at the same time
43. @_AprilJefferson CuriousAgility.blogspot.com
BATCH VS LEANInputArea
Backlog
WorkArea
Empty
OutputArea
Occupied
InputArea
Backlog
WorkArea
Empty
OutputArea
Empty
Push Pull
If work area empty then take from
input area
If work area empty and output
area empty then take from input
area
61. @_AprilJefferson CuriousAgility.blogspot.com
Pair Up then Put on Your Designer
Hat!
Choose
Share
Refactor
Design
Define
Design
workflow
proposal
with a
Kanban
30 MINS
Each
pair
gives
elevator
pitch
Team
identifies
what
they like
about it
10 MINS
Team
picks
board for
final
group
refactor
5 MINS
Team
uses
feedback
to revise
design
together
20 MINS
Decide
on the
policies
for each
part of
workflow
25 MINS
69. Sources
Thanks!
Lean Change Management
Jason Little, LeanChange.org
Methodology Comparison
http://www.ontheagilepath.net/2013/09/scrum-kanban-scrumban-fast-overview-
and.html#sthash.zTUaNzB7.dpuf
Lean Dot Game
http://www.netobjectives.com/system/files/DotGame_vas11_0.pdf
Sample Kanban Boards
Mattias Skarin, blog.crisp.se/mattiasskarin
Random Boards from Google images that were not copyrighted
Peer Consulting
Gerry Kirk, GerryKirk.org