CCNA Prince2 Overview Principles Questions

This principle requires that a project has a justifiable Business Case and that the justification is reviewed and updated throughout the project, not just at the start. Since the Business Case has not been reviewed since authorization, the project no longer fulfills this principle. The project board must ensure the Business Case remains valid at every stage.

The learn from experience principle requires that the project team captures and applies lessons throughout the project. By emphasizing this principle, the Project Manager ensures that reviews, lessons logs, and continuous improvement are integral to each stage, addressing the Board's concern.

Focus on products means that the project is driven by the definition and delivery of products, including their quality criteria. This principle ensures that before work starts, the product description defines what the product must do and how it will be judged fit for purpose, directly answering the team manager's question.

This principle requires that the project has an organizational structure with defined roles and responsibilities, including the project board representing business, user, and supplier interests. By defining these roles and ensuring accountability, the project manager is directly applying this principle, which is essential for effective governance and decision-making throughout the project lifecycle.

Focus on products requires that the project is driven by the definition and delivery of products, not just by activities. Defining products and their quality criteria first ensures that planning is based on what must be delivered and to what standard. This approach helps avoid scope creep and ensures that activities are only included if they contribute to a defined product.

Manage by exception mandates that the Project Manager only escalates when a tolerance is forecast to be exceeded. Here, the cost tolerance is at risk, so the Project Manager should escalate to the Project Board, providing an exception report and seeking a decision on how to proceed.

Tailoring allows PRINCE2 to be adapted to the project's size, complexity, and environment. Combining processes or reducing documentation where appropriate is a valid tailoring decision, as long as the principles are still applied. In this scenario, the project manager is tailoring the method to fit the project's needs.

This principle requires that a PRINCE2 project has a justifiable reason to continue. Adding a new reporting requirement may affect the business case, so the project manager must assess whether the change is still justified. The principle ensures that the project remains aligned with its business objectives and that any changes are evaluated against the ongoing viability of the business case.

The principle of continued business justification is mandatory in every PRINCE2 project. Even for a small project, there must be a valid Business Case that justifies the investment and is reviewed regularly. Tailoring may simplify how the Business Case is documented, but the principle itself must be applied.

Focus on products means that the project is driven by the delivery of products, and their descriptions are agreed upon before development. This ensures clarity on what is to be delivered, quality criteria, and acceptance criteria. Product descriptions are baselined and used to manage scope and quality, so this statement is correct.

Manage by stages means breaking the project into stages, each with its own plan and a decision point for the project board. This allows the board to review progress and make informed decisions before committing to the next stage. The scenario describes exactly this: dividing the project into manageable chunks with clear plans and decision points, which is the essence of the principle.

This is correct because the principle demands a clear organizational structure with defined roles and responsibilities. The project board, project manager, and team managers must have clear accountabilities. This ensures that decisions are made by the right people and that there is no ambiguity about who is responsible for what. The structure must be agreed upon and communicated to all stakeholders.

Learn from experience requires that lessons are captured and applied continuously throughout the project. Waiting until the end violates this principle. The project manager should implement ongoing lesson capture and review, ensuring that lessons are used to improve the project as it progresses.

This is correct because continued business justification requires that the business case is reviewed and updated at key decision points, such as stage boundaries. This ensures the project remains aligned with strategic objectives and that benefits are still expected to outweigh costs and risks. Regular review allows the project board to decide whether to continue, change, or stop the project based on current information.

Tailoring involves adapting PRINCE2 processes and themes to the project's size, complexity, and risk. Combining stages for a small, low-risk project is a tailoring decision that ensures the method is proportionate, demonstrating the tailor to suit the project environment principle.

Dividing the project into manageable stages, each with its own plan and decision point, directly implements the manage by stages principle. The board authorises the next stage plan only, retaining control between stages rather than committing upfront to a full-project Gantt chart.

Manage by exception means that the project board sets tolerances and the project manager only escalates when a forecast breach is likely. Presenting an exception plan at a stage boundary because tolerances will be exceeded is a direct application of this principle, ensuring that decisions are made at the right level.

Manage by stages requires the project board to authorise each stage and review the business case at stage boundaries. If the configuration lacks defined stage boundaries with decision points, this principle is absent, so the project proceeds without formal end-stage assessments.

This principle allows PRINCE2 to be adapted to the project's size, complexity, and risk. Simplifying documentation and reducing stage boundaries for a small project is a direct application of tailoring. The project board's decision reflects the need to avoid unnecessary bureaucracy while maintaining PRINCE2's core structure.

This action clearly defines the key roles within the project organization and documents them in the project initiation documentation. The principle requires that roles and responsibilities are defined and understood by all involved. By specifying the project board, project manager, team manager, and project assurance, the project manager ensures a clear structure and accountability.

