The Silent Analyst and the Offshore Handoff
A health-tech company runs a product team of nine: five developers in one location, a designer, a business analyst, a QA engineer, and a product owner. In the last three retrospectives the same theme surfaced: the business analyst, who holds most of the domain knowledge about clinical workflows, does not speak in refinement or planning. Developers say they discover requirements only after they start building. The analyst told the Scrum Master privately that the two senior developers routinely dismiss her input and that she no longer bothers. Sprint review attendance by clinicians has dropped to one person. Two recent stories were rejected at review because the clinical rule was misunderstood. The Scrum Master has been running the ceremonies efficiently and is proud that meetings end on time.
1. What is the Scrum Master's primary failure here, and what is the first intervention?
Read the worked answer
The Scrum Master has optimized for meeting efficiency rather than for the team's ability to self-organize and surface problems. Three retrospectives produced the same theme and no change, which means the retrospective is functioning as a ritual rather than a feedback loop. That is the primary failure.
The first intervention is not a team-building exercise. It is to make the pattern undeniable and to address the power dynamic directly. I would meet the analyst to confirm what she is willing to have shared, then raise the behavior with the team in specific, observable terms: which refinement sessions, which interruptions, what happened to the stories afterward. Naming behavior without attributing intent keeps it workable.
I would also examine my own contribution. Ending meetings on time while one voice is being suppressed is a false success. I would change my facilitation: structured turn-taking in refinement, written input collected before discussion so the analyst's domain knowledge enters the record regardless of airtime, and explicit norms that the domain expert's input is a gate before sizing.
Finally, I would check whether the two senior developers understand the cost. Two rejected stories and a shrinking clinical presence at review are concrete consequences they can connect to their behavior.
2. How do you rebuild the sprint review so clinicians return?
Read the worked answer
The review has lost its purpose. If clinicians attended and saw slides or status updates, they had no reason to come back. The review must be a working session where they see the product and their feedback changes it.
I would restructure it around the clinical workflow, not the backlog. Prepare two or three scenarios drawn from real claim or care pathways, demonstrate them end to end, and reserve most of the time for the clinicians to try them and react. Invite them with a specific ask, such as validating a particular decision rule, rather than a generic invitation.
I would also address scheduling and format friction. Ask the remaining clinician attendee what would make attendance feasible: a shorter slot, remote option, or asynchronous recording with a structured feedback form. One engaged clinician who is asked for something specific is more valuable than five passive observers.
Finally, I would close the loop visibly. When clinical feedback changes a story, tell the clinicians what changed and why. Attendance follows demonstrated influence, not repeated invitations.