Parks field-lighting work is on a team board, but expedite stickers cover half the cards. What should the SM/TC coach about classes of service?
Select an answer to reveal the explanation.
Short Explanation
If everything is a siren, nobody hears a siren. Expedite is a scarce class of service with a policy, not a sticker for half the lighting board. Guard it or the board is just colorful noise.
Full Explanation
Expedite for lighting, safety, or similar tickets must stay explicit, scarce, and policy-bound, or the visualization stops meaning anything. If everything is a siren, nobody hears a siren. Expedite is a scarce class of service with a policy, not a sticker for whichever parks ticket shouted last.
Treating every lighting ticket as expedite so nothing waits fails because universal expedite collapses classes of service into chaos. Removing classes of service because they confuse leadership fails because education beats deletion of a useful flow tool. Using expedite stickers as a substitute for WIP limits fails because expedite without WIP discipline still overloads the system.
Exam caveat: true emergencies deserve expedite; convenience does not. Operational check: define who may declare expedite and under what citizen-impact criteria, cap how many expedites can be active, keep standard WIP limits, and review expedite usage each iteration so parks lighting work does not normalize permanent sirens. Scarce expedite protects true safety lighting work from being normalized into permanent priority inflation. Scarce expedite protects true safety lighting work from being normalized into permanent priority inflation.