Manager wants to attend your Sprint Retrospective. Risk and response?

WHAT THIS TESTS: The interviewer is checking whether you understand that a retrospective is a protected space for inspection and adaptation, and that psychological safety is a prerequisite rather than a nice-to-have. They want to see if you recognize power dynamics, know how to negotiate boundaries with leadership, and can balance transparency with team effectiveness. This is not about being anti-manager; it is about understanding the conditions under which honest feedback occurs.

A GOOD ANSWER COVERS: First, name the primary risk explicitly. The observer effect means team members will self-censor concerns about management, process failures, or interpersonal friction because the manager holds hiring, firing, and promotion influence. Second, propose an alternative forum before accepting attendance. Suggest a separate demo, status meeting, or team update where the manager can get the information they need without poisoning the retrospective. Third, if the manager still attends, treat it as a time-boxed experiment with explicit ground rules. The manager is an observer, not a participant; they do not steer the agenda, defend decisions, or assign action items. Fourth, separate information gathering from problem solving. If the manager needs to know blockers, feed that through the Scrum Master or a dashboard; the retrospective is for the team to own its process.

COMMON WRONG ANSWERS: Saying that agile values transparency so the manager should just come. Confusing transparency with the absence of boundaries. Claiming that a servant leader has no power and therefore no chilling effect; power dynamics exist regardless of intent. Offering to let the manager speak but promising the team will still be honest; this ignores well-documented organizational behavior. Agreeing to let the manager attend without preconditions; this signals you do not understand the purpose of the retrospective.

LIKELY FOLLOW-UPS: How would you handle it if the manager insists despite your recommendation? What would you do if the team brings up the manager's own behavior as an impediment during the retrospective? How do you reconcile this with agile principles of openness? What data would you look at to decide whether the experiment worked?

ONE CONCRETE EXAMPLE: You tell the manager, I can share the anonymized themes and action items within twenty-four hours, which covers your need to be informed. If you still want to observe, we will try it for one thirty-minute segment of the next retro with you listening only. Afterward, I will survey the team on a one-to-five scale about whether they felt safe speaking freely, and we will review that data together before deciding on future attendance.

Source: echometerapp.com