Revision as of 21:59, 4 December 2013 by DominiGee (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Closure is the end of the project.

Rationale: This is important because it asks what determines the end of the project and how do you wrap it up. Closure asks you to reflect on your results and how you will communicate these to the other parties once the project is over.

Once you've successfully planned and executed your project, the next question is how will you know when it's finished? Closure prepares you to wrap up the project. You need to consider what the end-state should look like and when to communicate to interested parties that the project is over, so you don't have unnecessary activity long past the end of the project.


  • 8.1 What will the end-state of the project look like?
  • 8.2 Does the game meet its goals? How do you know that?
  • 8.3 How will you know if stakeholders are satisfied?
  • 8.4 Have you communicated to all interested parties that the project is over?

Recommended Methods :

  • Charters
  • Interviewing
  • Success/Failure Counters: Success/Failure relies on measurable factors. If you have a set success goal, such as 'twenty users need to complete the game', then counters are a useful determinant of success.
Personal tools