FY21-Q4 Ops, Continuous Delivery, Product KR: Achieve 70% Say/Do with 100% reprioritised => 33%

Key Result: Achieve a 70% say do ratio and 100% with reprioritisations based on: https://app.periscopedata.com/app/gitlab/658030/Say-Do-Ratios

We have two measures within Say/Do ratio. One includes issues marked Deliverable that were removed from the milestone during the course of the milestone, the other does not. If choosing to optimise planning around re-prioritising issues, managers should target 100% say/do.

Group	%13.5	%13.6	%13.7	%13.8	avg
groupconfigure	82%/75%	50%/83%	44%/100%	57%/80%	58%/84%
~"group::package"	64%/78%	67%/100%	65%/100%	65%/85%	65%/95%
grouprelease	0%/0%	73%/100%	80%/100%	100%/100%	84%/100%

Retrospective

Good

• grouprelease has achieved a very good say do in a short period for a new team
• groupconfigure seems to be improving their issue hygiene (general increase in second percentage)
• ~"group::package" had a good series of milestones that were perhaps a little ambitious

Bad

• 33% is worse than last quarter
• Both ~"group::package" and ~"group::package" seem to be struggling with issue hygiene
• grouprelease could use some more ambitious goals in their milestones (this is kinda good news ;-) )

Try

• More ambition could be helpful for grouprelease
• Less ambitious milestone for ~"group::package"
• More evaluation of capability within milestone for ~"group::package" and groupconfigure

/cc @sgoldstein