Code Avengers Drawing Circles Solution

‍

In Affiliate 1, yous learned the basics of an agile retrospective. What is a retrospective? What's the value of a retrospective? Who should nourish the retrospective? And more. Nosotros as well briefly touched on the 5 stage model introduced past Diana Larsen and Esther Derby in their book Active Retrospectives: Making Good Teams Great.

Now, we're going to dive into more particular on this approach.

How Not To Run
A Retrospective

‍

It was time for the squad'southward retrospective. Everyone sat down and yous could hear, run into, and almost feel the groans in the room. "Not once again. These retrospectives don't really accomplish anything and I take and so much to exercise."

‍

Bob, the squad'south Scrum Master, kicked off the retro. "Welcome anybody! But like terminal time, let's go around the table and everyone tin can talk near what's working and what'southward not, and and then offer some solutions."

‍

Cindy took out her phone. Joan opened her email on her laptop. Rahul only looked bored.

‍

Maya was the starting time to speak upward. She had been on the team the longest and knew the code inside and out. She always seemed to speak first. "The biggest problem to me is the depression quality of the codebase. Then many of you just commit code without thinking most how to make it improve. If you all would just exist more intentional about the code y'all write, nosotros'd exist better off."

‍

"That'due south not the reason why there are so many bugs, Maya!" John responded. "You've been hither the longest, and if yous had only spent the time documenting the code at the start, the residual of the developers would have a better idea of what's in your head!"

‍

"Non again," thought Erica. "Those two e'er argue. And the crazy matter is that the number of bugs in the code has been decreasing for months!"

‍

And, end. This retrospective is leading nowhere practiced, and it merely just began! Why? What specifically went wrong in just the start few minutes?

‍

Problem One: Lack of appointment

‍
Cindy, Joan, and Rahul aren't paying attending. As John and Maya go into their argument, Erica checks out. Yous can only imagine how the residual of the team is feeling.

‍

Problem Ii: Lack of alignment

‍
While John and Maya argue about why the codebase lacks quality, Erica silently doesn't fifty-fifty agree with the premise. The squad doesn't agree on the issues at hand.

‍

Problem Three: Jumping to solutions

‍
Both Maya and John spring to solutions far too fast without investigating alternatives, diving into root causes, or looking at the bigger picture.

‍

To gear up these issues, the team should have followed the five phased approach to effective agile retrospectives. Let's accept a look.

Phase 1: Set The Stage

‍

The first phase of a retrospective is a chance for the squad to "check in". Many teams skip this phase, and that's a large mistake! When I first learned about this phase, I admit I was skeptical. My bias, like many people with an applied science background, is to jump right into analyzing issues and finding solutions. I've since changed my outlook.

Why You Shouldn't Skip Setting The Phase

‍

i. It gives everyone a chance to context switch
Retrospectives crave an entirely different mindset from the day-to-day grind of working on a production or project. By taking a few minutes to set the stage before getting into the eye of the retrospective, the team has the chance to switch from thinking most the last thing they were working on to thinking near the bigger picture.

‍ two. It encourages participation
According to Marc Loeffler in his volume Improving Agile Retrospectives, "someone who is silent at this stage is likely to remain so for the residual of the retrospective." 😶 If you lot desire more people to participate in the remainder of the retrospective, now'southward your chance! Make certain everyone says at least one word during this phase.

3. It grabs everyone's attention
Many people are in meeting afterward coming together, solar day in and day out, and see the retrospective as yet another meeting to nourish. If you use Setting The Stage every bit an opportunity to have some fun, yous'll too grab their attention for the rest of the conversation. (If you don't believe me, think about the final conference you were at. If the speaker hooked y'all in the first few minutes, were yous more or less probable to listen to the remainder of his or her talk?)

So how does it work in practice? While in that location are lots of activities you can choose from, hither are a few of my favorites:

Action: One Discussion Check In

‍

Ask all participants to respond a question using but a single discussion (feel free to change this to a single judgement, if you prefer). Example questions include:

‍

In one word, how are you feeling right now?
If yous could go anywhere in the earth, where would yous go?
What was the terminal thing you ate?
If you lot could depict the previous iteration in a single word, what would it be?

‍

And so on. Use your imagination! Likewise realize that it'southward okay for someone to pass. If they don't feel comfortable answering the question, don't make them. Only saying "I pass" can be enough to become them involved.

‍

