Agile Metrics, Change and Risk
This topic covers agile metrics, impediments, inspection, adaptation, minimum viable products, spikes, customer feedback, and iterative delivery risk management.
How to study for CAPM
Treat each CAPM item as a project situation: identify the delivery approach, stakeholder need, artifact, team behavior, and value outcome before choosing.
Core concepts
Concept 1
Agile Metrics, Change and Risk questions test whether an entry-level project practitioner can choose the right artifact, behavior, or delivery approach for the situation.
Exam cue: Identify whether the scenario is predictive, adaptive, hybrid, business analysis, or general project management fundamentals.
Concept 2
The best CAPM answer usually protects value delivery, stakeholder clarity, team collaboration, and transparent control of work.
Exam cue: Match the artifact or action to the need: define, plan, communicate, estimate, control, inspect, adapt, validate, or realize value.
Concept 3
Eliminate answers that skip planning, ignore stakeholders, hide risks, resist adaptive feedback, or confuse project management with ongoing operations.
Exam cue: Prefer ethical behavior, collaboration, visible information, controlled change, and delivery of useful outcomes.
Risk pitfalls and guardrails
Choosing a document or meeting before identifying the project problem it is meant to solve.
Guardrail: Avoid answers that skip stakeholders, hide risks, ignore change control, reject feedback, or deliver outputs without validating value.
Treating agile change as uncontrolled work or predictive change as informal preference.
Guardrail: Avoid answers that skip stakeholders, hide risks, ignore change control, reject feedback, or deliver outputs without validating value.
Ignoring business value, acceptance criteria, stakeholder needs, or benefits after deliverables are produced.
Guardrail: Avoid answers that skip stakeholders, hide risks, ignore change control, reject feedback, or deliver outputs without validating value.
Memory anchors
Burndown Chart
A burndown chart shows remaining work over time in an iteration or release.
Burnup Chart
A burnup chart shows completed work and total scope over time.
Cumulative Flow
A cumulative flow diagram shows work across workflow states to reveal bottlenecks.
Impediment
An impediment is anything that blocks or slows the team from achieving its goal.
Retrospective Action
A retrospective action is a selected improvement the team commits to try next.
Adaptive Change
Adaptive change is expected and managed through backlog refinement, prioritization, and feedback.
MVP
A minimum viable product tests value with the smallest useful solution increment.
Risk Spike
A spike investigates uncertainty so the team can make a better delivery decision.
Customer Feedback
Customer feedback validates whether increments solve the right problem.
Iterative Delivery
Iterative delivery uses repeated cycles to inspect, learn, and improve the solution.
Checkpoint rule
Do the check-up only after you can summarize each concept in one sentence and identify one dangerous pitfall from memory.
Knowledge Check (after reading)
Short check-up to confirm understanding of this module.
Check-up Questions
A burndown chart's remaining-work line is flat for five days. What does it indicate?
Why can a burnup chart make scope change more visible than a simple burndown?
Answer all questions to submit.
Next step personalized recommendations
Continue learning
Move forward only after this module is stable.
What is Pass Harbor?
Completely free exam prep for 317 U.S. exams.
- Practice questions
- Flashcards
- Study guides
- Mock exams
- No registration
- No paywall
- Start instantly
“No more expensive exam prep. Quality study tools should be accessible to everyone.”