PRINCE2 Prince2-Foundation - PRINCE2 7 Foundation written Exam

The Risk Register in PRINCE2® is a document used to detail all identified risks associated with the project, including both threats and opportunities. This register includes descriptions of each risk, their status, and the responses planned or taken to manage these risks, serving as a key tool for risk management throughout the project lifecycle.References: = PRINCE2® 7 Foundation Training Manual and official PRINCE2® website documentation

In PRINCE2®, the Project Executive is responsible for the overall success of the project, which includes securing the necessary funding before the project begins. This role is part of the project board and has the authority to commit organizational resources and funds, ensuring that the project is financially viable from start to finish.References: = PRINCE2® 7 Foundation Training Manual and official PRINCE2® website documentation

Product-based planning in PRINCE2 focuses on defining and understanding the project's outputs or products. This method helps in determining the project's approach by clarifying what products must be delivered, thus guiding the planning of activities and resources needed to create these products. It ensures that the project's structure and execution strategy are aligned with delivering tangible, well-defined outcomes.References: PRINCE2® 7 Foundation resources on product-based planning.

When the change authority asks for more information regarding a proposed change, this occurs during the 'Assessing issues' step of the 'issue management technique' in PRINCE2. This step involves evaluating the impact and implications of issues or changes, including requesting additional information necessary to make informed decisions.References: PRINCE2® 7 Foundation resources on issue and change management.

The objectives of the 'Starting Up a Project' process include providing an interface between the corporate or program environment and the project (objective 1) and providing business justification for initiating the project (objective 4). This process ensures that the project is viable and worthwhile before further resources are committed and that there is a clear link to corporate strategies and ongoing work.References: (PRINCE2® 7 Foundation Handbook, AXELOS)

A requirement in the context of PRINCE2® is defined as a documented need or expectation that is formally approved and used as a basis for further project development. This documentation typically includes specific details about project scope, expected outcomes, and performance criteria, which are crucial for project planning and execution.References: = PRINCE2® 7 Foundation Training Manual and official PRINCE2® website documentation

In PRINCE2, a Team Plan is a type of plan that might only be produced for very large or complex projects. It is typically more detailed and is specifically designed to manage a segment of the project within a certain team or group. This plan provides detailed guidance on the delivery of the products assigned to the team within the constraints set by the Stage Plan.References: (PRINCE2® 7 Foundation Handbook, AXELOS)

In the PRINCE2 methodology, the 'project mandate' is the term used for initial documentation that triggers the start of a project, typically provided by corporate or program management. It can often come in the form of a request for proposal received by an external supplier, setting out the initial definition of the project and what it aims to achieve, which then leads to more detailed project definitions in the 'starting up a project' process.References: PRINCE2® 7 Foundation resources on project initiation documentation.

When the project manager is also acting as the team manager, they should use a 'Work Package Description' to control the work of a team member. This management product details what is to be delivered, the reporting requirements, and the tolerances within which the team member must work, providing a clear definition and control mechanism for delegated tasks.References: PRINCE2® 7 Foundation guide on management products, specifically Work Packages.

In PRINCE2, the 'Issue and Change Control' procedure encompasses the management of issues throughout the project lifecycle, including capturing, examining, and deciding on issues. Archiving superseded versions is part of the final step in the 'Deciding on changes' phase, where decisions are made on the issues and subsequent actions, including updates to project baselines and documentation, are implemented and archived as necessary.References: PRINCE2® 7 Foundation handbook and official resources on issue management technique.