Change Theme

Correct Answer: Based on the issue's impact on project objectives, time, cost, quality, scope, benefits, and risk.

According to PRINCE2 best practices, severity and priority levels for issues should be determined based on their impact on project objectives and constraints (time, cost, quality, scope, benefits, and risk). This ensures that the most critical issues affecting project success are addressed appropriately. The second option is incorrect because prioritizing based on stakeholder seniority could lead to critical issues being missed simply because they were raised by junior team members, which doesn't align with objective project management principles. The third option is incorrect because while numerical scales are commonly used, PRINCE2 doesn't mandate a fixed 1-5 scale across all projects. Different projects may require different assessment approaches based on their specific contexts. The fourth option is incorrect because the resources required to implement resolution actions should not be the primary factor in determining an issue's severity or priority. An issue with high impact on project objectives might require minimal resources to resolve, yet still be high priority.

Correct Answer: During project initiation, as part of defining the change control approach.

In PRINCE2, the Change Authority is established during project initiation as part of defining the change control approach. This is when roles and responsibilities for change management are defined and documented in the Project Initiation Documentation (PID). The Change Authority needs to be in place from the beginning of the project so that changes can be managed effectively throughout the project lifecycle. The second option is incorrect because waiting until after the first milestone would leave the project vulnerable to unmanaged changes during the initial stages. Change management processes should be established before any project work begins. The third option is incorrect because it suggests a reactive approach. According to PRINCE2, change management structures should be established proactively at the start, not created as a response to being overwhelmed with change requests. The fourth option is incorrect because the Change Authority is a persistent role throughout the project, not something that gets established at the end of each stage. While change control activities occur throughout all stages, the authority itself is defined during initiation.

Correct Answer: The project team may lose track of the latest approved versions of products

The correct answer is "The project team may lose track of the latest approved versions of products." Configuration Management in PRINCE2 is responsible for tracking and controlling the project's products throughout their lifecycle. Its primary purpose includes ensuring product versions are properly identified and tracked, maintaining information about product status, and protecting products from unauthorized changes. When a project lacks an effective Configuration Management Strategy, the team can't reliably identify which version of a product is the current approved one. This leads to confusion, potential use of outdated versions, inconsistencies between products, and ultimately rework or defects. The other options are incorrect: "The Project Board will not be able to approve the project initiation" - Project initiation approval depends on the Project Initiation Documentation's content and viability, not specifically on Configuration Management. "Team Managers will be unable to assign work to team members" - Work assignment relates to resource management, not Configuration Management. Poor version control doesn't prevent assigning tasks. "The project will automatically require exception plans for all change requests" - Exception plans are created for forecast deviations beyond tolerance levels. Poor Configuration Management doesn't automatically trigger exception plans for every change request.