Now, if you're like me, you might incertitude the value of this exercise. Trust me, I've been in that location! Merely hither's an example from a existent life retrospective that changed my heed. One person on that squad was named Jeff (non his real name). Jeff was usually a positive person who brought free energy to whatever situation. But over the past twenty-four hour period or two, the team had been noticing that Jeff was acting a fleck down in the dumps. It was unlike him. During Ready The Stage at that retrospective, the facilitator asked the group a one discussion check in question: "How are you feeling right now?" Everyone went around the table round-robin style. When it was Jeff's plough, he said: "Terrible. I've been meaning to tell everyone, but I learned a few days agone that my mom has Stage 4 Cancer. Sorry I've been and then downward in the dumps."

‍

Now, if the squad had jumped correct into the residuum of the retrospective, they might have been annoyed at Jeff's negative attitude. Only considering of the one word check in activity, the team's understood why Jeff was acting that fashion. They were able to provide emotional support and the team felt closer to one another. That's the impact of Setting The Stage.

Action: Constellations
‍

‍

Some people shy away from verbally checking in to the retrospective. For these people, Constellations is a fantastic do considering it allows you to answer simple questions without speaking. 😲 How is that possible? 🤔 Here's how it works:
‍

Beginning, clear the space. Move tables and chairs out of the style. Then ask everyone to come up to the center of the room.
‍

Explain to the group that y'all are going to make a statement and that yous'd similar everyone to motility themselves closer or further away from you to point the level of understanding or disagreement with the statement.
‍

For example, you might say: "I am happy with the results of the iteration." Then sentry people move close to you to indicate they agree or farther away from you to point they disagree.
‍

Non all statements take to exist related to piece of work. In fact, I encourage y'all to make this fun! For example, you might say: "Star Wars is better than Star Trek" or "Android is amend than iOS" Non only will statements similar these exist fun and engaging, you might learn a matter or two nearly your teammates!
‍

Encourage other people on the squad to make statements, likewise. You lot'll know when the activity is done when the energy starts to driblet in the room.

Activity: Review Your Action Plan

‍

Many teams struggle with follow-through on their Activeness Items. For those teams, it can exist useful to kickoff each retrospective with a review of the squad's Action Items from the previous retrospective. I learned this technique from Sven Winkler.

‍

Create 5 columns on a affiche board: Action Particular, More Of, Less Of, Keep Doing, and Stop Doing. Then write downwards each outstanding Action Detail on a viscous notation and put it in the Action Item Column. Have each person put a dot, an "X", or a gluey note in the column that best represents how they experience about information technology. Here is an example:

‍

‍

Phase two: Gather Information

‍

The second phase of the retrospective gives your team the hazard to wait back at your iteration to create a shared agreement of the events that shaped the nowadays. The Gather Data stage is actually the only phase that fits the classical definition of the word retrospective (which literally means "looking back on or dealing with past events or situations")!

The Advantages of Gathering Data

‍

Information technology gets people on the same page
Yous'd exist surprised how many times people take dissimilar memories of a shared issue. And when you have a team of 5-10 people, odds are very high that different people will recall dissimilar things from the previous iteration. Gathering Data gives your squad a chance to get on the aforementioned page most just what happened in an attempt to create a shared reality.
‍
‍It expands anybody'southward viewpoint
While the team went through the iteration together, it's likely that different people experienced different things at different times. An engineer might take struggled with the Continuous Integration server without others realizing. The designer might have been sick for a day or two and missed out on an important coming together. And so on.
‍
It tin can create alignment about what's most important
Have yous always heard the phrase "In God we trust; all others must bring data"? That statement applies to retrospectives, as well. Bringing data can help overcome disagreements about the virtually important bug that the squad might face up. For case, someone might mention that the squad faces also many simultaneous tasks. Without data, how would you know if this was truthful or not? You wouldn't; it would be just an opinion.
‍

Types of Information To Bring

Objective ("Hard") Information

‍

Objective Data is sometimes referred to equally "difficult data". Objective Information is any information that can exist measured and verified. There are a lot of different types of Objective Data. Here are only some:

Types of Objective Information:

‍

Sprint Goal
Burndown Nautical chart
Velocity
Number of meetings
Number of stories completed
Number of stories completed as a per centum of number of stories started

