Delivery

In the Delivery domain, PMP cares about whether the team can deliver usable valuein agreed increments, meet acceptance criteria, and handle changes through a disciplined process.

What to master

• Definition of Done vs. Acceptance Criteria
• Incremental delivery and verification/validation
• Change control (when to raise a CR, who approves, baselines)
• Tailoring delivery cadence (predictive / agile / hybrid)
• Done-but-not-accepted vs. blocked work — how to resolve

Start here

• PMP Change Request Flow — quick visual & traps
• PMP Exam-Day Strategy — time boxes, flag & move, review
• PMP Formulas You Must Know — earned value & forecasts

Delivery pitfalls on the exam

• Shipping a feature that doesn’t match acceptance criteria is not “done”. Re-plan or raise a change — don’t bypass control.
• “Stakeholder asked for this” ≠ approved change. Use the formal CR flow.
• In hybrid, keep the predictive baselines but deliver increments with agile ceremonies — be explicit about which rules apply.

See also (related study posts)

• How to Apply for PMP — application checklist
• ITTO Patterns for PMP — how to reason, not memorize
• Agile vs Predictive vs Hybrid — real examples

Exam-day checklist

• Re-read acceptance criteria for the increment in the scenario
• Confirm if a change needs a formal CR → route to CCB
• State how “Done” is verified and validated (by whom, when)