Retro is back - How to Run Retrospective Meetings That Work, Anat (Alon) Salhov @Producttank TLV, Feb' 2020

•

0 likes•142 views

Have you ever had that nightmare where you are constantly running only to remain in the same spot? It's all too easy for teams to have the same experience: repeating the same mistakes, working hard... but not really getting anywhere. In order to move forward and excel, we must step outside that loop once in a while to reflect on their recent work and achievements. Armed with a few lesson-learned, they can iterate on their processes and improve. In ProductTank TLV’s upcoming meetup, Anat Salhov shared with us the best practices to create Retrospective Meetings that provide a safe space for the team to review and discuss what works well (and what doesn't!) for continuous improvement.

Leadership & Management

• What is a retrospective (meeting) ?
• How often should we do a retrospective ?
• Recommended practice for retrospective
• Pre-conditions for effective retrospective
• References

Agile Manifesto - principle #12
“At regular intervals, the team reﬂects on how to
become more effective, then tune and adjust its
behaviour accordingly.”

“There are no Best Practices
only Good Practices that
worth trying”

1.Check-in / set the stage (5-10 min)
2.Gather Data (5-15 min)
3.Generate insight (10-30 min)
4.Decide what to do (15-30 min)
5.Closing (0-10 min)

1.Check-in / set the stage (5-10 min)
2.Gather Data (5-15 min)

1.Check-in / set the stage (5-10 min)
2.Gather Data (5-15 min)
3.Generate insight (10-30 min)
BLAMEHOW? WHAT?

1.Check-in / set the stage (5-10 min)
2.Gather Data (5-15 min)
3.Generate insight (10-30 min)
4.Decide what to do (15-30 min)

RETROSPECTIVE STRUCTURE
Opening Appreciate someone
Shortly discuss previous experiment/s
Gather Data Team radar
Generate Insight Five Whys
Decide What To Do Perfection Game
Closing Retro Darts

REFERENCES
1.retromat: https://retromat.org/
2.Agile retrospective book
recommendation:
3.For advanced - trello board:
https://trello.com/b/kC3rMYhh/retrospect
ive-techniques

Pre-conditions for
effective
retrospective

Avoiding
conflict
Say what the
manager want
to hear
boring
The same
people talk
all the time
Waste of
time
The same
AI all
the time
General AI
The problem
is not with us
No one
participate

Who's in the room?
The facilitator role
Planning
Play games

What does trust mean?
"People who aren’t afraid to admit
the truth about themselves”
Patrick
Lencioni

RETROSPECTIVE (20
MINS)
Opening One Word
Gather Data Starﬁsh
Generate Insight Silent Grouping
Decide What To Do
Dot vote one idea from the largest
group
Closing Know your neighbor

RETROSPECTIVE
STRUCTUREOpening If we were a vehicle…
Shortly discuss previous experiment/s
Gather Data Aladdin’s Lamp
Generate Insight Value / Cost chart
Decide What To Do Agree one wish
Closing ROTI

OVERALL
RETROSPECTIVE
Opening Which minister in the government?
Gather Data Wedding (Old, New, Browed, Blue)
Generate Insight Fish Bowl
Decide What To Do Divide the dollar
Closing
Keep in touch (Need help Can
help)

RETROSPECTIVE
STRUCTUREOpening Admit a mistake
Shortly discuss previous experiment/s
Gather Data Write down 3-4 events that happened
Generate Insight Keep Change Expected Surpried chart
Decide What To Do Design an experiment canvas
Closing Appreciate yourself

The document discusses retrospective techniques for reviewing and improving projects. A retrospective involves learning from experience to plan improvements for future efforts. It follows a structured process of setting the stage, gathering data about what went well and poorly, generating insights from the data, and deciding on actions. The facilitator prepares the retrospective by choosing topics and exercises and handles different personalities and cultures during the session. Closure involves identifying actions but consideration of energy levels is important.

Ale2012 retrospective

Marc Löffler

The document discusses ways to make retrospectives for agile software development teams more engaging and effective. It suggests adding hypotheses to retrospectives to give them more purpose and focus. Various metaphor-based retrospective formats are presented, like using soccer or cooking terms, to help teams think differently. The key ideas are that retrospectives need purpose and new perspectives to avoid repetition and keep people motivated to work on identified issues.

Retrospectives session agile tours 2012 bru

Steve Conard