Number of new support requests
Throughput (# of piece of work items finished per day)
Average bicycle time
WIP (# of work items started but non finished)
Number of new defects introduced

‍

Annotation that you don't accept to bring all of this data to every retrospective (though you certainly tin). Instead, bring the data that yous call up would exist most interesting given the context of what's going on.

‍

Subjective ("Soft") Data

‍

In contrast to Objective Data, Subjective Data is sometimes referred to as "soft data". And Subjective Information is just every bit important as Objective Data! Subjective Data includes personal opinions, feelings, and emotions on the team. Whereas Objective Information presents the facts, Subjective Data tin reveal what your squad thinks is important near the facts.
‍

Here are some questions you lot can inquire to gather Subjective Data:

‍

When did y'all feel motivated during the dart? Unmotivated?
What was the best moment during the iteration? The worst?
How happy were you with the new practice of <x> (possibly you introduced a new git commit strategy or started pair programming)

Alternatively, yous can plough Subjective Data into measurable information. For case, you could setup a Squad Radar to ask your team how it is doing living upwardly to the Scrum Values from i to five (1 beingness "poor" and 5 existence "excellent"). By aggregating the results across the team, you have turned subjective feelings into measurable information.

‍

On Retrium, Squad Radar looks like this:

‍

‍

Gathering Data Anti-Patterns

‍

Gathering Data is critical. Simply information technology's as well critical to practice it right. There are a number of pitfalls to scout out for.

‍

1. Practice not bring information that focuses on individual team members (at the detriment of others)
For instance, you might collect information around the introduction of bugs into the repository. Who committed which bugs and who stock-still them? While this data might be useful in other contexts, the retrospective should non exist used to compare and contrast individual performance. What to exercise instead: bring data around the total number of bugs introduced to the repo and the total number of fixes issued beyond the entire team.
‍

two. Do non falsely present Subjective Data equally Objective Data
For example, you might suspect that some team members are working on side projects during the dart (at the asking of management) without alerting the residue of the team. You believe this might be reducing downwardly the team's throughput. Y'all haven't nerveless Objective Data to know for a fact that this is happening, it'south merely a suspicion. Don't tell the team that this is a fact! What to do instead: bring this consequence up while your squad gathers Subjective Information, and then that your teammates know its an unproven opinion at this point.
‍

3. Exercise not collect more than data than you demand
Collecting and tracking data takes time and effort, so information technology's important to track merely the data you need and nil more. I bet you lot can think of a time when data was tracked without a clear purpose ("that'southward just how nosotros've done it in the past"). If there'due south no reason to collect information, and then don't.
‍

4. Do not share data outside The Team without permission
Data can easily exist driveling and misused. Information that you lot collect for the retrospective should exist for The Team only. If people on your squad suspect that the data you are collecting is not only for The Team, but likewise for management, stakeholders, or anyone else not on The Squad, they volition no longer experience condom.
‍

‍

What are some activities you tin use to Gather Data? Here area but a few:

‍

Activity: Timeline

‍

I sometimes detect it difficult to remember what I had for dinner final dark, permit solitary what happened over the class of the previous two weeks! That'southward why the Timeline activity can be so helpful: it jogs people'south memories about what happened. Timeline can be peculiarly helpful for teams with longer Sprint Lengths (if you lot take a 4 week dart, I'm looking at you lot!), or for a Project or Release retrospective.

‍

In this activeness, your squad will be edifice out a timeline of all the events that occurred during the iteration. Set up upward a whiteboard in which the x-centrality represents time. No need to be precise here ("on Day ii what happened? On Mean solar day 3 what happened? etc"). Instead, what matters is overall trends ("towards the beginning of the sprint, this happened. In the middle of the dart, this happened. etc").

‍

Have your time. Have people write downwardly whatever events occurred that were meaningful to them, or had an impact on the team. These can be technical events like "we merged in code from another branch", personal events similar "I was sick and took a day off", or events exterior the team's control like "we learned there will exist layoffs in the coming weeks".

‍

The important matter is to brand sure there is a shared understanding of what occurred.

Action: Mad Lamentable Glad

‍

‍

This popular retrospective technique helps highlight your team's emotions during the iteration (bringing to calorie-free Subjective Data exclusively). To run Mad Sad Glad, merely setup 3 poster boards around the room titled Mad, Sad, and Glad. Ask everyone to privately write on glutinous notes what they felt Mad about, what they felt Pitiful about, and what they felt Glad about. Once anybody is done brainstorming, have everyone place their sticky notes up on the board.

‍

And so, ask your team questions similar:

‍

What patterns do you see? Are most of the notes in ane cavalcade or another?
What surprises you most the results?
Did multiple people add together sticky notes about the aforementioned event? What does that mean?
Are there any events that led to a disparity in emotions? (Someone felt Glad about the aforementioned issue someone else felt Mad about, for case.)

Activity: Lean Java™
‍

‍

Lean Coffee™ is a style of constructing an agenda for the retrospective based on what the squad collectively wants to discuss the most. Here is out information technology works:

Take anybody write down topics they want to discuss, one topic per gluey note
Have everyone put upward all sticky notes onto a flipchart or whiteboard
Group together sticky notes that are similar enough that they should be discussed together
Have everyone dot vote on the topics they want to discuss the most
Prioritize the discussion based on the sticky notes that received the near votes
‍

Using Lean Coffee™, you can quickly identify topics the team wants to discuss that they actually care about.

‍

Phase 3: Generate Insights

‍

Ok, so you've Set The Stage to get everyone "checked in" and y'all've Gathered Information to build a shared understanding of the facts. Now it'southward time to clarify the data yous've collected to find insights and to find root causes.

‍

Generating Insights encourages you to call back securely about issues, which helps to expand your horizons by helping yous meet the big motion-picture show.

Why Y'all Shouldn't Skip Generating Insights

‍

And so many teams autumn into the trap of Solution Finding before they know what trouble they are trying to solve. These teams identify something interesting in the data and jump to conclusions about what to do to prepare the problem.

‍

Hither'south an example. The team might have Gathered Data and discovered that they did not work on any Retrospective Action Items during the sprint. They immediately jump into trying to find solutions to that trouble. Within a few minutes, they've identified a number of possible fixes:

‍

Write the Activity Items as hypotheses and experiments
Add the Action Items into the adjacent Sprint Backlog
Talk about the Action Items during the Daily Standup
Hang the Action Items on a Affiche Board in a highly visible place

‍

I could go on and on. Just which one of these solutions is the right ane? How do you know? Without Generating Insights, it'due south just a guess. It's my opinion versus yours. Information technology'south who talks first or who is the nearly convincing.

‍

Generating Insights provides your team with the opportunity to analyze the issue and to make sure whatever you Decide To Practice will have a high likelihood of success.

‍

Going back to our example, if the team used the 5 Whys technique to clarify why they were not working on their Retrospective Action Items, they might accept discovered that the real root cause of the issue was not that people forgot about the Activeness Items but that no 1 felt responsible for them. Look again at the list of potential solutions in a higher place. Practice any of these accost the actual issue? Not really.

‍

Instead, The Team might simply record downward who is responsible for the Activity Items during the retrospective. Without taking the time to Generate Insights, you might never take arrived at that conclusion.

Action: 5 Whys

‍

1 of the easiest ways to understand the ability of Generating Insights is by using the 5 Whys activeness. 5 Whys is a facilitation technique that helps y'all find the root causes of an issue. It is no more complicated than its name suggests. Here are the two like shooting fish in a barrel steps to running 5 Whys:

Place the issue at mitt
Inquire "why?" five times to get to the root cause of the consequence

‍

That's it. Actually. Of form there is no magic to asking "why" five times in particular. You might ask "why" three times or eight. Feel costless to stop one time you arrive at the root cause.

‍

To take five Whys to the next level, consider breaking your grouping into smaller subgroups of 2-4 people. Accept each subgroup perform the 5 Whys exercise independently, and then enquire each to report their findings back to the larger grouping. Breaking into pocket-size subgroups tin assist encourage more people to participate in the discovery process.

‍

Here'south an instance of five Whys in activeness, using baseball game as an analogy. Don't worry, if yous're not a baseball fan. It will still make sense. (Likewise this is not a real example: I'm not an expert on the Baltimore Orioles and the analysis hither is fabricated-upwardly.)

‍

Issue: The Baltimore Orioles missed the playoffs

Why did the Orioles miss the playoffs?
Because they lost too many games
Why did they lose too many games?
Because their starting pitchers gave up also many runs
Why did their starting pitchers give up too many runs?
Because their ii best pitchers got injured early in the season
Why did their two best pitchers become injured early in the season?
Because the team didn't emphasize strength and conditioning in the off flavour
Why didn't the team emphasize strength and workout in the off season?
Considering they didn't hire a strength and conditioning motorcoach until just before the season started

‍

Using 5 Whys, nosotros accept connected the dots betwixt The Baltimore Orioles missing the playoffs and the need for the team to hire a strength and conditioning autobus. Imagine if you hadn't run 5 Whys. Would y'all accept ever arrived at that conclusion?

Activeness: Force Field Analysis

‍

Forcefulness Field Analysis is a neat way of identifying the factors that ane) back up the topic (or drive the alter frontwards), and ii) oppose the topic (or prohibit the change from happening). The team can and then movement on to identify what actions it can have to reinforce the driving factors and to lessen the affect of the prohibiting factors.