Defined roles and responsibilities requires that projects have clearly defined roles, with the project board comprising the executive, senior user, and senior supplier. By ensuring these roles are filled, the project manager is applying this principle. It ensures accountability and that all interests are represented. This is the primary principle being applied in this scenario.

This principle establishes tolerances and delegates authority so that the project manager can work within them without constant board involvement. Escalation occurs only when tolerances are threatened. The scenario directly describes this: the board sets cost tolerance and the project manager manages within it, escalating only if exceeded.

Tailor to suit the project environment is the PRINCE2 principle that explicitly allows the method to be adapted to the project's size, complexity, risk, and organizational context. This includes reducing documentation and combining management products, as long as the principles are still applied. The project manager can therefore streamline the approach while maintaining the integrity of PRINCE2.

Continued business justification requires a viable business case to be maintained throughout the project. Recording the justification and reviewing it at stage boundaries and on major changes ensures the project remains aligned with business objectives and can be stopped if the justification disappears, which is exactly what this scenario demands.

This is a PRINCE2 principle.

Manage by exception mandates that the project manager escalates to the project board as soon as a tolerance is forecast to be exceeded. The project manager should present the issue along with options and a recommendation. This allows the project board to make an informed decision, such as granting a tolerance or changing the plan. Escalation is the correct action per the principle.

This principle ensures that the project has a clear organizational structure with defined roles, such as the Project Board representing business, user, and supplier interests. By applying it, the project manager establishes accountability and decision-making authority, which is essential for project success and aligns with the scenario's need for clear representation of all three interests.

Defined roles and responsibilities ensures that every individual in the project knows what is expected of them and that there is clear accountability. In PRINCE2, this is achieved through the project management team structure, including the Project Board, Project Manager, Team Manager, and assurance roles. The scenario describes the need for clear expectations and accountability, which is the essence of this principle.

Tailoring means adapting PRINCE2 to the specific needs of the project, such as its size, complexity, and risk. This action directly demonstrates the principle by ensuring that the method is not applied rigidly but is scaled appropriately. It allows the project to be managed efficiently without unnecessary bureaucracy while still maintaining PRINCE2's core principles.

Continued business justification is a PRINCE2 principle that requires the project to have a valid business case that is reviewed and updated throughout. It ensures the project remains aligned with business objectives and should be stopped if no longer justified. This principle directly focuses on the project's justification, making it one of the correct choices.

This principle requires that a PRINCE2 project has a defined organizational structure with clear roles and responsibilities for all involved. The project board's agreement to have accountable roles directly reflects this principle. It ensures that everyone knows what is expected of them and who is accountable for what.

The 'focus on products' principle requires defining and agreeing product descriptions before development begins, so work is driven by required outputs. Creating descriptions after products are built inverts this sequence, meaning the principle is being ignored.

The 'Defined roles and responsibilities' principle ensures that the project has a clear organisational structure with defined roles, such as the project board, project manager, and team managers. It directly addresses the need for a clear structure and accountability, which is what the project manager is emphasising. This principle is essential for effective decision-making.

Manage by exception requires the project manager to monitor against tolerances and escalate only when a tolerance is forecast to be exceeded. Assessing the change against scope, cost, and time tolerances determines whether the project manager can handle it within delegated authority. If the change exceeds those limits, an exception report must be raised to the project board so it can decide how to proceed.

Tailoring involves adapting PRINCE2 to the specific needs of the project, including its size, complexity, risk, and environment. Combining roles and simplifying documentation are examples of tailoring. In this scenario, the project manager is applying the tailoring principle to ensure that the method is proportionate to the project's scale and risk, which is exactly what tailoring requires.

PRINCE2 mandates continued business justification, so the business case must be reassessed whenever viability is questioned. The board owns that decision; stopping is correct if benefits no longer justify the investment, regardless of sunk costs.

Manage by exception requires the project manager to escalate to the project board as soon as a forecast breach of tolerance is identified. Since the time tolerance is forecast to be exceeded, the project manager must inform the board and seek their decision on how to proceed, ensuring that the board maintains control.

This action demonstrates tailoring by applying the 'learn from experience' principle in a way that fits the agile environment. Retrospectives are a common agile practice that aligns with the principle's intent to capture and use lessons. Tailoring allows the principle to be implemented using techniques that suit the project's delivery approach, while still fulfilling the principle's requirements.

This is a PRINCE2 principle.

