I honestly have never seen that acronym but apparently popular from Intel management practices?
I honestly have never seen that acronym but apparently popular from Intel management practices?
rhymes with claw! :-)
Plainspeak > newspeak.
Thanks.
Previous jobs have used them too. They're pretty popular I think.
They think it’s a godsend because suddenly they can measure their progress in some way that is not just “story points per sprint” ignoring the fact this measurement only makes sense within the system itself and may not reflect the reality at all.
I feel I could think of examples. There are so many dimensions of valuable work (no security holes, being nice, not reinventing the wheel, documenting well, long-term stability/refactorability, code being reusable by other teams) but I imagine OKRs can't cover all those facets.
It almost seems as fruitless as trying to measure friendship by OKRs.
management introduce OKRs so that they don't have to solve actual managerial problems - the OKRs _are_ their solution! That it misses a bad employee cruising, or a great employee's contribution is a footnote. After all, when the system is using an OKR to guide the actions of employees, and you go against it, it's basically career suicide.
I personally don't like OKRs or any performance metric that isn't directly tied to customers' actions (e.g., growing customer numbers, or growing revenue etc).
So now we're setting the Objectives, and measure the KPIs that are defined to reflect the objectives. The actual means to move the KPI, which would be the KR (key results) in OKRs, are no longer defined in quarterly planning sessions, but are selected and updated by the team during sprint planning.
This gives the teams a large independence in What they are doing while still maintaining business alignment and meaningful measurements.