Manager Wants to Attend Your Sprint Retrospective. How Do You Respond?
Tests your grasp of psychological safety and stakeholder management. A good answer identifies the risk to open feedback, proposes other ways to inform the manager, and suggests a structured, one-time experiment if they must attend.
What's really being asked
This question assesses your understanding of psychological safety as the foundation of effective retrospectives. It's not just about Scrum rules; it's about your ability to protect your team's process, diagnose a stakeholder's underlying need (to 'be informed'), and negotiate a solution that serves both the team and the manager. It separates candidates who just follow rules from those who understand principles.
The full answer
A strong answer has four parts. First, state the primary risk clearly: the manager's presence, no matter how well-intentioned, will chill open feedback and reduce psychological safety. Second, seek to understand the manager's goal by asking 'Why?'. What information are they looking for? This opens the door to alternatives. Third, propose those alternatives. Suggest a separate meeting with you or the team, or offer to provide a summary of the key impediments and action items (without attribution). Fourth, if they insist on attending, frame it as a one-time, structured experiment. This includes getting the team's consent, setting expectations that the manager is an observer only, and scheduling a debrief with the manager afterward, not during the retro.
The mistakes people make
A junior answer is to just say 'No, Scrum says managers can't attend.' This is rigid and poor stakeholder management. Another red flag is to immediately agree without any conditions, which shows you don't prioritize the team's psychological safety. A candidate who can't articulate why the manager's presence is a problem, beyond just 'it's the rule,' is also a concern. They might say 'it could make people uncomfortable' but can't explain the downstream impact on team performance and continuous improvement.
What usually comes next
'What if the team says they are okay with the manager attending?' (This tests if you understand subtle power dynamics). 'What if the manager is also the team's tech lead or a former IC on the team?' (Tests your ability to handle dual-role complexity). 'What specific themes or information would you share with the manager after the retro, and what would you keep confidential?'
A concrete example
'I'd tell the manager, 'I want to make sure you get the information you need. To protect the team's open feedback loop, which is fragile, how about we try this: I'll synthesize the key obstacles and our planned improvements from the retro and share them with you an hour after it ends. This gives you the signal you need without disrupting the process. If that's not enough, we can discuss you attending a future retro as a one-time experiment with you as a silent observer.''
Interview question
A manager asks to join your team's retrospective. Which response best balances protecting team safety with addressing stakeholder needs?
- a.Inquire about the manager's goals and offer to provide a summary of key impediments and action items after the meeting.Correct
- b.Politely decline, explaining that Scrum rules prohibit managers from attending to ensure team confidentiality.
- c.Welcome the manager to attend, as their involvement can help remove organizational impediments the team identifies.
- d.Inform the manager you need to ask the team for their consent first before you can provide an answer.
Why? this is the answer
This approach seeks to understand the manager's underlying need and proposes an alternative that satisfies it without compromising the team's psychological safety. Simply welcoming them ignores this risk, while putting the decision on the team creates an awkward power dynamic.
Just read this? Test yourself on what you have been reading.
Read the original → echometerapp.com
You just looked this up. Could you explain it out loud?
That is the part interviews actually test. Tezvyn takes questions like this one and gives you what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on agile — each one lists the topics its interview covers.
See open roles