Community-garden plot software shows excellent cycle time on tiny chores and terrible time on resident-facing features. Average cycle time still makes the team look fast. What should the Scrum Master/Team Coach use?
Select an answer to reveal the explanation.
Short Explanation
If the garden crew mows paths in an hour and never finishes a plot assignment, the average still looks zippy. Mix matters. Pair flow time with distribution so resident-facing work is not drowned by tiny chores.
Full Explanation
Flow metrics must be read together: excellent cycle time on tiny community-garden chores can mask terrible flow time on resident-facing features if only an average is shown. Flow distribution reveals the mix of work; flow time shows how long each class takes. Counting chores or hours on chores further hides citizen value. The Scrum Master/Team Coach should present time and distribution together.