‍

Derby, E., & Larsen, D. (2012). *Agile Retrospectives: Making Good Teams Great*. Dallas, TX: Businesslike Bookshelf.

‍

Here's how information technology works.

Pick a topic, effect, or proposed alter that y'all desire to analyze.
Depict two columns on a whiteboard: Supporting Factors and Restraining Factors
Break your group into smaller subgroups of 2-4 people.
Have each subgroup brainstorm all of the factors that back up the topic or drive the alter forrad, then inquire them to selection ane from the listing to put under the Supporting Factors column on the whiteboard
Repeat pace four for the the factors that oppose the topic or prohibit the modify from occurring, and have the group put these items under the Restraining Factors column on the whiteboard
Ask each person to vote on the item that is the strongest factor in each column
Analyze the Supporting Factors to determine which ones the group can strengthen
Analyze the Restraining Factors to make up one's mind which ones the grouping tin lessen

Never run a retrospective before?

Try Retrium. It guides you through the retrospective procedure

Starting time today for costless!

Phase iv: Make up one's mind What To Practise

‍

Now that you've analyzed the issue at paw, it's (finally) fourth dimension to brand information technology actionable. Your team will love this stage — fixing bug is what Solution Focused engineers want to do most. Engagement shouldn't be a problem. The focus here is making sure yous pick the best action for the upcoming iteration.

