Project Closure

• Topic 01

  Formal Project Closure Processes and Checklists

  15 questions
• Topic 02

  Contract Closure and Procurement Finalization

  15 questions
• Topic 03

  Lessons Learned Capture and Storage

  15 questions
• Topic 04

  Transition and Handover to Operations

  15 questions
• Topic 05

  Post-Implementation Review and Benefits Tracking

  15 questions

A few questions from this unit, with the answer and a full explanation. The complete bank is available when you start practising.

1. An agile project delivers features incrementally. How should benefits be tracked in this delivery model?

   • A
     Benefits should be tracked exclusively by the product owner during sprint planning.
   • B
     Benefits should be tracked after each release to assess whether released features deliver the expected business value, using analytics, feedback, or A/B testing.
     Correct answer
   • C
     Benefits tracking is not applicable to agile projects because value is delivered continuously.
   • D
     Benefits tracking in agile is performed by the PMO annually regardless of release frequency.
   Explanation

   In agile projects, continuous delivery enables incremental benefits tracking after each release. The product owner and benefits owner can use usage analytics, customer feedback, A/B testing, or business metrics to assess whether each release is delivering expected value. This makes benefits tracking more frequent and measurable than in traditional projects, not less. PMI guidance (Agile Practice Guide) and the PMBOK 7th edition both emphasise that agile delivery does not eliminate the need for benefits tracking; it makes it more granular.

2. At project closure, the lessons learned register is transferred to which organisational asset?

   • A
     The project charter
   • B
     The quality management system
   • C
     The risk register
   • D
     The lessons learned repository (organisational process asset)
     Correct answer
   Explanation

   At project closure, the lessons learned register — a project document updated throughout the project — is transferred into the lessons learned repository, which is an Organisational Process Asset (OPA). This repository is maintained by the organisation (often the PMO) and accumulates lessons from all past projects so future project teams can consult it during planning. The lessons learned register itself is an input to the Close Project or Phase process, and the OPA update is the output.

3. Which of the following is the primary purpose of the stabilisation period after a handover?

   • A
     To allow the operations team to request additional scope changes before formal acceptance.
   • B
     To provide enhanced project team support to the operations team while they become fully self-sufficient with the new deliverable.
     Correct answer
   • C
     To train end users who were not trained before the handover.
   • D
     To complete any outstanding project scope items that were deferred from the main delivery.
   Explanation

   The stabilisation period (also called 'hypercare') is a defined post-go-live period during which the project team provides enhanced support to the operations team as they take ownership of the new deliverable. It allows issues to be resolved quickly using project team expertise that is still available. At the end of the stabilisation period, full operational ownership transfers and the project team is released. It is not a period for additional scope changes, deferred work, or activities that should have been completed before go-live.