
- Foreword and Introduction
- 1: Putting projects in context
- 2: Entity arrangements
- 2.1 Strategic alignment
- 2.2 People and culture
- 2.3 Effective governance
- 2.4 Common APS Requirements
- Summary for entity arrangements
- 3: Individual project proposals
- 3.1 Clarifying the concept
- 3.2 The business case
- 3.3 Approving the project
- Summary for individual projects
- 4: Project implementation
- Appendices
- Quick reference card
PDF version of guide [3.0MB]
PDF of Quick reference card [0.3MB]
Tips for PDF and HTML versions [0.5MB]
Word version of checklists [0.1MB]
3.1 Clarifying the concept
Given the relatively high cost of preparing business cases with firm costings and timeframes, it is generally preferable to prepare proposals for projects on a progressive basis – that is, in a series of proposals of increasing detail.
The first step in progressive planning is a short project concept plan. The concept plan can be brief – one page, or a few pages. The brevity of the plan helps focus attention on its central issues.
The concept plan helps to establish that:
- the project is developed taking account of the broader context, and contributes as much as practicable to entity and government objectives;
- the key business outcomes of the project are clearly articulated; and
- the project deliverables are necessary and sufficient to lead to the desired business outcomes.
The concept plan may also be useful in explaining the concept to stakeholders and gaining their views of the proposal. At the entity level, the preparation and circulation of project concept plans helps provide early notice of projects and assists the entity in coordinating all its projects and resources.
An example of a concept plan is provided in Appendix C – Sample project concept at page 104.
Previous: Individual project proposals
Next: Broad planning context