Ir al contenido

ROTI

De Scrum Manager BoK
Esta página es una versión traducida de la página ROTI. La traducción está completa al 100 %.
⏱ 2 min  ·  📅 2026
ROTI (Return on Time Invested) is a closing activity of about 10 minutes used at the end of a retrospective or other type of meeting. Its purpose is to measure whether the time invested in the session was well spent and to gather suggestions for improving future sessions.

The discussion covers the different benefits that can be gained from a meeting: decision-making, information sharing, and problem-solving. Each participant assesses whether they have obtained those benefits in proportion to the time they have invested.

How to facilitate ROTI

Before starting, the group can briefly discuss what the typical and desirable benefits of a meeting are. For example: making decisions as a team, sharing useful information, and solving problems.

The ROTI scale

To carry out the activity, a numerical scale from 1 to 5 is proposed:

Score
Meaning
5
...
4
...
3
...
2
...
1
...

Procedure

  1. The facilitator briefly explains the scale.
  2. Each participant shows their score simultaneously (with fingers, cards, or in a digital tool). Simultaneity is important to avoid being influenced by others' votes.
  3. The distribution of scores is tallied.
  4. Anyone who gave a score of 1 or 2 briefly explains why and suggests how the session could have been improved. This is not personal criticism of the facilitator: it is improvement information.
  5. The facilitator takes note of the suggestions to apply them in the next retrospective.

When to use it

  • As the regular closing of every retrospective.
  • At the end of any long meeting or one that required significant preparation.
  • Especially useful when the team is learning to run retrospectives: it allows a quick calibration of whether the session design worked.

Common mistake

Ignoring low scores. If the facilitator collects the scores and moves on to the next item without opening a conversation about the 1s and 2s, the activity fails to serve its purpose. ROTI is only useful if the improvement information is listened to and acted upon. Asking for feedback that nobody is going to use breeds more distrust than not asking for it at all.

Resources

🔧 Diseñar una retrospectiva [Designing a retrospective] (in Spanish)Template · Scrum Manager

📄 Ejemplo: cómo diseñar una sprint retrospective [Example: how to design a Sprint Retrospective] (in Spanish)Scrum Manager Blog · Oct 2022

📄 Liderar retrospectivas y resolución de conflictos [Leading retrospectives and conflict resolution] (in Spanish)Scrum Manager Blog · Dec 2022

📄 Apuntes: Agile Retrospectives [Notes: Agile Retrospectives] (in Spanish)Scrum Manager Blog · Sep 2022

References

  • Derby, Esther; Larsen, Diana. (2006). Agile Retrospectives: Making Good Teams Great. Pragmatic Bookshelf.

See also

Want to advance in agility? You can search for course and exam calls, or go at your own pace by becoming a member of the Agile Club. This membership includes exclusive resources, e-learning classrooms, and access to Skill Arena: a space to practice and measure your agile skills at your own pace.