You have been recommended for the project manager role, but there are others on the shortlist, including some very experienced consultants.

In order to convince you are the person for the job, you need to develop a project and submit the Project Initiation Document (PID) using PRINCE2 and covering the subheading provided in ILX document.

Project: Installation of Solar Panels for Rental Properties

You have to:

- provide an understanding of the theory of PRINCE2 and follow the document guidelines;

- demonstrate the application of PRINCE2 theory to your topic;

- Provide the rationale for proposed plans and choices based on evidence and research;

- use academic conventions, referencing and writing skills appropriate for L6.

- You are free to use any tool or technique, permitted by PRINCE2, that will in your opinion be best at supporting your individual project topic. For example, you may wish to use WBS and Gantt charts or just one. Your risk management may be qualitative or quantitative or a combination of both. Ultimately, it is up to you to decide which tool(s) and or techniques(s) would best suit the project and deploy them accordingly.

Structure to use:

1 Project definition and approach

Definition:

[Explaining what the project needs to achieve. It should include:

- Background

- Project objectives and desired outcomes- Project scope and exclusions

- Constraints and assumptions

- The user(s) and any other known interested parties

- Interfaces]

Approach

[To define the choice of solution that will be used in the project to deliver the business option selected from the business case, taking into consideration the operational environment into which the solution must fit]

2 Project management team structure

[A chart showing who will be involved with the project]

3 Role descriptions

[For the project management team and any other key resources]

4 Quality management approach

[(See section A.22) Describing the quality techniques and standards to be applied, and the responsibilities for achieving the required quality levels. Where the project is subject to the commissioning organizations quality management policies/strategies, the PID should make reference to them rather than duplicate them. Where the project is not subject to the commissioning organizations quality management policies/strategies, appropriate strategies/ approaches should be documented]

5 Change control approach

[(See section A.3) Describing how and by whom the projects products will be controlled and protected. Where the project is subject to the commissioning organizations change control policies/strategies, the PID should make reference to them rather than duplicate them. Where the project is not subject to the commissioning organizations change control policies/strategies, appropriate strategies/ approaches should be documented]

6 Risk management approach

[(See section A.24) Describing the specific risk management techniques and standards to be applied, and the responsibilities for achieving an effective risk management procedure. Where the project is subject to the commissioning organizations risk management policies/strategies, the PID should make reference to them rather than duplicate them. Where the project is not subject to the commissioning organizations risk management policies/strategies, appropriate strategies/ approaches should be documented]

7 Communication management approach

[(See section A.5) To define the parties interested in the project and the means and frequency of communication between them and the project. Where the project is subject to the commissioning organizations communication management policies/strategies, the PID should make reference to them rather than duplicate them. Where the project is not subject to the commissioning organizations communication management policies/strategies, appropriate strategies/ approaches should be documented]

8 Project plan

[(See section A.16) Describing how and when the projects objectives are to be achieved, by showing the major products, activities and resources required on the project. It provides a baseline against which to monitor the projects progress management stage by management stage]

9 Project controls

[Summarizing the project-level controls such as management stage boundaries, agreed tolerances, monitoring and reporting]

10 Tailoring of PRINCE2

[A summary of how PRINCE2 will be tailored for the project.]