Why You lot Shouldn't Skip Deciding What To Do

‍

As you lot learned in Affiliate i, the purpose of the retrospective is to enable Actionable Team Learning. That ways that the insights yous discovered during the last stage of the retrospective must now be translated into Action Items or experiments then that the squad has the opportunity to change.

‍

Nearly teams naturally empathize the need to Determine What To Do, fifty-fifty if they've never heard of the 5 phase approach to retrospectives. They simply want to come up up with ideas for improvement. But a minority of teams simply run into the retrospective as an "opportunity to complain". These teams fail to come up with concrete actions and therefore find that retrospectives rarely (if ever) get agents of change. Many of these teams telephone call retrospectives "checklist items". They exercise them because "Scrum said to". They find fiddling to no value in the retrospective and volition eventually stop doing them altogether.

‍

Don't fall into that trap. Use this stage of the retrospective to pick the right affair to work on so that your team can see the benefits of the retrospective.

‍

Activity: Start Stop Continue

‍

vote — Beginning Stop Continue in Retrium

‍

This is a popular retrospective technique that is oft misused. Many teams kickoff their retrospective with Start Stop Proceed. That's jumping into Solution Finding way too fast. Employ this technique to help brainstorm a list of potential actions the team can take afterward it has identified an issue it wants to work on during Generating Insights.

‍

For example, yous might have used Forcefulness Field Assay to discover the strongest supporting and inhibiting factors for a change item. Use Start Stop Continue to suggest actions the team tin can have to increase the strength of the supporting factor and decrease the strength of the inhibiting gene.

‍

Afterward your team has generated the list of deportment, use Dot Voting to prioritize which actions the team most wants to work on.

Action: Bear upon, Effort, and Energy

‍

When you've generated a listing of potential actions, it tin can be difficult to know which one to work on next. Dot Voting tin help. A more powerful way is to use Impact, Endeavor, and Energy mapping.

‍

Hither's how information technology works:

Put up a affiche board with 4 columns: Thought, Effort, Touch on, Energy
Listing out all ideas for activeness in the Idea column
Ask the squad to estimate* the effort of each potential action, and put the results in the Attempt column for accomplish item
Enquire the squad to guess* the affect of each potential activeness, and put the results in the Touch column for reach item
Ask each person on the team to vote on the item or items that they personally feel most energized by, and put those votes in the Free energy column

‍

Now that you have mapped out the Bear upon, Effort, and Energy of each potential action, the team tin discuss which activeness makes the most sense. For case, an activity that has low effort, loftier impact, and high energy, would be a great candidate to commit to. An action that has loftier attempt, low impact, and low energy, is likely one you should skip.

‍

In the image in a higher place, the kickoff potential activeness would be a expert candidate (it has high impact and low effort), equally would the third (it has a lot of energy).

‍

* Use relative size measurements for estimation. For example, you can apply t-shirt sizes (small-scale, medium, large, actress big) to compare each idea. What matters is the relative sizes compared confronting each other ("this one is bigger than that one"), not the accurateness of any individual item.

