The wastewater SCADA team never invites plant operators to refinement. What should the Scrum Master / Team Coach do?
Select an answer to reveal the explanation.
Short Explanation
Building SCADA screens without operators is paving a control room from the parking lot. The people who run the plant are a collaboration partner, not a yearly survey. Invite them to refinement or the increment will surprise the shift that has to use it.
Full Explanation
Wastewater SCADA work that operators must run belongs in refinement with those consuming operators present so the people who run the plant shape the backlog. Operator constraints, shift realities, and alarm practices are domain knowledge developers alone often miss; excluding them produces technically neat increments that fail on the plant floor. Keeping refinement developer-only to avoid "slowing" the conversation trades short meeting speed for long operational rework. Interviewing operators once a year treats collaboration as a ceremonial sample rather than continuous shaping of municipal control work. Asking the RTE to write operator stories so the team never meets the plant relocates domain authorship to the train engineer and still skips the people who live with the SCADA changes. Exam caveat: SASM coaches bringing consumers and operators into refinement for shared understanding; annual interviews, developer-only refinement, and RTE ghostwriting are not substitutes for that collaboration. Operational check: invite plant operators to the next SCADA refinement, capture at least one operator-shaped acceptance criterion on a high-priority story, confirm the team can demo that criterion to operators before release, and keep an ongoing invitation pattern rather than a one-off visit. Document operator constraints that repeatedly surface so they inform Definition of Done.