Introduction
Project closure reports provide visibility of how digital and ICT-enabled projects are performing in realising the scope and benefits as agreed and funded by government.
Project closure reports also provide the opportunity to:
- acknowledge project achievements and outcomes
- better prepare agencies to deliver future digital projects by capturing the successes and failures of a completed project
- record key lessons which could improve the performance of other in-flight and future projects.
This standard aims to:
- guide closure reporting practices
- ensure closure reports for Australian Government digital and ICT-enabled projects consistently include a minimum set of information.
How to use this Standard
Agencies should self-assess their draft project closure reports against each of the below criteria.
Agencies should aim to be strongly aligned with all 7 criteria prior to finalising their project closure reports.
Agencies may use their own closure report templates or use the project closure reporting templates that have been developed by the DTA to align to the Standard.
Criteria:
- The project has recorded project performance against the agreed scope outlined in the Business Case (or equivalent).
- The project has recorded project performance against the agreed schedule outlined in the Business Case (or equivalent).
- The project has recorded achievement of outcomes and measured benefits realisation against their benefits management plan.
- The project has recorded project performance against the agreed budget outlined in the Business Case (or equivalent).
- The project has recorded the completion of assurance activities as per the agreed Assurance Plan with the DTA.
- The project has detailed fit-for-purpose transition arrangements in preparation for a shift to a business-as-usual environment.
- The project has documented key lessons learned and how the lessons will be applied to in-flight and future projects for the agency and the Australian Government.