The AOS quarterly retrospective is the honest look back that makes the next quarter better. Based on the Accelerate Operating System (AOS) model, it scores priorities and the scorecard, separates what went well from what to improve, and turns the lessons into concrete changes for the next cycle.
Run it at the end of each quarter, ideally just before quarterly planning so the lessons feed straight into the next set of priorities. Pairing the retro with planning keeps reflection from becoming a ritual no one acts on.
Keep it to the leadership team, five to twelve people who lived the quarter and will shape the next one. A psychologically safe room is essential, since a retro that punishes honesty stops surfacing the truth.
Set a learning-not-blame tone, score the priorities and scorecard plainly, then separate what went well from what to improve. Dig into causes rather than symptoms, and convert the discussion into a few concrete operating changes with owners and carry-forward items for planning. Note: this agenda is an independent interpretation of the AOS quarterly-rhythm model and is not affiliated with or endorsed by any provider.
Make every quarter teach the next one. Run it in OrgTP and carry lessons, changes, and carry-forward items straight into planning, with OrgTP adapting to your cadence.
75 minutes total · 6 sections
While bi-weekly sprint retrospectives are excellent for tactical, short-term adjustments, teams often lose sight of the bigger picture. To drive long-term growth, prevent systemic burnout, and align on macro-level goals, organizations must run a comprehensive Quarterly Retrospective.
A quarterly retrospective allows your team to step out of the day-to-day execution, analyze high-level trends over the past 90 days, and make strategic adjustments to your operating system.
This comprehensive guide provides a battle-tested Quarterly Retrospective Template and a step-by-step agenda to help your team evaluate performance, celebrate major wins, and align on strategic priorities for the upcoming quarter.
A Quarterly Retrospective is a strategic, 75-minute team reflection session held at the end of each quarter.
Unlike sprint retrospectives - which focus on immediate process tweaks - the quarterly retrospective is designed to evaluate macro-level trends, team health, cross-functional collaboration, and long-term strategic alignment. It is the perfect opportunity to assess whether your team's daily habits are actually moving the needle on your quarterly goals.
To cover historical performance, team health, and future planning without rushing, we recommend a structured 75-minute time-boxed agenda:
| Time | Agenda Item | Objective |
|---|---|---|
| 00:00 - 00:10 | Set the Tone & Ground Rules | Welcome the team, review the quarterly timeline, and establish a safe, collaborative environment for honest feedback. |
| 00:10 - 00:25 | Score Priorities & Scorecard | Review the past quarter's goals, KPIs, and key milestones. Celebrate major wins and document any missed targets. |
| 00:25 - 00:45 | What Went Well & What Didn't | Open the floor for team members to share their macro-level feedback on processes, tools, and collaboration. |
| 00:45 - 01:05 | Deep-Dive & Problem Solving | Prioritize the most critical systemic issues raised and brainstorm structural solutions or process improvements. |
| 01:05 - 01:15 | Carry-Forward & Close | Agree on 2-3 high-priority action items for the next quarter, assign owners, and officially close the session. |
To keep your quarterly review strategic, guide your team's discussion around these three macro-level pillars:
Evaluate how the team worked together over the past 90 days. Ask: Did we have the right people in the right seats? Did we experience communication breakdowns with other departments? How are the team's energy and burnout levels?
Analyze the efficiency of your operating system. Ask: Are our current meetings, reporting structures, and workflows serving us, or are they creating unnecessary overhead? What tools did we adopt that helped us, and which ones slowed us down?
Assess your progress against high-level goals. Ask: Did we hit our quarterly priorities? If we missed targets, was it due to poor execution, unrealistic planning, or unexpected market shifts? Are we still aligned on our long-term vision?
Do not rely solely on memory. Before the meeting, gather key performance metrics, sprint velocity charts, and any employee feedback data. Having a clear, objective record of the past 90 days prevents recency bias from dominating the discussion.
If an issue kept coming up throughout the quarter, a simple process tweak won't solve it. Use the quarterly retrospective to address the root cause of systemic problems - even if it requires structural changes, role reassignments, or retiring legacy tools.
Because this is a quarterly meeting, it is tempting to create a massive list of process improvements. Resist this urge. Agree on no more than 2 to 3 high-impact operational changes for the upcoming quarter. Ensure each change has a clear owner and is integrated into your weekly tracking.
A sprint retrospective is tactical and held every 2 weeks to make immediate, minor adjustments to the team's workflow. A quarterly retrospective is strategic and held every 90 days to evaluate macro-level trends, team health, and long-term alignment.
The quarterly retrospective should be attended by the entire functional team, including the Product Owner, Scrum Master, Developers, and any key cross-functional partners who worked closely with the team during the quarter.
Ensure the facilitator maintains a strict time-box for each agenda item and actively steers the conversation toward constructive, action-oriented solutions. Use the "Set the Tone" phase to remind the team that the goal is continuous improvement, not finger-pointing.
Any systemic issues that cannot be resolved with immediate action items should be documented and carried forward into the upcoming quarter's strategic planning sessions or addressed by leadership as structural priorities.
Stop copying agendas into a doc every week. OrgTP runs your meetings live — scorecard, rocks, issues, and to-dos all in one place, with your AI agents in the room.