The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
A manager has no standing right to attend a Sprint Retrospective under the Scrum Guide, but the Guide does not ban managers from attending. If a manager asks to join, first clarify what they need, then privately ask the Scrum Team whether they can speak openly with that manager in the room. Invite them only if the team is comfortable, with a defined listening-and-support role. If not, offer a different way to address the manager’s need.
What the Scrum Guide says about managers attending
The Scrum Guide defines the Sprint Retrospective as the event where the Scrum Team inspects how the Sprint went and plans ways to increase quality and effectiveness. The team considers its interactions, processes, tools, and Definition of Done, then identifies changes that could help. The Guide assigns this inspection and improvement work to the Scrum Team; it gives line managers no standing attendance entitlement, but it also does not expressly prohibit a manager from attending. The Scrum Guide describes the team as self-managing and without sub-teams or hierarchies.
The Scrum Master is accountable for the Scrum Team’s effectiveness, including helping it improve its practices. That responsibility supports the facilitator’s role in creating a productive retrospective and helping the organization address barriers; it does not make the Scrum Master the team’s manager.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11For a one-month Sprint, the retrospective is timeboxed to a maximum of three hours. Shorter Sprints usually have shorter retrospectives. The purpose is team learning and improvement, not an individual performance review or management report.
#1 Best Overall
Decide based on the team and the manager’s purpose
There is no one-size-fits-all answer to whether a particular manager should attend. A manager may be able to remove an organizational impediment, but their authority can also affect how freely people speak. Scrum.org identifies warning signs such as passive participation, blame, concerns being discussed outside the room but not raised in it, and discomfort when someone behaves as though they manage the team. These are reasons to assess the actual relationship rather than apply a blanket rule. Scrum.org’s facilitation guidance emphasizes trust, participation, and acting on agreed changes.
- Ask the manager what they want from the meeting. Is there a specific impediment they can remove, a recurring delivery concern, or a wish to observe? The answer helps distinguish a practical support need from a request for ongoing access.
- Ask the team privately. Without the manager present, ask whether members can speak honestly about difficult issues with this person in the room. Make the decision about this manager and this retrospective, not about managers in general.
- Choose the least disruptive way to meet the need. A one-time invitation can be evaluated before becoming a recurring practice. Revisit the decision if the manager’s role, team membership, or the team’s comfort changes.
Scrum.org contributor Stefan Wolpers argued in an August 23, 2021 article against making line-manager attendance regular or required, and suggested other ways to keep managers informed. That is expert commentary, not a Scrum Guide prohibition. His article supports clarifying the manager’s information need and using another forum when attendance could inhibit candor.
If the team agrees to an invitation
Set expectations before the retrospective begins so the manager’s presence supports the team’s work rather than changing it into an evaluation. The facilitator can explain the purpose and ground rules to everyone at the start.
- Manager: listen first, ask clarifying questions, and offer help removing relevant organizational impediments. Do not evaluate individuals or defend decisions while the team is describing its experience.
- Facilitator: make space for quieter members, keep discussion focused on working practices and conditions rather than personal blame, and ensure the team—not the manager—chooses its improvements.
- Whole team: turn discussion into a small number of actionable changes and make progress visible. Scrum.org recommends prioritizing one or two improvements when a team has generated a long list. Its retrospective guidance describes collecting ideas, discussing them, and prioritizing improvements; sticky notes and a whiteboard are one possible aid, not a Scrum requirement.
A useful opening might be: “This meeting is for the team to inspect how it worked and choose improvements. We’ve agreed you can join to listen and help with organizational impediments. Please ask clarifying questions, and leave decisions about team improvements to the team.”
Rank #3
If the team is uncomfortable with the manager attending
Decline attendance for that session and address the manager’s underlying need separately. Scrum.org’s manager-focused commentary suggests that managers can stay informed through other appropriate channels; protecting candid retrospective discussion does not require withholding agreed improvement work.
- For a specific organizational barrier: arrange a separate conversation with the manager about the impediment and what support is needed.
- For progress visibility: share the improvement actions the team has agreed to take and their resolution status, without circulating sensitive discussion or attributing comments to individuals.
- For the Sprint outcome: invite the manager to a suitable stakeholder forum. The Sprint Review is the Scrum event for the Scrum Team and key stakeholders to inspect the Sprint outcome and discuss adaptations; it is not a substitute for sharing private retrospective discussion.
You can say: “The team isn’t comfortable having a manager in this retrospective, so we won’t invite you this time. I can share the agreed improvement actions and their status, and we can meet separately about the organizational issue you’re trying to resolve.”
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Keep the retrospective a team improvement event
The practical test is whether the team can still participate honestly and choose its own improvements. If the manager’s presence helps remove a barrier and does not suppress candor, a bounded invitation may work. If the team says it would hold back, use a separate channel for the manager’s support or information needs instead of turning the retrospective into a reporting meeting.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
