によって Alex Ostreiko 2年前.
125
Retros
In team retrospectives, especially when involving remote members, it's crucial to include all participants equally. Tools like Scatter Spoke, Realtimeboard, and Retrium facilitate this.
によって Alex Ostreiko 2年前.
125
もっと見る
was extended with 2 more additional phases to help start and conclude the meeting in the context of Software Development
first 3 phases
decide
now what?
analyze
so what?
what?
Virginia Satir Interaction Model
how we respond to things
Human Systems Dynamics Institute
Liberating Structures
What? So What? Now What?
Adaptive Action format
Institute for Cultural Affairs (Canada)
ORID
Decision
Interpretation
Reflection
Observation
The Art of Focused Conversation
diverge, converge
--Norm Kerth, Project Retrospectives: A Handbook for Team Review
retro is a fundamentally vulnerable exercise
ensure safety
because we give feedback
appreciations
everyone here is a hero: you contributed something special, something from the heart this last Iteration
each person can take turns giving their appreciations
pick one item to resolve
prioritize quickly then spend more time on resolutions
invisible work
workflow improvements
experiments
how healthy are these processes?
what processes do we have on the team
communication w/client
planning
QA
execution
Mastery
Purpose
Autonomy
inspection
code reviews
transparency
burnup charts
adaptation
testing
have an advocate in the room
the hands of the remote person
put up stickies, etc.
AKA "sticky buddies"
bottleneck when everyone is waiting for you to solve issues
we want Team to learn to find solutions
poke at the problem
refrain from offering the "how" unless impasse
e.g.
did I do everything to capitalize on the strengths of the team
e.g. capacity
were my stories small enough for the team?
when filling 4Ls talk about how to improve your work, not theirs
Read between the lines
what can we do to make it easier for them in short and long term?
My Worst Nightmare
20/20 Vision
Show and Tell
Give them a Hot Tub
Actions Centered
Product Box
Prune Product Tree
have team arrange stickies into categories, then dot-vote (3 each)
then switch workers & managers, and trust workers to do the stepping in their own
what were the managers doing when they weren't micromanaging?
managers tell workers where to step (one at a time), count steps
the facilitator is a moving obstacle
Thinking in Bets by Annie Duke
CEO congratulating team on success
team
personal/professional development
product
choose out of 3
team influences
the soup
Close the Retro
debrief
Decide What to Do
diverge/converge on top 3 items
each person debriefs
open discussion 5 minutes
or vote
decide if continue
each person talks 1 minute
Generate insights
vote on them
dot voting in Miro
put a star in Google Docs
group them
list important items
A table in Google Docs
use
Zoom whiteboard
Miro
Jamboard
Trello
call them like there were a person at the whiteboard (like we did pre-pandy)
Gather Data
Iteration Report will have provided stats
Set Stage
check in
What were some of your neighbour's victories in the last two weeks?
how was it for the person next to you?
heroes
something that person next to you did that was helpful
Items
summarize
process updates
learnings
all docs
update Runbooks to reflect changes in process
learn workflow
keep WIP to a minimum
recurring craftsmanship meetings
core protocols to decide
how do we efficiently decide/vote
all work should be reperesented in Jira cards
workshop
TRIZ
Agile Starfish
use Google Drawing
Remember the Future
review Radar chart together
Start-Stop-Continue
space for Ideas and Actions
Sailboat
particularly useful to strengthen team identity
chunk down
use SMART
Specific, Measurable, Actionable, Realistic, Time-bound
team spirit is good, but not actionable
everyone present at Standup on time is specific and actionable
first define success
1-2-4-All
practice organizing into groups and solving a problem
similar to counting to 20
Check-In
options
say something personal
hobby
siblings
first job
pets
one positive observation
Count to 20 as a group w/out repeating
collaboration
paying attention
coordination
each number must be said only once
1 word
pick a feeling from NVC inventory
Intro
Double Diamond
leadership is part of the job
you are all leadears
do experiments
ask questions
you are empowered by your responsibilities
your authority comes from our shared commitment to the success of this team and this organization
great values and opportunities to improve, still flexible
Prime Directive
10 minutes
keep private!
add 5th column
Gratitude/Appreciation
Liked
things you really liked
What went better than expected?
Learned
Lacked
where you came in short
e.g. lack of knowledge of SQL window functions caused us to take longer than expected
things you have seen the team doing, but consider that could be done better.
Longed For
something you desired or wished for
e.g. paid version of Miro
Scope changes
stop/start work on a story
number of points
number of stories
defect count
velocity
charts
meetings
decision points
team membership
milestones
celebrations
new technologies
The agreement is owned by the Team. The Team enforces it.
no phones during standup
do not create tech debt
boy scout rule
Harry Potter
Captain Lorca
Forrest Gump
Darth Vader
thrilled/bored/curious, etc.
a dirty laundry meeting
