Example Achievement Log for a Agile Coach

Product & Project Management

Example Achievement Log for a Agile Coach

Here's a year in the life of an Agile Coach working across a financial services organisation, moving teams from waterfall into iterative delivery. The log shows how coaching relationships develop, where resistance emerges and shifts, and what 'done' looks like in this role.

A year in the life of a Agile Coach's log

  • Jan - task: Took on the Compliance & Licensing team after their Scrum Master left. Team of six, running two-week sprints but ceremonies clashed with monthly audit windows. Started mapping their actual calendar constraints with the team lead.
  • Mar - achievement: Compliance team moved sprint reviews to Friday mornings before audit lockdown. Velocity stabilised at 31 story points (was hovering at 12-18). Stakeholders attending reviews for first time.
  • Mar - feedback: Mark Chen, the team's compliance officer, said in the retrospective: 'You didn't tell us what to do, but you kept asking why we couldn't do it.' That stuck with me.
  • Apr - task: Began coaching the Product team through their first backlog refinement cycle. They were bringing 40+ items to sprint planning. Introduced a three-tier acceptance criteria standard and ran refinement workshops every Tuesday.
  • Jun - achievement: Product team reduced sprint planning time from 3.5 hours to 1.5 hours. Items coming in pre-estimated. Planning meeting felt purposeful instead of exhausting for the first time in three years.
  • Jun - feedback: Sarah Okonkwo, Head of Product: 'The team's actually owning the backlog now instead of fighting us about scope.' Said this unprompted in our coaching sync.
  • Aug - task: Supported the Compliance team through a failed release (data validation step missed in Definition of Done). Ran a blameless retro instead of escalating, team identified the gap themselves.
  • Sep - achievement: Rolled out the revised DoD across both teams and added a pre-release checklist. No defects escaped into production in September or October. Compliance team confidence in their own process noticeably higher.
  • Sep - task: Started mentoring a junior Scrum Master from the Platform team. She's taking on two teams; I'm helping her navigate how to coach without directing, which is harder than it looks.
  • Nov - achievement: Facilitated a cross-team dependency mapping session. Product and Compliance identified 11 hidden blockers and built a quarterly roadmap together. Reduced the chaos in their next two sprints noticeably.
  • Dec - feedback: In the town hall, Chris Frawley from Finance said coaching has 'cut our release friction in half.' The metric I use is how often they're asking me to attend ceremonies now: fewer every month.

What makes a strong entry

What most people write: Improved team velocity and got stakeholder buy-in.

What went in the log: Compliance team moved sprint reviews to Friday mornings before audit lockdown. Velocity stabilised at 31 story points (was hovering at 12-18). Stakeholders attending reviews for first time.

The strong version names the specific constraint (audit lockdown), shows the before-and-after numbers (12-18 to 31), and includes the concrete behavioural change (stakeholders attending). Six months later, you know exactly what this win looked like.

What most people write: Worked on backlog refinement with the Product team.

What went in the log: Began coaching the Product team through their first backlog refinement cycle. They were bringing 40+ items to sprint planning. Introduced a three-tier acceptance criteria standard and ran refinement workshops every Tuesday.

The strong version specifies the problem state (40+ items, no refinement cycle), names the intervention (three-tier criteria standard, Tuesday workshops), and is concrete enough to explain what the coaching actually consisted of. A reviewer can picture what happened.

How this becomes your review in November

This year I moved two teams into sustainable iterative delivery by coaching around their actual constraints rather than imposing process. The Compliance team stabilised from chaotic 12-18 point sprints to consistent 31-point delivery once we aligned ceremonies with their audit calendar; they now own their backlog and haven't shipped defects in two months. The Product team cut sprint planning time in half by establishing a three-tier acceptance criteria standard and running weekly refinement, and I watched them move from fighting scope with stakeholders to owning their roadmap together. What matters most is that both teams are asking for my help less often, not more.

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 Agile Coach.