Agile Project Management
Agile Project Management Cheat Sheet
Agile PM Is About Value Delivery Decisions, Not Ceremony Compliance
Most candidates fail by applying rigid waterfall structure to agile scenarios or performing agile rituals without understanding their purpose.
Check Your Readiness →
Among the harder certs
Avg: Approximately 65–70%
Pass: 750 / 1000
Most candidates understand Agile Project Management concepts — and still fail. This exam tests how you apply knowledge under pressure.
Core Framework
Agile Value Delivery Framework
Agile PM exams test the Agile Manifesto, its 12 principles, and practical application in project scenarios. The right answer always prioritizes delivering customer value over process compliance.
-
01
Individuals & Interactions over processes and tools
-
02
Working Software over comprehensive documentation
-
03
Customer Collaboration over contract negotiation
-
04
Responding to Change over following a plan
-
05
Incremental delivery
— deliver value in small, frequent batches
-
06
Inspect & Adapt
— use retrospectives to continuously improve
Scenario Traps
Wrong instinct vs correct approach
A customer requests a significant new feature during an active sprint
✕ Wrong instinct
Add it to the sprint since the customer is always the priority
✓ Correct approach
Add it to the product backlog, have the PO prioritize it for a future sprint, and protect the current sprint's commitment
The team consistently delivers all sprint items but the customer isn't satisfied
✕ Wrong instinct
Increase sprint capacity or add more features per sprint
✓ Correct approach
Inspect and adapt: involve the customer earlier in backlog refinement to ensure the right items are being built — the sprint review should surface the value gap
Two team members have a serious conflict that's disrupting the sprint
✕ Wrong instinct
The project manager resolves the conflict for them
✓ Correct approach
In agile, the team self-organizes to resolve conflict; the Scrum Master/agile coach facilitates the conversation but the team owns the resolution
Quick Rules
Know these cold
-
▸
Working software is the primary measure of progress — not documents
-
▸
Backlog changes are welcome — but they go into the backlog, not the active sprint
-
▸
Velocity is a planning tool, not a performance benchmark
-
▸
The Product Owner maximizes value — trust the PO's prioritization decisions
-
▸
Retrospectives are for process improvement — always result in at least one action
-
▸
Daily standups are for the team — not for management status reporting
-
▸
Done means potentially releasable — not code complete
Self Check
Can you answer these without checking your notes?
In this scenario: "A customer requests a significant new feature during an active sprint" — what should you do first?
Add it to the product backlog, have the PO prioritize it for a future sprint, and protect the current sprint's commitment
In this scenario: "The team consistently delivers all sprint items but the customer isn't satisfied" — what should you do first?
Inspect and adapt: involve the customer earlier in backlog refinement to ensure the right items are being built — the sprint review should surface the value gap
In this scenario: "Two team members have a serious conflict that's disrupting the sprint" — what should you do first?
In agile, the team self-organizes to resolve conflict; the Scrum Master/agile coach facilitates the conversation but the team owns the resolution
Failure Patterns
Common Exam Mistakes — What candidates get wrong
Treating agile ceremonies as mandatory bureaucracy
Agile ceremonies have a purpose — if the purpose isn't being served, adapt. Candidates select 'hold the ceremony as scheduled' when the correct answer is to adapt the process to serve the team's needs.
Allowing scope changes without re-prioritizing the backlog
Agile welcomes change — but changes enter the backlog and are prioritized by value, not added to the current iteration. Adding scope mid-sprint without backlog management is anti-agile.
Confusing velocity with productivity
Velocity measures how much work a team completes per sprint — it's a planning tool, not a performance metric. Using velocity to compare teams or pressure performance is a misapplication.
Measuring success by sprint completion rate instead of business value
Completing 100% of sprint tasks that don't deliver customer value is a failure. The correct success metric is customer satisfaction and value delivered.
Underestimating the Product Owner's decision authority
The Product Owner owns the backlog and prioritizes value. The team cannot override PO prioritization decisions. Candidates who escalate to management when disagreeing with PO priority are applying waterfall governance.
Are you doing agile or being agile? Test whether your instincts match the Manifesto.