Activity: Hypotheses and Experiments

‍

How you write your Action Items makes a big deviation. One option is to use the SMART template. Merely for teams that take people with strong opinions, that'southward sometimes not enough.
‍

Let's think near this fictional scenario: the team is trying to decide which action to accept in social club to reduce the number of bugs produced in the upcoming iteration. Jennifer argues passionately for trying out pair programming. Randy disagrees and argues vehemently for trying out TDD. They can't come to an agreement, and tensions flare. What should the squad do? How can information technology selection between the options?
‍

That's where hypotheses and experiments come up in. If Jennifer had said, "I hypothesize that by implementing pair programming, the number of bugs in our upcoming iteration will be reduced. I don't know that this will work, it's just a guess, simply let'south try", then Randy'due south reaction might not take been and so strong. He might reply, "I don't call back that will work, only it'southward worth a shot."
‍

Using hypotheses and experiments helps your group move from consensus decision making to consent decision making. When actions are presented as solutions, teams tend to want to build consensus to make sure they all concord that it is the correct solution. When deportment are presented as hypotheses, teams are less inclined to resist trying new things out (even if they don't agree it'southward the optimal experiment to run).
‍

Here's a template from Luís Gonçalves that you can employ to write your Activeness Items as hypotheses:
‍

We hypothesize by <implementing this change>
Nosotros volition <solve this problem>
Which will take <these benefits>
As measured by <this measurement>

People don't speak upwards in your retrospectives?

Apply Retrium to allow people to submit ideas anonymously.

Start today for gratuitous!

Stage five: Close The Retrospective

‍

Congrats on making it to the stop of the retrospective! Many teams make the mistake of catastrophe the meeting before endmost the feedback loop in this phase. Closing The Retrospective takes simply a few minutes and information technology's well worth your time.

Why You lot Shouldn't Skip Closing The Retrospective

‍

When you're in a blitz, it may seem like skipping this last phase of the retrospective is okay. But if y'all do, you lot're missing out on some important benefits.

It gives y'all a gamble to reflect on the retrospective itself. What worked? What didn't work? How can we get in meliorate side by side time? Think about it as a quick retrospective on the retrospective. If the retrospective didn't engage part of the team, what could we change to make it more relevant?
It creates the space for celebration. Who did we appreciate? What did nosotros learn that was particularly impactful?
It gives you the opportunity to document the results of the retrospective. What should we write downwardly or capture? Who should we share it with?

Activity: What Can Exit The Room

‍

Many teams have a retrospective basis rule: What Happens in the Retro Stays in the Retro. By that, they mean that in lodge to increment trust and create a sense of psychological rubber, the team should experience comfortable knowing that nothing that is discussed in the retro leaves the room.
‍

Just sometimes things the team learned in the retrospective should be shared outside the team. What if the finding could help other teams succeed? What if the team needs help on a particular effect from someone else in the organization? That's when Endmost The Retrospective with this activity makes sense.
‍

Here'due south how information technology works:

Remind the squad that "by default, everything that was said in the retrospective today stays private to The Team"
Then ask them: "Is at that place anything nosotros discussed today that we desire to share transparently with others?"

‍

The reply might be "no" and that's okay! But if the answer is "aye," document what The Team has authorized to be discussed outside the room.

‍

Activity: Check Out Question

‍

Just similar with the Ane Word Check In, but ask your team a question and ask them to answer in a single word or brusque phrase. You can do this verbally or have everyone write down their response on a viscous note and hand them to you as they leave.

Here are some example questions:

What is 1 matter we could do improve adjacent retrospective?
Which activity during the retrospective was your favorite? Least favorite? Why?
How has your mood changed since the get-go of the retrospective? Why?

‍

Don't limit yourself to these questions. Be creative. Use it equally an opportunity to collect feedback in an endeavour to ameliorate the retrospective experience adjacent time.

Activity: Retro as a Gif

‍

For teams that love to alive in the digital world, this technique can be a fun Shut The Retrospective activity. Hither'southward how it works:

Inquire your team to take our their laptops / iPhones / device of choice
Tell everyone to get find a gif that all-time represents the retrospective.
Go round-robin asking everyone to briefly explicate why they chose their gif

‍

For case, someone might cull a gif like this one to express that they feel closer to the rest of The Team or that they feel particularly happy nigh solving a problem:
‍

‍

Someone else might choose a gif like this one to point they are excited to get started on an Action Item:
‍

Retrieved from https://giphy.com/gifs/oWXYimsCBxvB6

