CCNA People: organizations, teams, and leadership Questions

The 'manage by exception' principle is applied when the Project Manager escalates a forecast tolerance deviation to the Project Board. This principle delegates decision-making authority for day-to-day management within defined tolerances, and only escalates when those tolerances are forecast to be exceeded, ensuring the Project Board focuses on strategic oversight.

The PRINCE2 project management team includes the Project Manager (C) as the person responsible for day-to-day management and the Senior User (D) who represents the interests of those who will use the project's outputs. Both are defined roles in the PRINCE2 management structure, with the Project Manager reporting to the Project Board and the Senior User being a member of that board.

In PRINCE2, the Project Board is chaired by the Executive, also known as the Senior Responsible Owner (SRO). The Executive is ultimately accountable for the project's success and ensures the business case remains viable. The Project Manager manages day-to-day activities but does not chair board meetings.

The Team Manager is responsible for the delivery of Work Packages and reports progress to the Project Manager.

The Executive (Senior Responsible Owner) is accountable for the Business Case and ensuring it remains viable. The Project Manager maintains it on a day-to-day basis, but the Executive holds ultimate responsibility.

The End Stage Report is the key document produced during the Managing a Stage Boundary process. It summarizes the stage's performance against the plan, provides updated business justification, and informs the Project Board's decision to authorize the next stage or stop the project.

Delegating change control decisions to a Change Authority allows the Project Board to focus on strategic oversight and major decisions, while the Change Authority handles smaller, low-impact changes efficiently. This reduces the administrative burden on the Project Board and speeds up the change process, ensuring that minor changes do not require escalation to the board. In PRINCE2, this delegation is a key mechanism for balancing control with agility, as defined in the Change theme.

The Senior User (A) is a correct member of the Project Board because they represent the interests of those who will use the project's product, ensuring the product meets user requirements and provides value. The Senior Responsible Owner (E), also called the Executive, is the correct member who chairs the Project Board and is ultimately accountable for the project's success. Both roles are defined in PRINCE2 as essential for project governance and decision-making.

The Highlight Report is prepared by the Project Manager and sent to the Project Board at intervals defined in the Communication Management Approach.

When an Exception Plan is approved to recover from a budget overrun, the Project Plan must be updated to reflect the new cost and schedule baselines. However, the Business Case must also be updated because the exception plan changes the project's forecast costs and benefits, which directly affects the justification for the project. PRINCE2 requires that the Business Case remains viable and approved whenever a significant deviation occurs, ensuring continued alignment with organizational objectives.

The Executive (Senior Responsible Owner, SRO) is the single point of accountability for the Business Case in PRINCE2. They are responsible for ensuring that the project remains viable and that the Business Case is maintained and updated throughout the project lifecycle, including at stage boundaries and at the end of the project. The Project Manager may draft or update the document, but the Executive owns the justification and must approve any changes.

An RFC proposes a modification to an agreed baseline; an Off-Spec is a deviation from what was specified—something that should be there is missing or incorrect. Both are issues that may require a change control decision.

In PRINCE2, the Team Manager is responsible for the day-to-day management of a Work Package. This includes coordinating the team's work, monitoring progress against the Work Package plan, and reporting back to the Project Manager. The Team Manager acts as the direct interface between the project management team and the team members executing the work.

The Executive (Senior Responsible Owner) is accountable for the Business Case and its maintenance throughout the project. The Project Manager develops and maintains the Business Case on behalf of the Executive, but accountability rests with the Executive.

The Project Manager is delegated the authority to manage the project on a day-to-day basis within agreed tolerances.

A Request for Change (RFC) is a formal proposal to modify a baseline (e.g., a product description, project plan, or scope), while an Off-specification (Off-spec) identifies a situation where a product or component has deviated from its approved specification or baseline. In PRINCE2, an RFC seeks to change what was agreed, whereas an Off-spec reports that something is not as specified. This distinction is critical for managing baselines and controlling issues within the organization's change control procedures.

Managing a Stage Boundary provides the Project Board with information to review the current stage's performance, update the project plan, and approve the next stage plan.

An RFC proposes a change to an approved baseline; an Off-spec is something that should be delivered but isn't or is missing.

The Initiating a Project process produces the Project Initiation Documentation (PID), which is the key output that defines the project's scope, objectives, and approach. The PID consolidates information from the Project Brief and Business Case, providing a baseline for decision-making and governance throughout the project.

