ACP-520 study guide
ACP-520 · Work through your exam, one topic at a time.
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 ACP-520 study guide has 7 sections and about 2,242 words.
01Agile Values and Principles
Candidates must be able to map behaviors and decisions back to the four value statements and twelve principles. The values are comparative, not absolute: working software is valued over comprehensive documentation, but documentation is not forbidden.
350 words, about 2 min02Agile Frameworks and Practices
Know the structure and events of the most common frameworks. Scrum : three roles (Product Owner, Scrum Master, Developers), five events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Retrospective), three artifacts (Product Backlog, Sprint Backlog, Increment) with commitments (Product Goal, Sprint Goal, Definition of Done).
346 words, about 2 min03Agile Team Roles and Responsibilities
Understand accountability boundaries in Scrum and general Agile teams. Product Owner (PO): maximizes value; owns and orders the Product Backlog; defines and communicates the Product Goal; is one person, not a committee; makes prioritization decisions.
320 words, about 2 min04Agile Planning and Estimation
Agile planning is iterative and emergent, not a single upfront event. Know rolling-wave planning , release planning , Sprint Planning , and backlog refinement .
328 words, about 2 min05Agile Project Delivery and Execution
Delivery is about producing a potentially releasable Increment each Sprint and adapting continuously. Key concepts: the Definition of Done (shared quality bar), continuous integration/delivery , incremental delivery , backlog refinement , and impediment removal .
319 words, about 2 min06Stakeholder Engagement and Communication
Agile communication is frequent, transparent, and face-to-face where possible. Know the stakeholder map (power/interest), information radiators (visible boards, burn-down/burn-up charts), and feedback loops (Sprint Review, demos, user testing).
287 words, about 1 min07Agile Metrics and Continuous Improvement
Metrics should inform improvement, not judge individuals. Know velocity (forecasting), burn-down (work remaining vs.
292 words, about 1 min