Entry-level Scrum Master resume example

• With a senior colleague reviewing the change, facilitated Scrum sprint planning using Jira capacity, dependencies, and a clear sprint goal; coached the team to split unfinished work into testable increments rather than rolling every ticket forward.
• Within an assigned workstream, used Agile retrospectives to trace repeated blocked work and agree one improvement with an owner; checked the next sprint for changed behavior instead of counting how many retrospective actions were created.
• Within the assigned scope, used cycle-time distributions and blocked-ticket history to prepare retrospectives, agreed a smaller work-in-progress limit, and checked whether the next sprint actually reduced waiting time.
• Within the assigned scope, owned a Scrum dependency review using Jira blocker history, resolved missing acceptance criteria and completed sprint planning with named decision owners.
• Within the assigned scope, designed retrospective coaching using delivery evidence, reduced carried-over items from 15 to 6 across three sprints without increasing the team’s capacity assumption.

• The team introduced cross-team dependency reviews for 23 shared milestones; my scope was data preparation, quality checks, and follow-up documentation under senior review. The team completed the rollout against the approved acceptance criteria; documented my assigned work separately from the team result and confirmed it with a senior colleague.
• Within the assigned scope, reviewed a delivered feature against acceptance criteria with design and engineering, documented the unresolved usability issue, and agreed whether it should block release or enter the next iteration.
• Within the assigned scope, traced a late scope request to the underlying user need, compared it with the agreed release goal, and worked with delivery partners to split required behavior from a follow-up enhancement. Updated acceptance criteria before development continued.

• Within the assigned scope, the team facilitated 11 root-cause retrospectives with owned follow-up experiments; my scope was data preparation, quality checks, and follow-up documentation under senior review
• Used a public product workflow to map the user problem, decision points and acceptance criteria; marked assumptions separately from observed behavior and prioritized an experiment before specifying a complete redesign.
• Prepared a decision log showing alternatives, dependencies and the metric that would reverse the recommendation; walked through an exception path and updated the acceptance criteria when ownership was unclear.
• Owned the independent prototype review using task-based acceptance criteria, resolved an ambiguous exception path and completed a test plan with an explicit stopping rule.

Relevant coursework: Financial accounting, statistics, operations management, organizational behavior

• Published a personal product case study using the project decision log, explaining rejected alternatives, testable assumptions and the evidence needed before a production launch.