The third element of the Reviewer is ojo™ Insights. ojo™ presents the metrics most changed for the Sprint or increment so the team can discuss any reasons why they performed as they did. It's another lens on how the team can inspect and adapt to improve.
​
As you prepare to close your sprint and review how your team performed, the ojo™ Insights page within the Reviewer helps you bring the facts into your retrospective conversation around what you did well and should keep doing, and which metrics declined and therefore may need to take a closer look.
​

The metrics presented on this page are the ones that carry the highest weighted rankings in changed scores at the end of your sprint or Kanban increment. To generate the ranking, Umano observes the current score for each metric relative to the deviation of your team’s usual performance and trend for that metric.

Observations are denoted by the ‘eye’ icon. Suggested actions and investigation is denoted by the ‘magnifying glass’ icon.

If the insight is for a sub-metric, then the sub-metric name is displayed in a grey shadow box, as illustrated in the example below.

In the metrics presented under ‘See More,’ you see all metrics that significantly deviated from usual, where significantly deviated from usual performance is determined by the difference between the current score and the usual score being larger than the standard deviation, and having drivers that are significantly deviated from their usual.

If a metric is significantly deviated but doesn’t have any impacting driver changes, they are not displayed.

ojo™ Insights page is updated daily, and then once the team closes the sprint in their Issue Tracker, or once the Kanban increment is complete (for example 5:00pm on Friday if you have set your increment reporting to weekly from Monday to Friday).
​
To allow time for the page to be updated once the sprint has been closed, the Umano teams have a practice of completing their Team Vibe and Team Input sections of their Retro. The final stage is to review what ojo™ presents on their metric related performance, and then to go back to Team Input and add any actions or experiments we intend to run during the next iteration.
​
​
​

​