Blocked hydrant-mapping stories sit in Dev as if they were still moving. What should the SM/TC coach the team to do?
Select an answer to reveal the explanation.
Short Explanation
A blocked hydrant story in Dev is a stalled car still counted as traffic moving. If the blocker is invisible, nobody swarms it. Mark it so the wait is honest.
Full Explanation
Flow visualization must distinguish active work from blocked work. Burying GIS vendor waits inside Dev inflates apparent WIP of moving items and delays impediment removal. Explicit blocked overlays or states make wait time and ownership visible to the team and SM/TC. Deleting stories or closing them early falsifies flow time and hides the real constraint.