EXIN Agile Scrum Master case studies
EXIN Agile Scrum Master · Put your knowledge to work in context.
The EXIN Agile Scrum Master (ASM) credential is a vendor-neutral certification offered by EXIN, an independent certification body. It is aimed at Scrum Masters, aspiring Scrum Masters, project managers moving into Agile delivery, team leads and consultants who facilitate Scrum teams and want to demonstrate that they can apply Scrum in practice rather than merely recite definitions. The EXIN Agile Scrum Master case studies are 5 cases and about 4,651 words.
1Aligning a regulated release window with Sprint length
Meridian Pay is a regulated payments company running two-week Sprints across four Scrum Teams. Marketing commits campaign launches to retailers with three-week notice, and the compliance team requires a signed-off release package at least five working days before any customer-facing change goes live.
879 words, about 4 min2A Product Owner in name only
Northwind Logistics has six developers, a QA engineer and a part-time Scrum Master working in three-week Sprints on an internal route-optimisation platform. The Product Owner is also Head of Operations and attends roughly one hour per week; day-to-day product decisions are made by a senior business analyst who is not the Product Owner and who has no authority over budget or priority.
880 words, about 4 min3When "Done" is not releasable
A ten-person team building a public-facing booking engine has a Definition of Done that lists code review, unit tests and deployment to staging. Load testing, accessibility checks and security scanning happen in a separate "hardening Sprint" every fourth Sprint, run by a different team.
952 words, about 5 min4The Scrum Master as coordinator, and a retrospective that repeats itself
A newly appointed Scrum Master takes over a team of seven in a company that recently renamed its project managers to Scrum Masters. In her first three weeks she is copied on 30 emails a day asking her to update a Gantt chart, approve leave, and chase test environments.
971 words, about 5 min5Scaling decisions while the basics are still missing
Four months into an Agile adoption, an insurer has five Scrum Teams: three feature teams on the claims platform, one shared services team that all three depend on, and one team maintaining a legacy policy system. All teams use two-week Sprints and story points, but refinement maturity differs sharply: the claims teams have about two Sprints of refined backlog; the shared services team has a three-week intake queue with a product owner who reports to the infrastructure directorate and takes work from all three claims teams plus two projects outside the adoption.
969 words, about 5 min