Team Transformation Workshop

@_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

TRANSFORMATION
CANVAS
Agree
on
Change
Negotiate
the
Change
Validate
Behavior
Verify
Performanc
e

Why Transformation Canvas?
Discovery
• What’s Really Going On
• Most Valuable Change
Transparency • Urgency for Change
Visibility • Changes Being Made
Alignment
• Change Agents
• Open and Honest Dialogue

Process Pushing Machine
Change Team as a Support Group

Look at Improvement Strategy with Change
Options of Change Agents
Big Picture Review

What Change Are We Making?

Why is this Change Important?

How Will We Measure
Success?

How Will We Demonstrate
Progress?

Who Are Affected By This
Change?

What Investments Are Needed?

How Will We Help People
Transition?

How Will Change Be Made
Visible?

Change Options

The Enabling of Strategic Synergies
Between All Affected Parties
Calling Shenanigans!

How Will We Do This?
Powerful
Questions
Silent
Brainstorming
One thought
per sticky
Review as a
Group
Discuss and
refactor

What
words/phrases
stuck out for you?

What was
interesting to you?

What did you find
worrisome about
this canvas?

What is supporting
this change?

What is working
against this
change?

How can your team
contribute to this
vision?

What help would
you need to
contribute to this
vision?

Feedback Driven Change Process
Now What?

Strategy Canvas
Team Canvas
Feedback and Iterate
• Share with Change Agents
• Explore Similarities and
Differences
• Make Changes from
Feedback

Feedback
 Please score this session on a sticky
5 Awesome to 1 Needs Work
If below 5 include what would make it better
Place Sticky on door under “Big Picture”

15 MINUTE BREAK

STYLE
How Will We Do Agile/LEAN?

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

What works for
you?

Feedback
Place Sticky on door under “Style”

30 MINUTE LUNCH BREAK

PULL SYSTEMS
Learn, See, Create

Game to demonstrate LEAN principles
Lean Simulation

Dot Game
Complete features
which are defined to
be 1 yellow sticky note
that has 6 colored
stickers in the
following pattern
B B
G R
Y G

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

Get in Position
Designer
IN Area
(materials)
UI
Developer
Technical
Analyst
Developer
Business
Analyst
Tester
OutArea

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

So how many
accepted?

What Is Our . . .
 (WIP)Work In Progress = Stickys
Started
 (TP) Throughput = Stickys Done/5
MINS
 (CT)Cycle Time = WIP/TP MINS

What Did We Learn?
WIP Rises with
Bottlenecks
Cycle Time Unstable &
Unpredictable

How Could We Improve?
 Smooth Flow
 Increase Productivity and Quality
Minimize WIP
Pull instead of Push
Slow Down to Speed
Up

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

Round 2
5 MIN  Minimize WIP
Finish Before You Start
Set Limits
 Quality Matters
B B
G R
Y G

What Did We Learn?
Bottlenecks Gone
Cycle Time
Improved

How Could We Improve?
 Smooth Flow
Balancing Number of Dots
“In Place” Testing
Talking to Customer
Remove Waste & Get
Feedback

Round 3
5 MIN  Maximize Throughput

What Did We Learn?
Cycle Time Stable
& Predictable
without Bottlenecks
& with Smooth
Flow!

Feedback
Place Sticky on door under “Dot Game”

What Are The Possibilities?
10
MINS
 Review Examples Around
Room
 Silently Identify Observations
1Thought per Sticky
Adhere to Board
Avoid Duplicates

What Did We Learn?
2 MINS
EACH Quickly
Discuss
Observations
Together

Feedback
Place Sticky on door under “Kanban Boards”

An inspection and adaption using lean
principles
So What’s Our Workflow?

What kinds of work
do we want to
visualize? Why?

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

Design Board
Choose
Share
Refactor
Design
Define
Design
workflow
proposal
with a
Kanban
20 MINS

Share Board
Choose
Share
Refactor
Design
Define
Each
pair
gives
elevator
pitch
Team
identifie
s what
they like
about it
20
MINS

Choose Board
Choose
Share
Refactor
Design
Define
Team
picks
board
for final
group
refactor
5 MINS

Refactor Board
Choose
Share
Refactor
Design
Define
Team
uses
feedback
to revise
design
together
20 MINS

Define Rules
Choose
Share
Refactor
Design
Define
Decide
on the
policies
for each
part of
workflo
w
25
MINS

Feedback
Place Sticky on door under “Workflow Design”

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

BLOG
CuriousAgility.Blogpost.com
TWITTER
@_AprilJefferson

Team Transformation Workshop

Recomendados

Recomendados

Más contenido relacionado

La actualidad más candente

La actualidad más candente (18)

Destacado

Destacado (8)

Similar a Team Transformation Workshop

Similar a Team Transformation Workshop (20)

Último

Último (20)

Team Transformation Workshop