Project Assurance is an independent role that provides objective oversight of the project's adherence to PRINCE2 principles, processes, and controls, reporting directly to the Project Board. Project Support, conversely, is a service-oriented role that assists the Project Manager with administrative, planning, and reporting tasks, such as maintaining logs and schedules. The key difference lies in independence: Assurance must be impartial and separate from day-to-day management, while Support works under the Project Manager's direction.

In PRINCE2, Project Support is a defined role responsible for administrative and advisory services to the project management team. The correct answer is designated project support staff because the PRINCE2 manual explicitly states that Project Support can be provided by a dedicated team or individuals assigned to this function, not by the Project Manager or Team Manager who have distinct responsibilities.

Separating the Project Manager and Project Assurance roles ensures that project assurance is performed independently of the project manager, providing objective oversight. This independence allows assurance to verify that the project is being managed correctly without bias, which is a core principle of PRINCE2's management of risk and quality.

The Senior Responsible Owner (SRO) is the single person accountable for the Business Case and ensuring the project delivers the expected benefits. The Project Manager maintains the project documentation but the SRO owns the Business Case.

If a product is defective, the Team Manager should first record the issue as an Off-specification and then raise a Problem/Concern to the Project Manager for resolution.

The Starting Up a Project (SU) process produces the Project Brief, which provides a high-level overview of the project's justification, scope, and approach. The Initiating a Project (IP) process then produces the Project Initiation Documentation (PID), which is a more detailed and comprehensive set of documents that forms the basis for managing the project. This distinction is a fundamental difference in the PRINCE2 methodology, where SU focuses on the initial concept and IP on detailed planning and controls.

The capabilities of the people available directly influence the project management team structure. PRINCE2 emphasizes that the team structure must be designed around the skills, experience, and availability of individuals to ensure roles can be effectively filled and responsibilities discharged. Without assessing capabilities, the structure may assign roles that cannot be performed, leading to project failure.

The Team Manager reports to the Project Manager, who manages the work packages within a stage.

B is correct because PRINCE2's principle of 'defined roles and responsibilities' mandates that Project Assurance be independent from the Project Manager to provide objective oversight of the project's progress, risks, and compliance with the Business Case. This separation ensures that the Project Board receives unbiased information, preventing the Project Manager from having unchecked control over assurance activities. Without this independence, assurance could be compromised by the Project Manager's personal or operational biases.

PRINCE2 separates the Project Manager role from Project Assurance to ensure that assurance activities are independent from the day-to-day management of the project. This avoids a conflict of interest where the Project Manager might be tempted to report overly optimistic progress or hide issues to protect their own performance. The Project Assurance role provides objective oversight, verifying that the project remains aligned with business, user, and supplier interests without being influenced by the Project Manager's personal stake in delivery.

The Executive is ultimately accountable for the project's business justification and ensuring it remains aligned with the organization's strategic goals. In PRINCE2, the Executive owns the Business Case and must approve any changes that affect strategic alignment. The team member's concern about misalignment triggers the Executive's responsibility to review and, if necessary, revalidate the project's mandate.

The Managing a Stage Boundary process is designed to provide the Project Board with sufficient information to review the current stage's performance, approve the next stage's detailed plan, and authorize continued project work. It produces the Stage Plan for the next stage and a request to proceed, ensuring controlled progression between stages.

The Project Manager is delegated authority by the Project Board to manage the project on a day-to-day basis within agreed tolerances.

Project Support is the correct role because it is specifically defined in PRINCE2 as providing administrative and clerical services to the project team, such as maintaining files, scheduling meetings, and managing project documentation. This role is distinct from management or assurance functions, ensuring the team can focus on delivery without administrative overhead.

The accountable person is ultimately answerable for the correct and thorough completion of the deliverable or task, and has 'A' in the RACI chart.

According to PRINCE2's management by exception, if a tolerance is forecast to be exceeded, the Project Manager must escalate to the Project Board via an Exception Report.

The Change Authority is an optional role that is delegated by the Project Board to make decisions on change requests within defined limits, to streamline the change control process.

In PRINCE2, when a project forecasts exceeding its cost tolerance, the Project Manager must escalate the issue to the Project Board via an Exception Report. This is a formal mechanism to request a decision on corrective action, as the Project Manager does not have authority to change tolerances or budgets. The Project Board then evaluates the situation and provides direction, ensuring governance and control over the project's viability.

