Agile Retrospectives Blog

Agile Retrospective Return of Time Invested Exercise

Written by Luis Gonçalves | Apr 9, 2023 7:38:22 AM

AGILE RETROSPECTIVE RETURN OF TIME INVESTED

For many years I have been doing Agile Retrospectives and I have found some difficulties in getting real feedback in my sessions. After using this exercise things changed! I will present you the Agile Retrospective Return of Time Invested.

This exercise is a variation of typical Return of Time Invested (ROI) exercise that you can find in Agile Retrospectives book from Diana and Esther.

[shortcake_call2action title="AGILE RETROSPECTIVE ONLINE COURSE" description="We have developed an online Agile Retrospectives Certification to help you to take your Agile Retrospectives to the next level." button_text="TAKE THE COURSE" button_link="https://www.scrummastergrowth.com/agile-retrospectives-certification-program-closed"/]

If you are interested in getting some extra Agile Retrospectives exercises, I created a blog post with dozens of Agile Retrospectives Ideas, check them and see if you find something interesting.

 

 

What you can expect to get out of this technique
What you can get out of this exercise is very simple. This exercise allows you to get qualitative and quantitative feedback in your sessions. There are several exercises out there that are used to rate the quality of products or services.

Usually these methods are quantitative, meaning that you have a scale and you choose a number within the scale. The problem with these methods relies on the fact that users cannot really give qualitative feedback.

If you use these kind of systems you might get a 5 star service, but what was so good about the service? What did you really like? On the other end, if you get 1 star what was so bad about the service? With quantitative systems you get very little information about the product or the service.

With the exercise that I am presenting here, you will not have this problem. This exercise will provide you quantitative and qualitative information that will allow you to create great Agile Retrospectives in the future with the feedback you will collect from the participants.

When you would use this technique
I use this exercise every time I want to collect feedback from a session that I ran. Of course, in this program we are talking about Agile Retrospectives so you can use this exercise when you want to close your Agile Retrospective and you are interested in getting feedback from your participants.

One of the biggest advantages of this exercise is that people do not need to speak, this is especially good with teams of introverted people. Many times people tell me that is very hard for them as facilitators to get people to give feedback or even speak. But one thing that I found out: when you ask them to write their opinions, they are very imaginative.

But one thing that I found out: when you ask them to write their opinions, they are very imaginative.

So if you think about this, this exercise is great to use with any team, but I believe its exercise is especially good if you have an introverted team. They will feel comfortable with writing their true feedback giving you the opportunity to improve for the next session.

How to do it
To do this exercise the only thing you need is a Flipchart, post-its for each team member and markers.
Draw on a graphic with two axis on the Flipchart.

• Axis X: Value
• Axis Y: Fun

Split the graphic in 4 different parts:
• Boring/No Value
• Boring/Great Value
• A Lot of Fun/No Value
• A Lot of Fun/Great Value

After having the graphic on the Flipchart simply ask your team members to think where they would like to put their vote. Give them some minutes to think about it. When they are done, ask them to write the reason on a post-it why the chose that quadrant.

This part is very important because it is what will give you the “feedback” that you can use for your next session.

It does not really matter if they spent a great time and they got great value. If you do not know what made the session a great success, this is why you ask people to write the reasons on a Flipchart.