Example Achievement Log for a Scrum Master

This Scrum Master managed two cross-functional teams through a major platform migration, unblocking bottlenecks and handling sprint rhythm across inconsistent capacity. The log tracks the visible work of facilitation, the things that broke, and the moments when teams and leadership named what stuck.

A year in the life of a Scrum Master's log

Jan - task: Took on Payments squad after their Scrum Master left mid-sprint. Ran catchup with Anil (PM) and Priya (eng lead) to map current state. Sprint 6 had no definition of done and backlog grooming hadn't happened in weeks.
Feb - achievement: Rebuilt backlog refinement for Payments. Set standing Wednesday slots, templated story format, got five stories ready for Sprint 7. Throughput went from 18 to 31 story points completed.
Feb - task: Platform migration kicked off. Both squads (Payments and Core API) depended on new event bus deployment. Built cross-team sync twice weekly instead of async Slack threads. Blockers surfaced faster but team started running at 75% capacity.
Apr - feedback: James (VP Eng) said in May 1-1: 'Migration would have slipped six weeks without you finding dependencies early.' Said it casually but made a note.
May - achievement: Core API team failed to deploy event bus twice in three days. Root cause was unclear stories and no test env parity. Ran a focused retro, reworked acceptance criteria template, added staging validation step to DoD. Next four sprints had zero deployment failures.
May - task: Capacity stayed at 72% through July. Stopped pushing teams to take new work. Cut ceremony time instead: standups 12 mins, retros moved to every other sprint. Both teams resisted but understood during migration crunch.
Jul - feedback: Priya (Core API lead) in retro: 'You cut the noise so we could focus on the hard thing. That matters.' First time she'd offered unsolicited feedback.
Aug - achievement: Migration completed on Sept 8. Event bus live, both squads cut over, zero incidents in first 48 hours. Ran celebration retro, captured lessons, and brought back skipped ceremonies for Sprint 19.
Oct - achievement: Started coaching new Scrum Master for Infrastructure squad starting cold. Met weekly for 7 weeks. Covered backlog management, sprint planning under ambiguity, and how to run retros that don't repeat last retro's action items.
Nov - task: Payments squad requested daily standups after two weeks of missed cross-team context. Switched from async updates. Also surfaced that nobody on the team owned quality metrics. Created dashboard tracking defect escape rate and build time.
Dec - feedback: Anil (Payments PM) in planning session: 'You spotted the quality blind spot before it cost us velocity.' Pointed out the dashboard saved them debugging time in December release.

What makes a strong entry

What most people write: Improved team velocity and process.

What went in the log: Rebuilt backlog refinement for Payments. Set standing Wednesday slots, templated story format, got five stories ready for Sprint 7. Throughput went from 18 to 31 story points completed.

The strong version names the specific day, the artifact changed (templated stories), the exact count of stories prepared, and the before-and-after numbers. A review reader six months later can picture what was fixed and verify the impact was real.

What most people write: Handled a sprint deployment issue and fixed it.

What went in the log: Core API team failed to deploy event bus twice in three days. Root cause was unclear stories and no test env parity. Ran a focused retro, reworked acceptance criteria template, added staging validation step to DoD. Next four sprints had zero deployment failures.

The strong version documents the failure itself (two deployments, three days), the diagnosed cause (two specific things), the three concrete fixes applied, and the measurable outcome (four consecutive sprint clean record). This shows root-cause thinking, not a whitewash.

How this becomes your review in November

I inherited the Payments squad mid-year with no working backlog and took over the Core API Scrum Master role partway through the platform migration. I rebuilt refinement process and tooling for Payments, moving throughput from 18 to 31 story points, and when Core API hit deployment failures I ran a focused retro and reworked acceptance criteria and testing process such that the next four sprints had zero incidents. During the migration I kept both teams unblocked by surfacing dependencies early and right-sizing ceremony time to preserve capacity, which James called out in our May conversation as the work that prevented a six-week slip. I also coached the new Infrastructure Scrum Master through seven weeks of pairing, covering backlog management and retro design.

Starting your own log

Don't try to reconstruct a year you have already had. Start from today, one line whenever something happens, and let it build. The Perform Review Achievement Log does this for you and can capture wins straight from Slack, and how to start an achievement log covers the wider playbook.

Example Logs for Related Roles

Ready to start your own? Start your Achievement Log free, see how the Perform Review Achievement Log works, or browse performance review phrases for Scrum Master.