The Senior Responsible Owner (Executive) is ultimately accountable for the project's success, ensuring the project delivers the expected benefits and remains viable. This accountability is a core PRINCE2 principle, distinguishing the Executive from other roles that have delegated authority for day-to-day management.

(Team Manager) is correct because PRINCE2 defines the Team Manager role as the person responsible for the team's work and for delivering the products within the team plan. This role is distinct from the Project Manager and is formally defined in the PRINCE2 management structure.

The Project Board is responsible for authorizing the start of each stage, including the initiation stage and subsequent management stages. This ensures that the project proceeds only when the board has reviewed and approved the Stage Plan for that stage, providing governance and control over the project's progression.

According to PRINCE2, when a Team Manager reports that a Work Package is likely to exceed its tolerances, the Project Manager must first assess the situation and consider corrective actions within the stage tolerance. This is because the Project Manager has delegated authority to manage the stage within the agreed stage tolerances, and only if the forecast exceeds those tolerances should an Exception Report be raised to the Project Board. The correct first step is always to evaluate whether the issue can be resolved within the existing tolerance limits before escalating.

PRINCE2 separates the Project Manager role from Project Assurance to ensure independent oversight and avoid conflicts of interest. The Project Manager is responsible for day-to-day management and decision-making, while Project Assurance provides an objective check that the project remains aligned with business, user, and supplier interests. This separation prevents the Project Manager from being the sole judge of their own work, which could compromise governance and control.

Project Assurance provides independent oversight to the Project Board, ensuring the project is on track without being influenced by the Project Manager's day-to-day perspective.

The Project Manager is responsible for managing the day-to-day activities of the project within the tolerances set by the Project Board. This includes monitoring progress, resolving issues, and escalating deviations that exceed tolerances. PRINCE2 defines this as a core duty to ensure the project remains on track without requiring constant Board intervention.

PRINCE2 defines specific roles: Project Manager, Team Manager, Project Assurance, Project Support, and the Project Board (Executive, Senior User, Senior Supplier). 'Risk Manager' and 'Quality Manager' are not standard roles in PRINCE2; their responsibilities are typically covered by Project Assurance or delegated within the team.

The Senior User represents the users and ensures that the products meet their needs. The PM manages delivery but the Senior User defines requirements.

An RFC proposes a change to agreed baselines; an Off-spec is a product that does not meet its specification.

In PRINCE2, the Senior Responsible Owner (SRO) is the single point of accountability for the project's success and the realization of benefits. This role is defined in the PRINCE2 framework as the individual who owns the business case and ensures the project delivers the expected outcomes that justify the investment.

The Project Initiation Documentation (PID) is the definitive document created during the Initiating a Project process that defines how the project will be controlled and governed. It consolidates key information such as the project's scope, objectives, roles, responsibilities, and the management controls (e.g., tolerances, reporting, and escalation procedures) that will be used throughout the project. This ensures all stakeholders have a shared understanding of the governance framework before execution begins.

The PRINCE2 Project Board is the decision-making body responsible for overall project governance. It comprises three roles: the Executive (Senior Responsible Owner), the Senior User, and the Senior Supplier. The Senior User represents the interests of those who will use the project's outputs and is essential for defining requirements and benefits.

In PRINCE2, an Exception Report is triggered when a forecast indicates that a stage will exceed its agreed tolerance (e.g., cost or time). Option C is correct because exceeding stage cost tolerance is a formal deviation that requires escalation to the Project Board via an Exception Report, as the Project Manager cannot authorize changes beyond tolerance.

The Project Product Description defines the overall product and its expectations, including user needs, but the User Requirements document captures detailed user needs. However, in PRINCE2, the Project Product Description is the key document for defining what the user expects.

Project Assurance is an independent check that the project is being conducted in compliance with PRINCE2 principles, themes, and processes, ensuring governance and control. A quality review, on the other hand, is a specific technique used to assess the quality of a product (e.g., a document or deliverable) against predefined quality criteria. Therefore, the key difference is that Project Assurance focuses on the project's overall adherence to PRINCE2, while a quality review focuses on the quality of a specific product.

The Senior Responsible Owner (SRO/Executive) is accountable for the Business Case and must ensure it remains viable. The Project Manager develops and maintains it on behalf of the SRO.

