PMI Agile Certified Practitioner (PMI-ACP)® Ultimate Cheat Sheet
Your Quick Reference Study Guide
This cheat sheet covers the core concepts, terms, and definitions you need to know for the PMI Agile Certified Practitioner (PMI-ACP)®. We've distilled the most important domains, topics, and critical details to help your exam preparation.
💡 Note: While this study guide highlights essential concepts, it's designed to complement—not replace—comprehensiv e learning materials. Use it for quick reviews, last-minute prep, or to identify areas that need deeper study before your exam.
About This Cheat Sheet: This study guide covers core concepts for PMI Agile Certified Practitioner (PMI-ACP)®. It highlights key terms, definitions, common mistakes, and frequently confused topics to support your exam preparation.
Use this as a quick reference alongside comprehensive study materials.
PMI Agile Certified Practitioner (PMI-ACP)®
Cheat Sheet •
About This Cheat Sheet: This study guide covers core concepts for PMI Agile Certified Practitioner (PMI-ACP)®. It highlights key terms, definitions, common mistakes, and frequently confused topics to support your exam preparation.
Use this as a quick reference alongside comprehensive study materials.
Mindset
28%MVP — Minimum Viable Product (Ship Core Value)
Smallest releasable product that delivers real user value to validate key assumptions fast.
Key Insight
Primary goal is validated learning about users/market — not feature completeness; release to test specific hypotheses.
Often Confused With
Common Mistakes
- Treating an MVP as low-quality or 'unfinished' rather than usable by target users.
- Equating MVP with a throwaway prototype that won't produce validated learning.
- Ignoring essential non-functional requirements (security, privacy, performance).
Safe-to-Fail Experiments (Hypothesis Probes)
Small, hypothesis-driven probes that preserve psychological safety and produce measurable learning.
Key Insight
Design small, reversible tests with clear success metrics; failures => data to update backlog, not blame.
Often Confused With
Common Mistakes
- Assuming 'safe' means reckless—skipping planning, safeguards, or risk controls.
- Scaling experiments into large, costly builds instead of low-cost probes.
- Treating a failed experiment as waste rather than validated learning to inform next steps.
Working Software over Documentation
Deliver usable product increments frequently; documentation exists only to enable value, compliance, and future work.
Key Insight
Progress = working, valuable increments + fast feedback — docs support delivery, they don't equal progress.
Often Confused With
Common Mistakes
- Interpreting the value as 'no documentation' — produce just enough for context, compliance, and handover.
- Assuming running code equals acceptable quality — tests, security, and maintainability still required.
- Shipping any working increment without stakeholder acceptance or clear value.
Tailor the Team's Process (Inspect & Adapt)
Select and adapt practices, roles, artifacts, and governance to context using short experiments, metrics, and reviews.
Key Insight
Tailoring is evidence-based: run small experiments, measure impact, keep what adds value, revert what doesn't.
Often Confused With
Common Mistakes
- Assuming tailoring always speeds delivery — unvalidated changes can add overhead or risk.
- Making ad-hoc or one-off changes without experiments, metrics, or review.
- Only changing ceremonies/artifacts while ignoring effects on roles, contracts, or compliance.
Daily Stand-up (Daily Scrum) — 15‑min Team Sync
15‑minute team sync to share progress, plans, and impediments; defer problem solving.
Key Insight
15‑min timebox for team coordination and early blocker detection — not a manager status update.
Often Confused With
Common Mistakes
- Treating the daily as a manager's status report
- Attempting to resolve impediments during the 15‑min timebox
- Assuming the 3‑question script or excluding PO/SM is mandatory
Scrum Master — Servant‑Leader, Not Boss
Servant‑leader who coaches, facilitates, and removes impediments; does not set product vision or order backlog.
Key Insight
Enables team autonomy and continuous improvement; Product Owner owns backlog and product decisions.
Often Confused With
Common Mistakes
- Assuming the Scrum Master must be the team's top technical expert
- Thinking the Scrum Master orders the backlog or decides features
- Reducing the role to meeting facilitator, not coach/impediment remover
Work Visibility — Status, Quality & Risks
Expose backlogs, boards, charts and the Definition of Done so stakeholders can inspect, adapt and plan.
Key Insight
Transparency = visible artifacts + ongoing context; artifacts alone create noise, conversations drive adaptation.
Often Confused With
Common Mistakes
- Publishing artifacts once and walking away — transparency requires continuous context.
- Hiding issues to avoid blame instead of inviting joint problem solving.
- Equating visibility with micromanagement; it's situational awareness, not time-tracking.
Agile Communication: Channel, Cadence, Purpose
Pick channel and cadence to speed feedback: synchronous for ambiguity, asynchronous for traceability and audit.
Key Insight
Match channel to intent — use live interaction for rapid clarification; use written artifacts for traceability, inclusivity and compliance.
Often Confused With
Common Mistakes
- Assuming face-to-face removes need for agreements or follow-up.
- Treating standups as manager status reports rather than quick team coordination.
- Relying on posted reports alone — no substitute for interactive clarification.
Psychological Safety (Safe, Speaking-Up Team)
A shared team climate where members take interpersonal risks, speak up, admit errors, and learn without fear.
Key Insight
It's co-created — leaders model inclusivity but everyone sustains candid, respectful challenge without blame.
Often Confused With
Common Mistakes
- Assuming only the leader owns safety — it's a team practice to sustain.
- Equating safety with 'no conflict' — that blocks candid feedback and improvement.
- Thinking one workshop fixes it — psychological safety requires ongoing actions and norms.
Feedback: Give & Receive (Actionable Loops)
Frequent, timely, two-way feedback focused on observed behaviour and clear next steps to speed learning.
Key Insight
Separate behaviour from identity (SBI/feedforward); aim for immediate, specific actions — not just evaluation.
Often Confused With
Common Mistakes
- Treating feedback as only formal or annual — in agile it must be frequent and informal too.
- Relying on automated tests as a substitute — tests don't replace customer or interpersonal feedback.
- Using feedback as appraisal only — it's for immediate improvement, not just judgment.
Value-First Backlog (WSJF · MoSCoW)
Continuously order the backlog by expected business value and cost-of-delay to deliver validated outcomes early.
Key Insight
WSJF = Cost-of-Delay ÷ Job Size — ranks urgency per effort; prioritize value trade-offs, not effort alone.
Often Confused With
Common Mistakes
- Treat WSJF as 'highest dollar value first' — it's cost-of-delay relative to size.
- Let the Product Owner prioritize in isolation — stakeholder and team input are required.
- Do backlog ordering only at planning — prioritization is continuous and re-sequenced for early feedback.
Rapid Demos & Feedback Loops
Use scheduled and ad‑hoc demos to validate increments early, gather input, and reprioritize the backlog.
Key Insight
Show thin vertical slices often — feedback validates assumptions; triage suggestions by impact before applying.
Often Confused With
Common Mistakes
- Expect demos to be polished — partial slices that test assumptions are acceptable.
- Treat every stakeholder comment as immediate scope change — assess value and cost first.
- Limit feedback to scheduled reviews — ad‑hoc channels prevent late surprises.
Iterative & Incremental Development
Deliver working product in short timeboxed iterations and additive increments; use feedback to refine scope and plans.
Key Insight
Iteration = fixed timebox; increment = shippable functionality — progressive elaboration + feedback control scope and improve estimates.
Often Confused With
Common Mistakes
- Conflating iteration (timebox) with increment (delivered functionality).
- Treating iterations as mini‑waterfalls with siloed design→build→test.
- Assuming progressive elaboration allows unlimited scope change.
Embrace Change (Backlog‑First Adaptation)
Treat change as routine: triage by backlog reprioritization, do quick impact checks, communicate decisions and record a(
Key Insight
Evaluate and gate changes — reprioritize the backlog, run quick impact checks, and keep audit trails; agile ≠ no governance.
Often Confused With
Common Mistakes
- Accepting every change immediately without impact analysis.
- Believing agile removes governance or the need for audit trails.
- Thinking cross‑skilling is a one‑step fix to absorb unlimited new work.
MVP — Minimum Viable Product (Ship Core Value)
Smallest releasable product that delivers real user value to validate key assumptions fast.
Key Insight
Primary goal is validated learning about users/market — not feature completeness; release to test specific hypotheses.
Often Confused With
Common Mistakes
- Treating an MVP as low-quality or 'unfinished' rather than usable by target users.
- Equating MVP with a throwaway prototype that won't produce validated learning.
- Ignoring essential non-functional requirements (security, privacy, performance).
Safe-to-Fail Experiments (Hypothesis Probes)
Small, hypothesis-driven probes that preserve psychological safety and produce measurable learning.
Key Insight
Design small, reversible tests with clear success metrics; failures => data to update backlog, not blame.
Often Confused With
Common Mistakes
- Assuming 'safe' means reckless—skipping planning, safeguards, or risk controls.
- Scaling experiments into large, costly builds instead of low-cost probes.
- Treating a failed experiment as waste rather than validated learning to inform next steps.
Working Software over Documentation
Deliver usable product increments frequently; documentation exists only to enable value, compliance, and future work.
Key Insight
Progress = working, valuable increments + fast feedback — docs support delivery, they don't equal progress.
Often Confused With
Common Mistakes
- Interpreting the value as 'no documentation' — produce just enough for context, compliance, and handover.
- Assuming running code equals acceptable quality — tests, security, and maintainability still required.
- Shipping any working increment without stakeholder acceptance or clear value.
Tailor the Team's Process (Inspect & Adapt)
Select and adapt practices, roles, artifacts, and governance to context using short experiments, metrics, and reviews.
Key Insight
Tailoring is evidence-based: run small experiments, measure impact, keep what adds value, revert what doesn't.
Often Confused With
Common Mistakes
- Assuming tailoring always speeds delivery — unvalidated changes can add overhead or risk.
- Making ad-hoc or one-off changes without experiments, metrics, or review.
- Only changing ceremonies/artifacts while ignoring effects on roles, contracts, or compliance.
Daily Stand-up (Daily Scrum) — 15‑min Team Sync
15‑minute team sync to share progress, plans, and impediments; defer problem solving.
Key Insight
15‑min timebox for team coordination and early blocker detection — not a manager status update.
Often Confused With
Common Mistakes
- Treating the daily as a manager's status report
- Attempting to resolve impediments during the 15‑min timebox
- Assuming the 3‑question script or excluding PO/SM is mandatory
Scrum Master — Servant‑Leader, Not Boss
Servant‑leader who coaches, facilitates, and removes impediments; does not set product vision or order backlog.
Key Insight
Enables team autonomy and continuous improvement; Product Owner owns backlog and product decisions.
Often Confused With
Common Mistakes
- Assuming the Scrum Master must be the team's top technical expert
- Thinking the Scrum Master orders the backlog or decides features
- Reducing the role to meeting facilitator, not coach/impediment remover
Work Visibility — Status, Quality & Risks
Expose backlogs, boards, charts and the Definition of Done so stakeholders can inspect, adapt and plan.
Key Insight
Transparency = visible artifacts + ongoing context; artifacts alone create noise, conversations drive adaptation.
Often Confused With
Common Mistakes
- Publishing artifacts once and walking away — transparency requires continuous context.
- Hiding issues to avoid blame instead of inviting joint problem solving.
- Equating visibility with micromanagement; it's situational awareness, not time-tracking.
Agile Communication: Channel, Cadence, Purpose
Pick channel and cadence to speed feedback: synchronous for ambiguity, asynchronous for traceability and audit.
Key Insight
Match channel to intent — use live interaction for rapid clarification; use written artifacts for traceability, inclusivity and compliance.
Often Confused With
Common Mistakes
- Assuming face-to-face removes need for agreements or follow-up.
- Treating standups as manager status reports rather than quick team coordination.
- Relying on posted reports alone — no substitute for interactive clarification.
Psychological Safety (Safe, Speaking-Up Team)
A shared team climate where members take interpersonal risks, speak up, admit errors, and learn without fear.
Key Insight
It's co-created — leaders model inclusivity but everyone sustains candid, respectful challenge without blame.
Often Confused With
Common Mistakes
- Assuming only the leader owns safety — it's a team practice to sustain.
- Equating safety with 'no conflict' — that blocks candid feedback and improvement.
- Thinking one workshop fixes it — psychological safety requires ongoing actions and norms.
Feedback: Give & Receive (Actionable Loops)
Frequent, timely, two-way feedback focused on observed behaviour and clear next steps to speed learning.
Key Insight
Separate behaviour from identity (SBI/feedforward); aim for immediate, specific actions — not just evaluation.
Often Confused With
Common Mistakes
- Treating feedback as only formal or annual — in agile it must be frequent and informal too.
- Relying on automated tests as a substitute — tests don't replace customer or interpersonal feedback.
- Using feedback as appraisal only — it's for immediate improvement, not just judgment.
Value-First Backlog (WSJF · MoSCoW)
Continuously order the backlog by expected business value and cost-of-delay to deliver validated outcomes early.
Key Insight
WSJF = Cost-of-Delay ÷ Job Size — ranks urgency per effort; prioritize value trade-offs, not effort alone.
Often Confused With
Common Mistakes
- Treat WSJF as 'highest dollar value first' — it's cost-of-delay relative to size.
- Let the Product Owner prioritize in isolation — stakeholder and team input are required.
- Do backlog ordering only at planning — prioritization is continuous and re-sequenced for early feedback.
Rapid Demos & Feedback Loops
Use scheduled and ad‑hoc demos to validate increments early, gather input, and reprioritize the backlog.
Key Insight
Show thin vertical slices often — feedback validates assumptions; triage suggestions by impact before applying.
Often Confused With
Common Mistakes
- Expect demos to be polished — partial slices that test assumptions are acceptable.
- Treat every stakeholder comment as immediate scope change — assess value and cost first.
- Limit feedback to scheduled reviews — ad‑hoc channels prevent late surprises.
Iterative & Incremental Development
Deliver working product in short timeboxed iterations and additive increments; use feedback to refine scope and plans.
Key Insight
Iteration = fixed timebox; increment = shippable functionality — progressive elaboration + feedback control scope and improve estimates.
Often Confused With
Common Mistakes
- Conflating iteration (timebox) with increment (delivered functionality).
- Treating iterations as mini‑waterfalls with siloed design→build→test.
- Assuming progressive elaboration allows unlimited scope change.
Embrace Change (Backlog‑First Adaptation)
Treat change as routine: triage by backlog reprioritization, do quick impact checks, communicate decisions and record a(
Key Insight
Evaluate and gate changes — reprioritize the backlog, run quick impact checks, and keep audit trails; agile ≠ no governance.
Often Confused With
Common Mistakes
- Accepting every change immediately without impact analysis.
- Believing agile removes governance or the need for audit trails.
- Thinking cross‑skilling is a one‑step fix to absorb unlimited new work.
Leadership
25%Self-Organizing / Self-Managing Teams
Cross-functional teams with authority to pick backlog items and execution within leader-set boundaries—drives speed and責
Key Insight
Self-organization ≠ no leader; leaders enable, set priorities/constraints, coach, and accept team decisions.
Often Confused With
Common Mistakes
- Equating emergent leadership with formal authority (titles still matter for escalation).
- Treating the Delivery Team as only coders; excluding testing, design, QA, documentation.
- Believing self-organization means no structure or accountability.
Servant Leadership — Enable, Coach, Remove Impediments
Leader supports teams by coaching, removing impediments, and aligning stakeholders to enable autonomous, accountable del
Key Insight
Servant leaders create conditions for team ownership; they guide decisions without abdicating oversight or accountability.
Often Confused With
Common Mistakes
- Assuming servant leadership removes accountability or oversight.
- Thinking the servant leader is passive and avoids decisions.
- Believing it's only for nonprofits and not applicable to product delivery.
Impediment Backlog — Visible, Prioritized Issues
Public prioritized list of impediments, risks and actions with single owners, due dates and acceptance criteria to force
Key Insight
Visibility + one named owner + measurable acceptance + verification = real accountability and resolved impediments.
Often Confused With
Common Mistakes
- Assuming it holds only long‑term risks; exclude day‑to‑day impediments.
- Assigning to a team/role without a single owner — no accountability.
- Stop at recording action items; skip follow‑up, timebox, or verification.
Five Whys — Root‑Cause Drilldown
Ask 'Why?' repeatedly to expose an actionable root cause; stop when the cause is testable and leads to improvements.
Key Insight
Not a fixed '5' ritual — iterate until an actionable, verifiable cause emerges; expect multiple contributing causes.
Often Confused With
Common Mistakes
- Insisting on exactly five 'whys' instead of stopping when root cause is reached.
- Treating Five‑Whys answers as facts without validation or evidence.
- Using it to assign blame to an individual rather than identify system/process causes.
Knowledge Flow — Tacit vs Explicit
Capture and transfer tacit + explicit knowledge via pairing, demos, lightweight docs and pragmatic KM governance.
Key Insight
Use interactive transfer (pairing, demos, mentoring) for tacit knowledge; use concise artifacts, tagging and short how‑tos for explicit knowledge.
Often Confused With
Common Mistakes
- More meetings ≠ effective transfer; measure usable outcomes, not meeting count.
- Trying to fully convert tacit knowledge into docs; use shadowing and mentoring instead.
- Assuming one repo or tool guarantees discovery/reuse; you need curation, tags and incentives.
Proximity — Co‑location vs Simulated
Place team members together or recreate proximity (overlap hours, video, shared boards) to speed tacit transfer and ramp
Key Insight
Physical co‑location speeds tacit learning and onboarding; distributed teams can capture most benefits by engineering overlap, camera‑on norms, visual
Often Confused With
Common Mistakes
- Believing co‑location is mandatory for agile success; it's situational and often costly.
- Assuming co‑location alone ensures psychological safety or high performance.
- Dismissing simulated proximity; it works when engineered (overlap, shared boards, pairing, camera‑first).
Agile Values & 12 Principles — The Decision Compass
Four values and 12 principles that steer practice choices to deliver value iteratively, get feedback, and sustain pace.
Key Insight
Values force trade-offs; principles point to fit‑for‑context practices — delivery of value ≠ automatic deployment.
Often Confused With
Common Mistakes
- Confusing continuous delivery with always deploying to production.
- Assuming self‑organizing means no leadership, direction, or accountability.
- Believing Agile means no documentation, design, or planning (only 'just enough').
ScrumMaster / Agile Coach — Enable, Don't Own
Facilitates, removes impediments, fosters psychological safety, and grows team capability via coaching and facilitation.
Key Insight
The coach's job is to enable experts and experiments: ask questions, remove blockers, and teach others to teach — not prescribe.
Often Confused With
Common Mistakes
- Being completely hands‑off and never intervening when the team is stuck.
- Trying to personally deliver all technical training instead of enabling SMEs or curating resources.
- Treating training as a one‑time event instead of ongoing coaching and follow‑up.
Product Owner (PO) — Value Decision Owner
Accountable for product vision, backlog prioritization, and maximizing value through stakeholder trade-offs.
Key Insight
PO owns WHAT and WHY (value/priorities); the team owns HOW and estimates — collaborate, don't micromanage.
Often Confused With
Common Mistakes
- Treating the PO as a 'mini project manager' — PO drives value, not project schedule control.
- Micromanaging implementation or prescribing solutions instead of collaborating with the team.
- Prioritizing only short-term business value and ignoring technical debt, security, or sustainability.
Product Vision — Align, Validate, Iterate
A concise aspirational statement that guides prioritization, aligns stakeholders, and is updated with evidence.
Key Insight
Vision creates shared commitment for decisions — you need consensus on direction, not unanimous agreement; validate and evolve it.
Often Confused With
Common Mistakes
- Expecting full agreement — aim for shared understanding and committed trade-offs, not unanimity.
- Treating the vision as a fixed deliverable or as a detailed roadmap/requirements list.
- Letting the loudest or highest-paid stakeholder override vision-based prioritization without evidence.
Retrospectives — Blameless, Timeboxed Improvement
Timeboxed, blameless reviews that reconstruct timelines, find systemic causes, and create prioritized, measurableexperi-
Key Insight
Small, timebound experiments with clear owners and metrics are the retro currency; psychological safety + causal analysis beats blame.
Often Confused With
Common Mistakes
- Treating retro cadence as fixed — change cadence when outcomes demand it.
- Expecting a single root cause — map causal chains and contributing factors.
- Running retros as chat-only — produce timebound experiments with owners and success metrics.
Conflict Modes & Group Decisions (Thomas‑Kilmann)
Classify conflict stage, apply stage‑specific interventions, and use Thomas‑Kilmann modes to resolve while protecting关系.
Key Insight
Match intervention to stage: latent → system fixes; perceived/felt → facilitated conversation; manifest → mediation or structured intervention; pick T
Often Confused With
Common Mistakes
- Equating resolution with compromise — sometimes root‑cause fixes or facilitation are better than splitting differences.
- Assuming aftermath means done — follow up for lingering trust or performance impacts.
- Defaulting to formal mediation at manifest stage — try structured facilitation first when appropriate.
Product
19%Definition of Done (DoD) — Team Quality Bar
Team-owned checklist of measurable criteria that makes a backlog item or increment potentially shippable.
Key Insight
DoD is a team-level shippability gate; acceptance criteria are item-specific — DoD sets the global quality bar.
Often Confused With
Common Mistakes
- Treating DoD as the same as an item's acceptance criteria.
- Assuming DoD is fixed and never changes.
- Believing DoD alone guarantees releasability or regulatory compliance.
Relative Sizing & Velocity (Story Points)
Use relative story points to size items, then map sizes to team velocity and sprint capacity to forecast delivery.
Key Insight
Story points = relative effort/complexity/risk; velocity is a historical, probabilistic input for forecasting, not a target.
Often Confused With
Common Mistakes
- Treating story points as hours or fixed time estimates.
- Using velocity as a performance target rather than a forecasting metric.
- Comparing story-point counts between different teams without calibration.
Kanban Method — Flow, Pull & WIP
Flow-based approach: visualize work, limit WIP, and use pull to reduce cycle time instead of fixed sprints.
Key Insight
Pull + WIP limits stabilize flow and reduce cycle time; Kanban optimizes flow, not sprint scope.
Often Confused With
Common Mistakes
- Assuming Kanban permits unlimited new work — WIP limits and policies control intake.
- Expecting WIP limits to instantly increase throughput (they improve predictability over time).
- Believing Kanban means no roles or governance — it still requires policies and ownership.
Iteration vs Increment — Timebox vs Outcome
Iteration = timeboxed cycle; increment = integrated, tested product outcome that meets the Definition of Done.
Key Insight
Iteration is the cadence; the increment is the deliverable — only DoD-compliant increments count as done.
Often Confused With
Common Mistakes
- Treating the Definition of Done as optional — a finished story doesn't equal a finished increment.
- Equating iteration with increment — a timebox is not automatically a product outcome.
- Assuming every iteration must be released to customers — release is a separate business decision.
Information Radiators — Live Work Dashboards
Visible live displays (boards + charts) that surface work, flow metrics (CFD, control, burnup) and blockers to trigger团队
Key Insight
They exist to prompt team action, not to report status — pick ~3 actionable visuals (CFD, control chart, burnup) and pair them with policies.
Often Confused With
Common Mistakes
- Equating a dashboard with a Kanban/task board.
- Cramming metrics — more metrics = more insight (creates noise).
- Using radiators as management-only status reports instead of team inspection tools.
Task Boards (Kanban) — Inclusive Planning Tool
Card-and-column boards that make flow, WIP limits, swimlanes and blockers visible for team planning, coordination and予測.
Key Insight
Boards enable lightweight, inspectable planning and predictability — they don’t remove scheduling; enforce explicit policies, WIP limits, and classes‑
Often Confused With
Common Mistakes
- Assuming the board replaces conversations — it augments, not replaces, coordination.
- Believing Gantt is always superior; boards can support planning, forecasting and control with WIP and metrics.
- Thinking a Kanban board enforces discipline without explicit policies or team agreements.
Value-Driven Delivery (Measure, Prioritize, Realize)
Prioritize and deliver small testable increments tied to measurable success criteria and a benefit owner.
Key Insight
Every increment must map to a measurable benefit and an assigned owner — value continues after handoff via governance.
Often Confused With
Common Mistakes
- Relying only on financial KPIs and ignoring qualitative or operational indicators.
- Assuming bigger, less frequent releases automatically deliver more value.
- Stopping measurement at handoff instead of assigning owners and governing benefits.
Lean Flow & Waste Elimination
Map end-to-end flow, limit WIP, remove bottlenecks and shorten feedback to deliver continuous, usable increments.
Key Insight
Lean optimizes flow and customer value — minimize unnecessary batch size and delays, not just cut cost.
Often Confused With
Common Mistakes
- Treating Lean as headcount or budget cuts instead of flow/value improvement.
- Believing Lean only applies to manufacturing, not knowledge work or software.
- Expecting zero batching; ignoring practical trade-offs and necessary batching.
Delivery
28%Rapid Review Cadence
Short, regular demos/checkpoints of small increments to validate direction and gather actionable feedback.
Key Insight
Small, frequent demos catch misalignment and risks faster than big releases—use partial increments to steer early.
Often Confused With
Common Mistakes
- Assuming more reviews always add bureaucracy—timebox and focus outcomes, not length.
- Treating reviews as a substitute for QA/testing; reviews give feedback, tests give quality evidence.
- Waiting for 'finished' features before demoing; partial slices produce earlier, usable feedback.
Empowered Stakeholders (Engage & Enable)
Identify and enable decision-makers, clarify decision rights, and run continuous engagement and feedback governance.
Key Insight
Authority + access beats status updates—empowered stakeholders with clear decision rights shorten feedback loops.
Often Confused With
Common Mistakes
- Relying only on the Product Owner to liaise; whole-team stakeholder contact prevents single-point bottlenecks.
- Assuming tools/docs alone create engagement—psychological safety and removed impediments are required.
- Treating engagement as a one-time kickoff or passive updates instead of ongoing, two-way governance.
Cycle Time — Start-to-Finish Flow Clock
Elapsed time from when work starts to when it’s done; key to finding bottlenecks and forecasting flow.
Key Insight
Cycle time excludes backlog wait (that’s lead time); use percentiles/variation, not just the mean, to predict delivery.
Often Confused With
Common Mistakes
- Confusing cycle time with lead time — cycle excludes pre-start waiting.
- Assuming shorter cycle time always means higher team or individual productivity.
- Reporting only the average cycle time and ignoring distribution/tail percentiles.
Burndown vs Burnup — Remaining vs Scope
Burndown shows remaining work over time; burnup shows cumulative done vs scope to reveal scope churn and progress.
Key Insight
Burndown masks scope changes; burnup separates completed work from scope changes—use burnup when scope varies or you need scope history.
Often Confused With
Common Mistakes
- Treating burndown and burnup as identical — they answer different questions.
- Interpreting a steep/smooth burndown as definitive proof of high productivity (ignores rework/scope removal).
- Forcing story points as the only unit — charts can validly use hours, counts, or points.
Small Releasable Increments (Thin Slices)
Deliver thin, customer-visible slices often to validate assumptions, gather feedback, and limit exposure to big failures
Key Insight
An increment is a thin, testable, customer-visible slice (MVI/MVP) for learning—not necessarily full feature completeness
Often Confused With
Common Mistakes
- Treating an increment as a full-feature release; ignoring thin, testable slices
- Confusing increments with individual tasks or developer work units (not customer-visible)
- Assuming frequent delivery eliminates all risk or automatically shortens the schedule
Agile Risk Management (Backlog-Driven)
Continuously identify, assess, prioritize, and respond to risks; convert responses into backlog items and experiments
Key Insight
Prioritize by exposure (impact × likelihood) and turn responses into small experiments/stories to implement, monitor, and adapt
Often Confused With
Common Mistakes
- Skipping risk work because iterations are short—risk still exists
- Designing only large upfront responses; neglect lightweight experiments/backlog items
- Leaving risk identification/response solely to the PM; the whole team must own it
Kaizen Loop — PDCA/PDSA Process Improvement
Team-led, hypothesis-driven short experiments (retrospectives + PDCA/PDSA) to remove waste and measure impact.
Key Insight
Turn feedback into validated change: run short PDCA cycles with clear hypotheses and measurable success criteria.
Often Confused With
Common Mistakes
- Treating feedback as opinion—no hypothesis or metric to validate change.
- Assuming Kaizen is only cosmetic tweaks; ignoring measurable improvements.
- Running PDCA once as a checklist instead of repeating short cycles.
Team Velocity — Forecasting, Not a Productivity Badge
Iteration-level measure of delivered work used for forecasting; adjust for refactors, maintenance, scope and shared time
Key Insight
Velocity is a team-specific forecast metric affected by refactor/maintenance and shared resources—don’t compare teams directly.
Often Confused With
Common Mistakes
- Dropping refactor/maintenance because it 'doesn't count' as work.
- Treating higher velocity as inherently better despite quality or scope changes.
- Prorating part-time/shared resources as if full-time capacity remains unchanged.
Inspect–Adapt–Improve (Learning Cycle — PDCA ↔ ASD)
Iterative Plan/Speculate → Build → Evaluate → Learn loop each iteration; maps to PDCA/ASD to pick the right improvement.
Key Insight
Not identical to PDCA — favor just‑enough planning and rapid inspect→adapt each iteration to improve outcomes, not blame.
Often Confused With
Common Mistakes
- Treating it as identical to PDCA instead of an agile‑focused variant.
- Using the cycle to blame individuals rather than iterating processes/outcomes.
- Equating 'Learn' with a single retrospective or waiting until project end.
Sprint Retrospective — Inspect, Decide, Improve
Timeboxed end-of-sprint team meeting to inspect how the sprint went, agree measurable improvements, assign owners, and跟进
Key Insight
Whole‑team event (not a demo) for process improvement — every action must have an owner, a measure, and follow‑up next sprint.
Often Confused With
Common Mistakes
- Confusing the retrospective with the Sprint Review (product demo).
- Leaving action items vague or ownerless with no success measures.
- Skipping it when a sprint 'went well' or treating it as only the Scrum Master's duty.
Customer Collab > Contracts
Prioritize continuous customer engagement and negotiated trade-offs over rigid contracts to shorten feedback loops.
Key Insight
Use lightweight, flexible agreements that allow iterative scope changes — contracts should enable collaboration, not block it.
Often Confused With
Common Mistakes
- Thinking contracts must be discarded — instead use flexible agreements that permit change.
- Assuming the customer dictates every decision — aim for negotiated trade-offs and shared ownership.
- Expecting the customer to be co‑located constantly — schedule frequent, timely feedback instead.
Personas — Composite User Archetypes
Research-based fictional user archetypes used to prioritize features, drive acceptance criteria, and validate value.
Key Insight
Personas are data-informed composites that direct prioritization and tests; keep them updated with research and metrics.
Often Confused With
Common Mistakes
- Treating personas as single real users — they're composite, research-backed archetypes.
- Using one persona for all users — create distinct personas for different behaviors/needs.
- Letting personas go stale — refresh them with new research, analytics, and feedback.
WIP Limits (Work‑in‑Progress)
Cap active items to reduce multitasking and queues; enable pull flow and make bottlenecks visible.
Key Insight
Limit concurrency to expose queues — WIP is a visibility/pull control, not a delivery quota.
Often Confused With
Common Mistakes
- Treating WIP as a delivery quota instead of an in‑progress cap.
- Thinking WIP is only for Kanban; Scrum/XP teams can use it too.
- Believing lower WIP always speeds delivery — too low can cause idle time.
Bottlenecks & Theory of Constraints (TOC)
Detect the system constraint with flow metrics/visuals and target it to improve end‑to‑end throughput.
Key Insight
Only relieving the current constraint raises system throughput — local improvements outside it don't help.
Often Confused With
Common Mistakes
- Assuming bottlenecks are fixed and won't shift after changes.
- Adding people or more WIP at a constrained stage will always fix it.
- Mixing up lead time vs cycle time — request→delivery vs active work.
Certification Overview
Cheat Sheet Content
Similar Cheat Sheets
- PMI Certified Associate in Project Management (CAPM)® Cheat Sheet
- PMI Professional in Business Analysis (PMI-PBA)® Cheat Sheet
- Google Cloud Certified Generative AI Leader Cheat Sheet
- PMI Construction Professional (PMI-CP)™ Cheat Sheet
- Project Management Institute Portfolio Management Professional (PfMP)® Examination Cheat Sheet
- IAPP Certified Information Privacy Manager (CIPM) Cheat Sheet