ACP-520 case studies
ACP-520 · Put your knowledge to work in context.
The ACP-520 credential is aimed at people who work in, lead, or support agile teams and want to demonstrate a working command of agile values, frameworks, roles, planning, delivery, stakeholder engagement, and continuous improvement. It suits scrum masters, product owners, project and delivery managers, business analysts, and team leads moving from traditional to agile ways of working, as well as practitioners who want a structured way to validate experience they have already built on the job. The exam is multiple choice and is organized around seven weighted domains: agile values and principles, frameworks and practices, team roles and responsibilities, planning and estimation, delivery and execution, stakeholder engagement and communication, and metrics and continuous improvement. Frameworks and practices carry the largest weight, so expect scenario questions that ask you to choose the most appropriate practice or response rather than recall definitions. The ACP-520 case studies are 5 cases and about 2,377 words.
1The Sprint Goal That Wasn't
A Scrum team is midway through a two-week sprint. At the sprint review, the Product Owner announces that the team did not meet the Sprint Goal, which was to 'increase checkout conversion by 2%'.
511 words, about 3 min2The Overcommitted Team
A development team has a velocity of 30 story points per two-week sprint. The Product Owner, under pressure from stakeholders, has committed the team to 45 story points for the upcoming sprint.
473 words, about 2 min3The Disengaged Stakeholder
A Scrum team is developing a new customer portal. The key stakeholder, the Head of Customer Service, has not attended any Sprint Reviews for the past three sprints.
461 words, about 2 min4The Metric That Drove the Wrong Behavior
An organization has adopted Scrum and is using velocity as a key performance indicator for teams. Management compares team velocities and rewards the team with the highest velocity each quarter.
454 words, about 2 min5The Remote Team's Communication Breakdown
A Scrum team has been fully remote for six months. Initially, they held daily stand-ups via video conference, but over time, attendance has dwindled.
478 words, about 2 min