When are deliverables accepted or not accepted? ISEB ISEB-PM1 Exam

Question

Options

• AWhen the project is initiated.
• BAs an output of the scope verification process.
• CWhen the project is closing.
• DIn the contract closure process.

• A
  4% (2)
• B
  78% (35)
• C
  7% (3)
• D
  11% (5)

Explanation

Deliverables are formally accepted or rejected as an output of the scope verification process (also called "Validate Scope" in modern PM frameworks). This is the structured process where stakeholders review completed work against the agreed scope baseline and make a formal decision to accept or reject each deliverable, producing documented acceptance decisions as output.

Why the distractors are wrong:

• A (Project initiation): Deliverables haven't been created yet at initiation - the project is just being defined and authorized.
• C (Project closing): Closing assumes deliverables are already accepted; you can't close a project without prior formal acceptance having occurred.
• D (Contract closure): Contract closure is an administrative process for closing out procurement agreements, not the mechanism for accepting deliverables.

Memory tip: Think of scope verification as the "inspection checkpoint" - it's the formal gate where the customer/stakeholder looks at what was built and signs off (or rejects it). Associate it with the phrase "verify → accept or reject" and you'll never confuse it with closing, which is purely administrative wrap-up.

No community discussion yet for this question.