Running the Retro as a Gif practise is more than simply fun. Information technology also gives you a sense of how the team is feeling after the retrospective is over. You tin utilise this data to improve next fourth dimension.

How To Run A Retrospective. This Time In A Expert Way.

‍

Let'south go back to how we started: with the case team. If you think, Bob (the Scrum Chief) started the retro by going round robin and asking everyone what should be improved. Immediately, a number of team members checked out. And then Maya and John got into a disagreement that Erica thought didn't fifty-fifty matter.
‍

Allow's replay that retrospective using the 5 phase arroyo nosotros but outlined and see the difference it can make.

Gear up The Stage (10 min)

‍

Scrum Chief Bob has prepared the infinite ahead of fourth dimension for the Constellations exercise. He moves all the chairs and tables to the side to create an open space.

‍

As the squad walks in, he asks everyone to join him in the middle of the room and he explains how he will start by making a statement and he'd like everyone to physically move closer or farther away from him to indicate their level of agreement with what he's about to say.

‍

"The best Marvel motion-picture show was the original Iron Man."

‍

Anybody laughs. Most people motion far away from him. Cindy shouts, "No way! The Avengers movies are and so much amend!" Erica laughs, "Yous're crazy. Information technology's all about Thor."

‍

There was a cursory pause before Maya says, "Tin I brand a statement?"

‍

"Of course!" Bob responds.

‍

"The all-time place to take vacation is the embankment," exclaims Maya.

‍

Most of the team excitedly moves very close to Maya. But non Hashemite kingdom of jordan or Mike, who motility equally far away as possible. "The beach is for lazy people. My platonic holiday is in the mountains," says Mike. Hashemite kingdom of jordan nods his head and responds, "I never knew y'all enjoyed hiking. And so fun! We'll have to go sometime."

‍

The team continues with a series of statements until the energy leaves the room and Bob recognizes it's fourth dimension to move on.

‍

What did this accomplish?

Information technology got everyone energized
It got anybody to know each other better
It gave everyone fourth dimension to switch out of the day-to-day grind and into the retrospective mindset

Gather Data (x min)

‍

Anybody waits to hear what's side by side. Bob says, "Next up, we're going to run a Development Practices Radar. We'll use this to collect some subjective information virtually what the team thinks we're doing well and not doing well. Based on what we learn, we will pick a narrow focus for the rest of the retrospective."

‍

Bob continues: "The 6 topics of consideration are: Testing Practices, Shared Coding Standards, Managing Technical Debt, Clarity of Scope, Ability to Focus, and Deployment Process."

‍

"Let's start with Testing Practices. What does that mean to y'all?"

‍

Rahul responds, "To me, Testing Practices means the way nosotros check our code for correctness."

‍

"That sounds correct. But I'd as well add it includes transmission testing," Cindy responds.

‍

"Great," says Bob. "Now that we have a shared definition of Testing Practices, I'd similar each of you to write down on a sticky note a number from ane to 5 indicating how well we are doing in this area. 1 means there's not much we are doing well. 5 means we're doing too equally could exist expected."

‍

Everyone thinks for a moment, then writes down their responses. "Perfect. Who would like to volunteer to collect the responses?"

‍

Rahul volunteers and everyone hands him their sticky notes.

‍

The process continues for each spoke of the Development Practices Radar. At the end, Bob asks each of the volunteers to calculate the average for their set of sticky notes.

‍

"Here are the results," says Bob. Bob draws a Squad Radar on the whiteboard:

‍

‍

"Wow. I wasn't expecting that!" says John. "I was sure the lowest average rating was going to be on Managing Technical Debt, but that'south really one of the highest!"

‍

"With this new data, is everyone okay focusing only on Shared Coding Standards for the rest of the retrospective? Information technology seems in that location's a lot of room for comeback in that area," asks Bob.

‍

The team agrees.

‍

What did this achieve?

It narrowed the focus on the retrospective based on data
Information technology expanded everyone'southward viewpoint
It created a shared mental model as to why we are talking about a particular topic

Generating Insights (20 min)

‍

"Let's spend some time analyzing Shared Coding Standards to see what'southward truly going on," says Bob. "Commencement, commencement thinking virtually what forces are helping you lot maintain good quality Shared Coding Standards. What'due south working in your favor? Whenever you think of something, jot it down on a sticky annotation."

‍

"Information technology's of import," Bob continued, "to non filter anything out right now. Only write downwardly whatever y'all think of. We'll narrow down our choices later."

‍

"I'll set up a timebox of five minutes. Get!"

