Value Stream Mapping: add "% complete and accurate" measures between stages.
Problem to solve
There's a really powerful metric used in Value Stream Mapping: "% complete and accurate". It helps identify where work has to flow back upstream, which is wastage.
Further details
In VSM generally, say within an organisation (as opposed to narrowly within a code lifecycle) it's bad if work has to flow back upstream. The key measure to look for is what percentage of work received by a workstation is complete and accurate. Your goal is 100%.
From the best book on this topic "%c/a is obtained by asking downstream customers what percentage of the time they receive work which is 'usable as is', meaning that they can do their work without having to correct the information that was provided, add missing information that should have been supplied, or clarify information that should have and could have been clearer" - Kindle location 1196, Value Stream Mapping, Martin & Osterling.
Proposal
Gitlab could possibly (a) derive this from rejections or other actions taken (which would be harder to implement), or (b) allow a manager to ask stage-owners to answer a poll about it, then a manager can raise issues for process change to resolve the root cause of the shortfall.
What does success look like, and how can we measure that?
This issue is so we can discuss the proposal and come up with success measures.
Links / references
Related epics &433
~"feature proposal" ~"Plan" boards direction ~"devops:manage" mapping