Monthly Milestone Map Retrospective

Review the month's milestones, lessons and next goals.

Try this retrospective live

Milestones Reached

What key achievements and milestones did we hit this month?

We shipped the new onboarding flow ahead of schedule and the early feedback has been great.
Hit our community engagement target two weeks early this month.
Finally closed out the backlog of long-standing support tickets.
Obstacles Navigated

What challenges did we face and how did we work through them?

Dependencies on the external vendor slowed us down more than expected.
We underestimated how long testing would take and had to push the release.
Competing priorities made it hard to focus on the roadmap.
Lessons Learned

What insights or learnings can we carry forward?

Breaking large tasks into smaller chunks made progress much easier to track.
We need to involve QA earlier in the process to avoid last-minute surprises.
Regular check-ins kept everyone aligned and reduced misunderstandings.
Goals Ahead

What do we want to achieve in the month ahead?

Launch the beta version of the new feature to a select group of users.
Establish a clearer process for prioritizing incoming requests.
Run a knowledge-sharing session so the whole team understands the new platform.

What is the Monthly Milestone Map?

A sprint retrospective looks at a couple of weeks. The Monthly Milestone Map steps back to look at a whole month, so your team can see how far it has come and what to aim for next. It picks up the patterns a single sprint is too short to show: the obstacle that came up three times, or the habit that quietly made everything easier. The map has four stops: the milestones you reached, the obstacles you worked through, the lessons you learned and the goals for the month ahead. As people add notes, recurring themes become visible, which makes it a good fit for teams that plan on a monthly rhythm or want a regular checkpoint to adjust course. Lessons connect back to the obstacles that taught them, and goals build on both, so the conversation stays tied to real outcomes. Run in TeamRetro, each month's map becomes a record of what the team achieved and learned, and you can open last month's goals at the start of the next session. Product teams, cross-functional squads, community groups and volunteer teams all use it to mark progress and leave with a short list of goals for the month ahead.

Monthly Milestone Map retrospective format

Milestones Reached

What key achievements and milestones did we hit this month?

This column captures the concrete wins and progress from the month. Ask people to look past completed tasks to the moments, deliverables and team accomplishments that mattered. Ask quieter members what they were proud of, and make sure big launches and small, steady gains both get a mention.

Obstacles Navigated

What challenges did we face and how did we work through them?

Use this column to surface the roadblocks, delays and difficulties the team ran into. Keep it constructive: you're here to learn from them, not assign blame. Ask how each obstacle was handled and which ones are still unresolved, so they can feed into next month's goals.

Lessons Learned

What insights or learnings can we carry forward?

This column turns the month's experiences into lessons the team can keep. Ask for specific, actionable reflections over vague observations. Point out lessons that could change how the team works, and connect them to the obstacles raised earlier.

Goals Ahead

What do we want to achieve in the month ahead?

This column turns reflection into intention. Help the team set clear, realistic goals that build on the milestones and lessons you've just discussed. Link each goal to a person or group, and keep the list short so it doesn't become a wish list nobody can manage.

When to use this retrospective

  • Your team works on a monthly cadence and wants a regular checkpoint to review progress and plan ahead.
  • You want to look past individual sprints to see longer-term progress and challenges that keep coming back.
  • You lead a community group, volunteer team or cross-functional squad that likes to mark milestones together.
  • You want to turn a month's lessons into a few concrete goals and keep momentum from month to month.

Suggested icebreaker questions

  • If this past month were a movie title, what would it be called?
  • What's one thing you're personally proud of from the last month, work or otherwise?

Want a warm-up your team plays, not just answers out loud? Browse free icebreakers →

Ideas and tips for your retrospective meeting

  • Gather a few metrics or milestones before the session so the team has a shared reference point.
  • Keep the milestones section celebratory. Recognizing wins gives the team energy for the month ahead.
  • Treat obstacles as things to learn from, not failures, so people talk about them openly and without blame.
  • Limit the number of goals so the team stays focused and the commitments stay achievable.
  • Start with anonymous brainstorming so quieter voices and dissenting views are captured before group discussion.
  • Open the session by revisiting last month's goals, so the team sees what got done and what slipped.

Frequently asked questions

How long does a Monthly Milestone Map retrospective take?
Most teams take 60 to 90 minutes. A month gives you more to cover than a single sprint, so allow a little more time than you would for a standard retrospective.
When should I use a Monthly Milestone Map?
Use it if your team works on a monthly rhythm, or if you want a regular checkpoint to step back from day-to-day work, mark progress and agree on next month's goals.
How is it different from a sprint retrospective?
A sprint retrospective covers a single iteration, usually one to four weeks. The Monthly Milestone Map follows the calendar month, so it suits teams that don't work in sprints and shows milestones and recurring challenges across several pieces of work.
Who should participate in a Monthly Milestone Map?
Everyone who contributed to the month's work. You can also invite stakeholders or cross-functional partners who can add context to the milestones and help shape next month's goals.
Can I use this for non-software teams?
Yes. The prompts are general, so the format works for community groups, marketing, operations and any team that reviews its progress monthly.
How do I make sure the goals we set actually get done?
Give each goal an owner, keep the list short and realistic, and review the goals at the start of next month's session.

Related templates

WWE Smackdown Showdown Retrospective

Tag-team your sprint review with a wrestling theme.

Working, Not Working Retrospective

Sort what's working from what isn't, then fix it.

Quarterly Retrospective

Step back from the sprints and review the whole quarter.

Baby Steps Retrospective

Pick one small change your team will actually finish.

Ready to run this retrospective?Try this retrospective live