Food-inspection mobile app crashes are discovered only when field staff call the help desk. What should the Scrum Master/Team Coach establish?
Select an answer to reveal the explanation.
Short Explanation
If the only crash detector is a field inspector on hold with the help desk, the kitchen already served a bad meal. Wire up telemetry so the team hears the thud immediately. Do not wait for a pile of complaints, and do not blame the people who called.
Full Explanation
Fast production telemetry is part of quality-for-flow. Food-inspection mobile app crashes discovered only when field staff call the help desk mean the team learns late and through pain. The Scrum Master/Team Coach should establish rapid crash/feedback signals without blaming inspectors or waiting for complaint piles—so public-health field tools improve from data, not from anger.
Maintaining a blame list of inspectors who report crashes fails by concept: it punishes the feedback channel and suppresses reporting. Silencing crash reports until a quarterly steering meeting fails by concept by delaying response to field failures. Disabling crash reporting so the board stays green fails by concept: it optimizes appearances while inspectors struggle in restaurants and facilities.
Exam caveat: SAFe DevOps and quality practices value fast feedback from production; telemetry and blameless response beat complaint-driven discovery. Telemetry does not replace root-cause fixing—it accelerates it for civic mobile tools.
Operational check: enable crash analytics/alerts for the inspection app, route signals to the team within the iteration, review top crashes in the next sync without blame, and verify mean time to detect and fix drops versus help-desk-only discovery.