‍

Everyone starts thinking on their own and the sticky notes beginning piling up.

‍

"Time'due south up!" A few people quickly finish writing down their final idea.

‍

"Side by side, I'd similar you to recollect through all the forces that are preventing you lot maintain good quality Shared Coding Standards. What's working against y'all? I'll fix another timebox of 5 minutes. Go!"

‍

More sticky notes are created and presently, the timebox is up. Everyone looks at Bob.

‍

"Now, please self-organize into subgroups of 3-iv people. Discuss what y'all wrote down and pick one-2 supporting factors and i-2 prohibiting factors that you'd like to bring to the broader group. Whenever you're ready, put those factors up here on the whiteboard. I'll set the timer for 5 minutes. Become!"

‍

‍

Anybody organically splits into smaller subgroups. You tin can hear the energy in the room equally Bob walks effectually making sure everyone knows what to do.

‍

"Time'south upwardly! Finally, let's vote on the issues you think are strongest in each column. Y'all can only vote on 2 problems per column. Get!"

‍

When the votes are tallied, it turns out that the strongest driving strength towards good quality Shared Coding Standards is the fact that past default anybody'due south development environment is setup using a standard configuration. And the strongest restraining forcefulness that is preventing improvement in the team's Shared Coding Standards is the lack of agreement on what those standards should exist in the first place.

‍

John pipes up. "If nosotros took the fourth dimension, I bet we could come up with agreements on our coding standards. What practice the balance of you lot think?"

‍

"Absolutely," Erica responds. "I'm glad this came up. It would be great to be on the same folio about this."

‍

What did this achieve?

‍

It helped the team analyze the event before picking a solution
It created mutual understanding effectually root causes
It increased the odds that the change the squad picks will exist beneficial

Decide What To Practice (15 min)

‍

"Perfect. It sounds like we're fix to move on to coming upwardly with an activity nosotros can commit to as a team," says Bob. "What I'd like for you to do next is to start brainstorming what the team tin can do to come up to agreement on this. I know it tin can be a contentious issue! I'll set a 5 infinitesimal timer. Go!"

‍

As the squad brainstorms actions, Bob draws a single horizontal line on the whiteboard. On the left hand side of the line he writes the word "Low Impact" and on the correct hand side of the line he writes the word "High Bear upon".

‍

When the timer is up, Bob says: "Ok folks. Come up on up to the board and put your ideas somewhere onto this line to indicate how impactful you call back your idea might exist. Don't be agape to motion other ideas around and so that we have a view into how impactful each idea is compared to the others."

‍

‍

Anybody on the team comes up to the board and places their ideas onto the line. Some conversation ensues as viscous notes are moved around, simply inside a infinitesimal or 2, the group is done.

‍

That's when Bob draws some other line onto the whiteboard, this time a vertical line half way down the center. On the height of the line he writes the give-and-take "High Endeavour" and on the lesser he writes the word "Low Endeavor."

‍

"Now, motility the mucilaginous notes up or downward to indicate how much effort they will accept. Get!"

‍

The resulting diagram looked like this:

‍

‍

Almost immediately, John said: "The only idea with high impact and low endeavour is using an automated process like Prettier. Information technology will make all our code follow the same standards automatically!"

‍

"I can't believe this wasn't obvious before," Mary responded.
‍

Anybody agreed — this made a lot of sense. It would remove the arguments. Remove the need for documentation that needed to be kept upwardly to date. And it wasn't even difficult to accomplish.

‍

"Permit's do it!" everyone agreed.
‍

The power of retrospectives, Bob idea to himself.

‍

What did this reach?

It helped the squad pick the change item with the highest impact and lowest amount of try
Information technology congenital momentum for the change to occur
It established a common framework for picking a change detail

Shut The Retrospective (5 min)

‍

"Almost washed, everyone! Come dorsum to the centre of the room. I'd like everyone to stand up in a circle."
‍

The grouping looked at each other, puzzled. John fabricated a snarky comment, "Not another game, Bob. I thought we were washed!"
‍

"Almost," Bob said. "I want these retrospectives to piece of work for you. So before we phone call it a day, I'd like for you to pick up 1 sticky note and write downwardly just i thing I can practice better next time. It'll assist me amend the retrospective feel for you."
‍

Everyone wrote something down.
‍

As the squad started walking towards the door, Mary said, "Bob, I want to thank you. That was so much better than any other retrospective I've ever been a part of. I felt like you really helped usa as a team."

‍

Bob merely smiled.

‍