The PMI Agile Certified Practitioner (PMI-ACP)® certification goes beyond theory by testing a candidate’s knowledge of the practical tools and techniques used in agile environments. These tools are essential for planning, collaboration, estimation, tracking, quality management, and continuous improvement — all of which are critical to agile success.
This article covers the most commonly tested agile tools and techniques that appear on the PMI-ACP exam and are regularly used in agile project delivery.
1. User Stories
Purpose: To capture customer-centric requirements in a simple, conversational format.
Format:
“As a [user], I want [goal] so that [benefit].”
Why it matters:
User stories promote collaboration, support incremental development, and are foundational to backlog creation and sprint planning.
2. Product and Sprint Backlogs
Product Backlog: A prioritized list of features, enhancements, and fixes maintained by the Product Owner.
Sprint Backlog: A subset of the product backlog selected for delivery during a sprint.
Why it matters:
Backlogs are the central planning and prioritization tools in Scrum and many other agile frameworks.
3. Planning Poker
Purpose: Team-based estimation using story points.
How it works:
Each team member selects a card (e.g., from the Fibonacci sequence) based on their effort estimate. Estimates are revealed simultaneously, and differences are discussed.
Why it matters:
Encourages consensus, promotes discussion, and reduces bias in estimation.
4. Kanban Boards
Purpose: To visualize workflow, limit work in progress (WIP), and optimize flow.
Structure:
Columns represent work states (e.g., To Do, In Progress, Done). Tasks move left to right.
Why it matters:
Kanban supports continuous delivery, improves transparency, and highlights bottlenecks.
5. Burnup and Burndown Charts
Burndown Chart: Tracks the remaining work in a sprint or release.
Burnup Chart: Tracks completed work against total scope.
Why it matters:
These charts help teams monitor progress, velocity, and scope changes over time.
6. Information Radiators
Definition: Visible displays of key project data in a shared space.
Examples: Task boards, cumulative flow diagrams, test results, team calendars.
Why it matters:
Promotes transparency, enables quick decision-making, and keeps everyone aligned.
7. Definition of Done (DoD)
Purpose: A shared understanding of what it means for work to be “done.”
Includes:
Code completed, reviewed, tested, documented, and accepted.
Why it matters:
Prevents ambiguity, ensures quality, and sets clear team expectations.
8. Velocity Tracking
Definition: The number of story points or work units completed in a sprint.
Use: To forecast future sprint capacity and support release planning.
Why it matters:
Provides a historical measure of team performance and helps with agile planning.
9. Retrospectives
Purpose: To reflect on what went well, what didn’t, and how the team can improve.
When used: At the end of each iteration (e.g., sprint retrospective in Scrum).
Why it matters:
Supports continuous improvement, promotes psychological safety, and strengthens team collaboration.
10. Test-Driven Development (TDD)
Definition: Writing tests before writing the code that will fulfill them.
Cycle:
Write test → Write code → Run test → Refactor
Why it matters:
Improves code quality, reduces defects, and supports sustainable development.
11. Story Mapping
Purpose: Visualizes the user journey and how features support user goals.
Structure:
High-level activities (top) with user stories (bottom) arranged by priority and workflow.
Why it matters:
Helps with backlog organization, MVP planning, and stakeholder communication.
12. Root Cause Analysis (e.g., 5 Whys, Fishbone Diagram)
Purpose: Identify the true cause of a defect or problem rather than treating symptoms.
Why it matters:
Supports continuous improvement and problem-solving in agile teams.
13. Pair Programming
Definition: Two developers work together at one workstation — one codes, the other reviews.
Why it matters:
Promotes knowledge sharing, reduces bugs, and improves collaboration.
14. MoSCoW Prioritization
Categories:
- Must Have
- Should Have
- Could Have
- Won’t Have (this time)
Why it matters:
Used in time-boxed development to prioritize features based on value and necessity.
Conclusion
The PMI-ACP exam emphasizes practical knowledge of agile tools and techniques that drive successful delivery in fast-paced environments. By mastering these core practices — from estimation and tracking to quality assurance and team collaboration — you’ll be better equipped to both pass the exam and lead effective agile initiatives.
In your preparation, aim to not just memorize these tools but understand how and when to apply them. The PMI-ACP exam will test your ability to think in context, just as agile projects do in real life.