Chapter 22: Closing a project

Question 1

Purpose of closing a project

Answer 1

Confirm acceptance of project product, recognize achievement of objectives, or acknowledge end of project.

Question 2

PRINCE2 feature of project closure

Answer 2

PRINCE2 projects are finite with clear start and end points.

Question 3

Key aspects of a successful project closure

Answer 3

Confirm objectives met, operational regime takes over, project management team disbanded, costs cease, transfer ownership.

Question 4

Closure activities planning

Answer 4

Closure should be part of the final stage plan and include preparation for closure authorization.

Question 5

Premature project closure

Answer 5

Can occur if business case becomes invalid, requires tailored closure process.

Question 6

Agile project closure in mature environments

Answer 6

Frequent handovers and iterative nature reduce need for formal closure activities.

Question 7

PRINCE2 Agile guidance for closure

Answer 7

Closure may involve workshops, reviews of final release, ongoing evaluation, and formal acceptance processes.

Question 8

Agile maturity impact on closure

Answer 8

Frequent releases and continuous user acceptance make final handover routine.

Question 9

Key closure activities in PRINCE2 Agile

Answer 9

Prepare for closure, hand over products, evaluate project, recommend closure, close logs and registers.

Question 10

PRINCE2 Agile closure examples

Answer 10

Workshops with stakeholders, review of project vision and final product, check baseline against outcomes.

Question 11

Premature closure triggers in agile

Answer 11

Caused by fail-fast approach, transparency, timeboxing, and regular retrospectives.

Question 12

Agile techniques for fail-fast

Answer 12

Empirical forecasting, timeboxing, sprint demos, early customer feedback, prototyping.

Question 13

PRINCE2 Agile closure summary

Answer 13

Agile allows for smoother, more efficient closure with minimal effort due to iterative nature of work.