Manage by exception requires that the Project Manager only escalates to the Project Board when a tolerance is forecast to be exceeded. In this scenario, the time tolerance is expected to be breached, so the Project Manager must raise an Exception Report to inform the Board and seek their decision. This allows the Board to make an informed choice, such as approving a new baseline or stopping the project.

According to the 'Manage by exception' principle, if a stage is forecast to exceed its tolerances, the project manager must escalate the exception to the project board. The board then decides how to proceed. Informing the board immediately is the correct action because the project manager's authority is limited by the stage tolerances.

This is correct because the 'manage by exception' principle requires that if a stage tolerance is forecast to be exceeded, the project manager must escalate the issue to the project board by creating an exception report. The project board then decides how to proceed. This ensures that the project board maintains control and can make informed decisions about the project's direction.

Changes must be managed within stage boundaries.

Focus on products requires that the project is driven by the definition and delivery of products, not just by activities. In this scenario, the lack of clear product definitions has caused scope creep and rework. Applying this principle means defining the products, their quality criteria, and their acceptance criteria upfront. This will provide a clear scope and reduce ambiguity, directly addressing the issue.

The principle of manage by exception requires the project manager to escalate to the project board as soon as it is forecast that a tolerance will be exceeded. Since the cost tolerance is at risk, the project manager must inform the board and seek a decision, rather than attempting to resolve it independently or amending the business case without authority.

Continued business justification requires that a project has a valid business case that is reviewed and updated throughout the project. If the business case is not updated, the project may continue even if it no longer delivers value. This principle ensures that the project remains aligned with business objectives and should be stopped if justification is lost. The scenario directly violates this principle.

Tailoring is the PRINCE2 principle requiring the method to be adapted to the project's size, complexity, importance, capability and risk. For a complex infrastructure project, this principle justifies scaling processes, roles and documentation to fit the specific context rather than applying PRINCE2 rigidly.

Manage by exception is the principle that establishes tolerances for the six aspects of project performance (time, cost, scope, quality, risk, and benefits) and delegates authority to the project manager to manage within those tolerances. The project manager only escalates to the Project Board when an exception is forecast, which is exactly what is described in the scenario.

This is correct because the principle of defined roles and responsibilities requires that all members of the project team, including the project board, project manager, team managers, and other stakeholders, have clearly defined roles and responsibilities. This ensures accountability and effective decision-making. In this scenario, the project manager is applying this principle by ensuring clarity of roles and responsibilities.

Defined roles and responsibilities is the PRINCE2 principle that requires a clear organizational structure with defined roles, responsibilities, and relationships. It ensures that all stakeholders understand who is accountable for what, and that the project has the necessary decision-making bodies, such as the project board. This principle directly supports the need for accountable roles in the project organization.

Continued business justification demands that a project has a clear, documented business case that is approved and reviewed at each stage. In this scenario, confirming alignment with strategic objectives and maintaining the business case throughout ensures the project remains viable and worth the investment.

The 'Defined roles and responsibilities' principle requires that the project has a clear organisational structure with accountable roles, including a project board, before work begins. Here, the project board has not been appointed, yet the project manager is already producing products. This directly contradicts the principle that roles must be defined and agreed.

The 'Continued business justification' principle requires that a project has a justifiable business case throughout its life. By reviewing the End Stage Report and Next Stage Plan at a stage boundary, the project board assesses whether the business case remains valid and whether the project should continue. This directly supports the principle by ensuring the project is still worthwhile before committing to the next stage.

This principle requires that a project has a valid business case and that the justification for the project is maintained throughout its life. By ensuring a clear business case is approved before proceeding, the project manager is applying this principle, which ensures the project remains aligned with business objectives and delivers value.

In PRINCE2 the Executive is the single point of accountability for the project and represents the business perspective on the project board. They ensure that the project remains aligned with business objectives and that the business case is valid, making them the correct answer for who is ultimately accountable.

Continued business justification requires the business case to remain valid and viable throughout the project, not merely at initiation. Reviewing revenue against investment continuously applies that principle directly, satisfying the stem's condition that viability is maintained.

The principle of continued business justification requires that a PRINCE2 project has a viable Business Case that is reviewed and updated at stage boundaries. The Project Board's review of the updated Business Case at 'Managing a Stage Boundary' directly supports this principle by ensuring the project remains aligned with corporate strategy and that benefits still outweigh costs and risks.

This principle requires that the project remains aligned with strategic objectives and that the business case is reviewed at stage boundaries. The board is checking that the project still provides value. This is a direct application of the principle, as it ensures the project continues to be justified beyond the initial approval.

This principle requires that a project has a valid Business Case and that it remains justified throughout. Changes that are not assessed against the Business Case could undermine the project's viability. Therefore, allowing changes without impact assessment directly violates the principle of continued business justification.