The document provides guidance on how to conduct effective retrospectives. It outlines a flexible five-step framework: 1) Set the stage by establishing focus and agreements, 2) Gather data about objective and subjective experiences, 3) Generate insights by understanding patterns and systemic influences, 4) Decide on one or two actions or experiments, 5) Close by reiterating actions and providing appreciation. Various techniques are suggested for each step, such as timeline, voting methods, and questioning approaches. Following the framework and using different techniques can help teams continuously improve their way of working through retrospective meetings.

How to make your retrospectives the heart of your agile proces

Yves Hanoulle

Retrospective Retreat - Scrum Master Week - Day 3

Ilan Kirschenbaum

Facilitating online agile retrospectives

Enrico Teotti

The document provides guidance on facilitating online agile retrospectives. It discusses the roles of the facilitator as architect, pilot and guide. It emphasizes that online facilitation is not the same as in-person and suggests considering digital constraints and interactive approaches. The document then outlines the typical stages of a retrospective - set the stage, gather data, generate insights, decide what to do, and close out - and provides tips for each stage. It aims to help facilitators effectively lead remote retrospectives.

Scrum Master as a Facilitator

Ilan Kirschenbaum

Project Retrospectives are an important part of any software development process. The Principles Behind the Agile Manifesto state that, "At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly." How can this be done? By taking the time to reflect and learn and proactively determine what should be done differently in the next iteration, release, or project. Linda's presentation will introduce techniques for project retrospectives, whether they are agile or not. The techniques help teams discover what they’re doing well so that successful practices can continue and identify what should be done differently to improve performance. Retrospectives are not finger pointing or blaming sessions, but rather a highly effective process in which teams reflect on the past to become more productive in the future. Linda will share her experiences with leading retrospectives of several kinds for dozens of projects—successful and unsuccessful, small and large, in academia and industry. Her lessons learned can be applied to any project to enable teams and organizations to become learning organizations.

Agile Retrospectives

Yves Hanoulle

The document provides guidance on how to conduct effective retrospectives for agile teams. It discusses principles behind agile processes and retrospectives from the Agile Manifesto. It emphasizes that retrospectives should be a check-in rather than post-mortem, focus on learning and improvement rather than blame. Various techniques are presented for designing effective retrospectives, including setting goals, using timeboxes, gathering feedback, identifying themes for improvement, and planning actions to implement lessons learned. Common "smells" or issues that can undermine retrospectives are also identified.

Continous feedback workshop

Jorge Baldeón

Agile retrospectives

Toni Tassani

1. The document outlines the structure and components of an effective retrospective meeting, including setting the stage, gathering data, generating insights, deciding what to do, and closing the retrospective. 2. It recommends allocating time equally among the components, with around 30-50% of time spent gathering data, 20-30% generating insights, and 15-20% deciding what to do. 3. Various activities are suggested for each component, such as check-ins for setting the stage, timelines for gathering data, and SMART goals for deciding actions.

Running an idea generation workshop

CharityComms

This document provides guidance on running an effective idea generation session, including recommended structures, techniques, and considerations. It recommends beginning with scene setting to understand the audience, problem, or product. Quantity techniques like quick-fire post-its and pairs exercises aim to generate many initial ideas. Quality techniques like building on ideas and De Bono's 6 Hats help refine and develop ideas. The document includes an example agenda and emphasizes preparation, facilitation, and getting feedback to conclude the session.

The Art of the Retrospective: How to run an awesome retrospective meeting

Chris Smith

The drive to inspect and adapt is one of the most important aspects of agile software development. A great way to bake this approach into your process is by having regular retrospective meetings that engage and challenge the team to solve their own problems and make things better. However, these meetings can be difficult to run well and drive improvement. In fact, many teams sleepwalk through sessions, treating them as a box-ticking exercise that signals the end of the iteration. Maybe its time we tried a bit harder to make retrospective meetings work? In this talk, Chris explains how to put together an awesome sprint retrospective. He discusses the following: * Why retrospectives can be unpopular * Structuring the meeting to succeed * Setting the right tone * Activities to gather data * Activities to generate insights * How to decide what to do * How to manage retrospective actions

Rohit Arora - Retrospective, Making Them From Good To Great

Agile Impact

Rohit Arora - Retrospective, Making Them From Good To Great

Agile Impact Conference

The document discusses how to conduct effective agile retrospectives for teams. It provides guidance on setting the stage, gathering data, generating insights, deciding on actions, and closing the retrospective. Key aspects covered include establishing norms, choosing appropriate activities, facilitating discussions, and following up on identified actions. The goal is for retrospectives to help teams continuously improve through reflective learning.

