The library hotspot-lending team visualizes only developer tasks, so wait for Product Owner clarification never appears. What should the SM/TC include on the board?
Select an answer to reveal the explanation.
Short Explanation
If the board shows only coding, it is missing half the commute. Waiting on the Product Owner still uses the team’s clock. Put every capacity-consuming wait on the same map.
Full Explanation
Team boards should show all work that consumes capacity, including waits on other roles such as Product Owner clarification—not developer tasks only. If the board shows only coding, it is missing half the commute. Waiting on the PO still uses the team's clock for casework, permitting, or other civic products.
Visualizing developer tasks only because visualization is supposedly an engineering artifact fails because Lean flow includes every capacity-consuming state. Keeping PO wait on a private chat so the board stays clean fails because cleanliness that hides waits is anti-transparency. Showing only stories that already have acceptance criteria and deleting the rest fails because unreadiness waits are exactly what coaches need visible.
Exam caveat: capacity includes waiting, clarification, and handoffs—not only typing. Operational check: add states or policies for PO clarification and similar waits, stop hiding those waits in chat, include them in WIP and flow-time views, and coach the PO and team to clear clarification queues deliberately. Including PO waits teaches product and delivery roles that clarification delay is still delay for the resident. Including PO waits teaches product and delivery roles that clarification delay is still delay for the resident.