The Project Support role in PRINCE2 is specifically defined to provide administrative and clerical services to the project management team. This includes maintaining project files, tools, and configuration management records, ensuring that the project operates efficiently without burdening the project manager with routine tasks.

Project Assurance independently monitors compliance with standards and assesses risks and issues, reporting to the Project Board. It does not manage day-to-day or provide admin support.

In PRINCE2, the Executive is the individual who is ultimately accountable for the project's business justification and ensuring that the project remains viable. The Executive is responsible for developing and maintaining the Business Case throughout the project lifecycle, including updating it at stage boundaries and confirming its continued viability before proceeding. The Project Manager is responsible for creating the Business Case initially and monitoring it, but the Executive retains accountability for its ongoing validity.

The Project Board is responsible for providing resources and authorizing funds for the project. This is a key duty of the board, as they own the business case and must ensure the project remains viable by approving the necessary budget and resource allocation.

In PRINCE2, when a stage is forecast to exceed its cost tolerance, the Project Manager must escalate the issue to the Project Board by raising an Exception Report. This is because the Project Manager does not have authority to exceed the agreed tolerance; the Project Board must decide whether to approve a revised plan or take other corrective action. Option D correctly follows the PRINCE2 exception management process.

In PRINCE2, the Project Board does not meet on a fixed schedule like weekly or monthly. Instead, it operates on an exception-driven basis, meaning it convenes only when triggered by management by exception—typically when a stage's tolerances are forecasted to be exceeded or when a decision is required outside the delegated authority. This aligns with PRINCE2's principle of management by exception, ensuring the board focuses on strategic oversight rather than day-to-day operations.

The SRO owns the Business Case and is accountable for the project's success and benefits realization. They also chair the Project Board.

The Project Board approves the Stage Plan for the next stage, allowing the project to proceed. This is part of the exception-driven decision-making.

PRINCE2 mandates that Project Assurance is independent of the Project Manager to ensure objective oversight. Option C is correct because Project Assurance's primary role is to provide an independent view of the project's health, checking compliance with standards and business justification.

The 'Starting Up a Project' process is the first process in PRINCE2, executed before the project is formally initiated. Its key output is the Project Brief, which provides a high-level overview of the project's justification, scope, and approach, enabling the Project Board to decide whether to proceed to the initiation stage.

The Project Manager is responsible for producing the Project Initiation Documentation (PID) in PRINCE2. The PID is a key deliverable that consolidates the project's scope, business justification, plans, and controls, and the Project Manager compiles it based on input from the Project Board and other stakeholders. This responsibility is explicitly defined in the PRINCE2 Project Manager role description.

An Exception Plan is produced when a stage is forecast to exceed its tolerances, as an alternative to the current Stage Plan, for approval by the Project Board.

The Team Manager is responsible for delivering the Work Package within agreed tolerances and reporting progress via Checkpoint Reports.

The Project Initiation Documentation (PID) is the key output of the Initiating a Project process, providing a foundation for the project.

Project Assurance and quality reviews serve distinct purposes in PRINCE2. Project Assurance is an independent oversight function that ensures the project remains viable, compliant, and on track against the business case and plans. A quality review, on the other hand, is a structured technique used to assess whether a specific product meets its defined quality criteria and is fit for purpose.

The Project Initiation Documentation (PID) is the key output of the Initiating a Project process because it consolidates all essential information—such as the Business Case, project scope, risks, and controls—into a single baseline document that authorizes the project to proceed. PRINCE2 mandates that the PID is created during this process to provide a firm foundation for the project and to enable senior management to make an informed decision about project continuation.

The Executive (Senior Responsible Owner) is the role accountable for the Business Case and its ongoing justification throughout the project. PRINCE2 requires the Business Case to be maintained and reviewed at every stage boundary to ensure continued viability, and this responsibility rests with the Executive, not the Project Manager or Team Manager.

PRINCE2's Controlling a Stage process requires the Project Manager to escalate any forecast deviation beyond the agreed stage tolerance to the Project Board via an Exception Report. The Project Manager cannot proceed without the Board's direction, as the tolerance is a delegated authority limit set by the Board.

Project Assurance provides an independent view of the project's progress, ensuring that the project remains viable and adheres to the business case. It reports directly to the Project Board, not the Project Manager, to maintain objectivity. This independence is critical for the Board to make informed decisions about project continuation.