The old “what worked, what didn’t” or “stop doing/start doing” gets old fast. Return on Time Invested (ROTI) is a great way to mix things up for agile teams and ask them to reflect on:
If a team is going to be truly self-managing, this is a good Retrospective pattern that asks them to come up with iterative improvements to the way they behave and interact as a team.
ROTI uses the following 5-point Likert scale.
I got so much from that event. I wouldn't have missed that for anything!
Definitely valuable. I gained more than the time I spent.
I gained enough to justify the time I spent.
Useful, but it wasn't worth 100% of the time I spent. I feel I've lost time.
I would have rather watched paint dry or grass grow. No value at all.
When an event like Sprint Planning or the Sprint Review concludes, ask participants to do the following:
*Obviously, deciding not to do a Daily Scrum or Sprint Review because it’s boring isn’t an option. That’s not within the team’s control.
Asking the team to come up with options for a small improvement is a good way to bring options to the Retrospective for examination and discussion. Ultimately, ROTI helps to place the ownership on making things more effective back on the team members themselves.
I’ve often plotted out the Sprint’s timeline and used ROTI to guage the team’s emotional wellbeing across the Sprint.
We then look for patterns:
Then, we deep-dive into a root cause analysis of the factors that were attributed to the highs and lows and see if we:
Using the 1-2-4-all pattern from Liberating Structures is a great way to brainstorm the causes and come up with solutions the whole team owns.
When things aren’t working, some teams interpret ‘self-managing’ as autonomous. These teams change the guardrails to suit their personal preferences for working rather than for the benefit of their customers and the organisation. They decide to drop events like the Daily Scrum because they feel it isn’t working for them istead of asking ‘why’ isn’t it working’ AND ‘how do we fix it?’.
Whether its when the Retro gets stale, or when things aren’t working, the ROTI Retrospective pattern can help teams address their problems with the effectiveness of their practices by placing the ownership of improvement back on the team and asking them quite simply, “what’s ONE THING in your control to change to improve what YOU get out of this event“.
How do you write great User Stories?
Backlog Refinement is a critical part of good practice in Scrum. Refining the Product Backlog ensures that the Team and Product Owner have sufficientl
What metrics do you need to understand whether you’re going to achieve enterprise outcomes for agile transformations
Should you have business as Product Owners? Is the Release Train Engineer a Delivery Manager? Where do Project Managers go? Aren’t Epic Owners the executive? Everyone gets these things wrong. Find out how to avoid SAFe’s implementation traps.
Are you still asking the ‘three questions’. It’s time you learned some better patterns to inspect your progress toward the team’s Sprint Goal.
You have reports to deliver to executive. Delivery, risk, and cost is foremost on their mind. What kind of reports on your agile capability and delivery, based on objective agile project management metrics, are going to provide you with the best transparency of what’s really going on?
Copyright © Zen Ex Machina® and ™ (2021). All rights reserved. ABN 93 153 194 220