where the Gate is integrated with the ICT Investment Approval/Two Stage processes ensure that the review supports development of the first pass business case; check that financing has been adequately assessed for the project; and check that the project is realistic, properly resourced and has authorised work plans through to the next stage of the project. Project Documentation Required for the Business Need Review To undertake the review, the review team may require access to: the NPP or Cabinet Submission/Decision; the entity’s Portfolio Budget Statement, business plan or equivalent documents. These documents should set out the entity’s outcomes and outputs, strategic direction, high level aims and objectives; a project brief that provides information about: objectives—a high-level description of the purposes, outcomes sought, key deliverables and timelines; critical success factors—the main criteria against the success of a project will be measured. This could include a benefits management plan showing that the project is required, the expected benefits and the business changes and enablers that will be required for the anticipated benefits (these should be linked to the objectives); background—an outline of the key drivers for the project, showing how it will contribute to policy outcomes and/or the business strategy; scope—a high-level view of the boundaries of the project, the main assumptions, possible constraints and dependencies; stakeholders how they will be engaged; —and finance—the assessed costing and budget for the project and its components; organisation—the way in which the project is to be organised, led, managed and monitored; risks—the main risks identified so far and how they will be managed; issues—a strategy for capturing and resolving issues; and evaluation an approach for measuring results and achieving outcomes. – a work plan for the short to medium term, which: identifies the components of the project; shows the main deliverables and milestones for each component; shows the contribution each component makes to the overall project outcomes; and contains estimates of resource requirements. These documents, and other information the review team deems relevant, will be requested at the Planning Meeting or during the course of the review. Areas to be Considered in the Business Need Review This section contains topics that would commonly be considered when conducting a Gate 0— Business Need Review. Review teams are expected to use their own expertise in determining the relevance and appropriateness of these topics for the specific project under review. Teams may determine that additional topics are considered critical to the assessment of the project. Policy and Context
where the Gate is integrated with the ICT Investment Approval/Two Stage processes ensure that the review supports development of the first pass business case; check that financing has been adequately assessed for the project; and check that the project is realistic, properly resourced and has authorised work plans through to the next stage of the project. Project Documentation Required for the Business Need Review To undertake the review, the review team may require access to: the NPP or Cabinet Submission/Decision; the entity’s Portfolio Budget Statement, business plan or equivalent documents. These documents should set out the entity’s outcomes and outputs, strategic direction, high level aims and objectives; a project brief that provides information about: objectives—a high-level description of the purposes, outcomes sought, key deliverables and timelines; critical success factors—the main criteria against the success of a project will be measured. This could include a benefits management plan showing that the project is required, the expected benefits and the business changes and enablers that will be required for the anticipated benefits (these should be linked to the objectives); background—an outline of the key drivers for the project, showing how it will contribute to policy outcomes and/or the business strategy; scope—a high-level view of the boundaries of the project, the main assumptions, possible constraints and dependencies; stakeholders —and how they will be engaged; finance—the assessed costing and budget for the project and its components; organisation—the way in which the project is to be organised, led, managed and monitored; risks—the main risks identified so far and how they will be managed; issues—a strategy for capturing and resolving issues; and evaluation – an approach for measuring results and achieving outcomes. a work plan for the short to medium term, which: identifies the components of the project; shows the main deliverables and milestones for each component; shows the contribution each component makes to the overall project outcomes; and contains estimates of resource requirements. These documents, and other information the review team deems relevant, will be requested at the Planning Meeting or during the course of the review. Areas to be Considered in the Business Need Review This section contains topics that would commonly be considered when conducting a Gate 0— Business Need Review. Review teams are expected to use their own expertise in determining the relevance and appropriateness of these topics for the specific project under review. Teams may determine that additional topics are considered critical to the assessment of the project. Policy and Context
RMG-106-guidance-assurance-reviews-process.docx