Applying PRINCE2 Practices

Correct Answer: Executive

In PRINCE2, the Executive role typically chairs the Project Board. The Executive is appointed by the corporate or programme management to ensure that the project is focused on achieving its objectives and delivering a product that will achieve the forecasted benefits. The Executive is ultimately accountable for the project's success and has the final say on major decisions. The Senior User represents the interests of those who will use the final product. While they are an important member of the Project Board, they do not typically chair it. The Project Assurance Coordinator is not a standard PRINCE2 role. Project Assurance is a function that can be delegated by Project Board members to verify aspects of the project, but it is not a chairing role. The Senior Supplier represents the interests of those designing, developing, and implementing the project's products. The financial investment of the supplier does not determine who chairs the Project Board in PRINCE2.

Correct Answer: Issue Register

In PRINCE2, the Issue Register is the document that records all project issues and maintains information about their status throughout the project's lifecycle. The Issue Register is a key management product in PRINCE2 that provides a central repository for capturing and managing all issues that might affect the project. It tracks information such as issue description, impact, priority, status, and resolution actions. The other options are incorrect: Change Authority Document - This is not a standard PRINCE2 document. Change authority refers to a person or group with authority to approve changes, not a document for tracking issues. Configuration Item Record - This document tracks the status of specific configuration items (project products), not issues. While it may record changes to products, it doesn't serve as the central log for all project issues. Issue and Change Control Strategy - This defines the approach and procedures for issue and change management, but it's not the document used to record and track individual issues. It establishes how issues will be managed rather than being the actual log of issues.

Correct Answer: Identifying the products required and their dependencies

In PRINCE2, Product-Based Planning is a specific planning technique that focuses on identifying and analyzing the products that the project must deliver, rather than the activities needed to create them. This technique emphasizes the importance of clearly defining what is to be delivered before determining how it will be delivered. The correct answer is "Identifying the products required and their dependencies" because Product-Based Planning centers on first identifying all the products that need to be delivered, then understanding the relationships and dependencies between these products. This approach helps ensure that all required outputs are identified and properly sequenced before planning activities. The other options are incorrect: "Defining detailed activity schedules based on resource availability" focuses on activities and resources rather than products, which is contrary to the product-focused approach of Product-Based Planning. "Establishing comprehensive risk mitigation strategies for all project activities" relates to risk management rather than planning techniques, and again focuses on activities instead of products. "Creating complex Gantt charts that map all project activities over the timeline" describes a timeline-based activity planning approach, not the product-based approach emphasized in PRINCE2.