Reviving Retrospectives

Hina Popal

Ale2015 Agile Facilitation

Svetlana Mukhina ICP, -ATF, -BVA, - ACC, PSM I, CSPO

This document provides information about agile facilitation techniques. It begins with an introduction of the author and their background. The session plan outlines learning objectives about facilitation, facilitators, and designing meetings. Techniques described for designing meetings include warmups, brainwriting, world cafe, five to fist voting, pro-con analysis, and meeting minutes. Group dynamics models of forming, storming, norming, performing, and adjourning are also discussed. Recommended materials and certification in agile team facilitation are presented at the end.

What's wrong with sprint retrospectives and how to fix them

Chris Smith

The document discusses common problems with sprint retrospectives and how to fix them. It begins by outlining issues like retrospectives being perfunctory, unpopular activities that teams want to avoid. To address this, the document recommends preparing well for retrospectives, deliberately facilitating engaging activities, keeping to a retrospective framework, varying the types of activities used, and creating specific actions teams commit to implementing. Example activities are provided for each part of running an effective retrospective.

Retrospectives - Agile Ottawa Meetup

Dag Rowe

Retrospectives Workshop Are you struggling with retrospectives? Do you find it hard to get value out of them? Are you looking for tricks to make them amazing all the time? Come join us for a Retrospective workshop! The twelfth principle of the Agile manifesto says: At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. We cannot understate the importance of this practice; if you only use one Agile practice, use Retrospectives. Retrospectives enable your team to inspect and adapt by looking at your results, and altering your plans to match reality. If you do not allow time for improvements, your team will always be in 'firefighting' mode. In this meetup, Dag will elaborate on a few facilitation concepts, and invite the group to participate in a workshop. The workshop will teach you additional tips and tricks to make your retrospectives GREAT! Agile 101 - Transitioning to Agile Simon will facilitate a discussion how to run a successful transition to Agile from total chaos, or total waterfall.

Adapt or Die_devopsdaystaipei_2017

Juggernaut Liu

This document discusses retrospectives in agile software development. It defines a retrospective as a meeting held at the end of a sprint by a development team to inspect what went well and what could be improved in the previous sprint. The document provides tips for facilitating a good retrospective, including defining the scope, driving engagement, using timeboxing and visualization techniques, and encouraging transparency and continuous improvement. The overall goal of a retrospective is for teams to learn and improve their processes incrementally.

Mission possible - the social warfare

SQALab

2020 05 agile ottawa meetup slides

Sue Johnston, MBA + a bunch of other stuff

Sue Johnston and Ellen Grove presented on facilitating effective virtual meetings. They discussed the importance of planning meetings by defining the purpose, identifying necessary participants, and preparing activities and questions. During meetings, they recommended gathering information through breakout groups, generating insights through individual reflection, and deciding through techniques that allow all voices to be heard. They emphasized giving people time to think and engaging listeners through conscious communication. The presentation provided references on meeting planning, remote collaboration skills, and the presenters' websites for further resources.

Institute of Design: Teaming Workshop By Chris Bernard

Chris Bernard

Facilitation Fundamentals

Svetlana Mukhina ICP, -ATF, -BVA, - ACC, PSM I, CSPO

Facilitation Fundamentals

LuxoftAgilePractice

This document discusses facilitation techniques that can be used in Agile meetings and sessions. It begins with introductions and then outlines the session plan and learning objectives. The document then proceeds to define and describe various facilitation techniques including warmup exercises, brainwriting, world cafe, five-to-fist voting, pro-con analysis, and meeting minutes. It concludes with recommendations for further training materials and available Agile Practice services.

"The Dog Ate my Data"

Retro is back - How to Run Retrospective Meetings That Work, Anat (Alon) Salhov @Producttank TLV, Feb' 2020

Recommended

Recommended

More Related Content

Similar to Retro is back - How to Run Retrospective Meetings That Work, Anat (Alon) Salhov @Producttank TLV, Feb' 2020

Similar to Retro is back - How to Run Retrospective Meetings That Work, Anat (Alon) Salhov @Producttank TLV, Feb' 2020 (20)

More from ProductTank TLV

More from ProductTank TLV (20)

Recently uploaded

Recently uploaded (14)

Retro is back - How to Run Retrospective Meetings That Work, Anat (Alon) Salhov @Producttank TLV, Feb' 2020