CCNA People: organizations, teams, and leadership Questions

The 'Managing a Stage Boundary' process includes reviewing the 'Project Initiation Documentation' to ensure the project organization remains suitable. Updating the PID, including the Project Board composition if needed, ensures that the Board has the appropriate authority and engagement for the next stage. Delegating all decisions, replacing a Board member, or increasing meeting frequency do not directly address the need to confirm the organization's viability.

The Project Manager manages the project on a day-to-day basis within the tolerances set by the Project Board.

The Project Manager is responsible for day-to-day management, including preparing Highlight Reports for the Project Board and managing stage boundaries. Project Assurance is independent, and the Project Board defines tolerances.

Separation ensures independence and objectivity in assurance, preventing conflicts of interest where the PM would be checking their own work.

In PRINCE2, Project Assurance is the role responsible for independently monitoring and assuring the Project Board that the project remains viable and on track across business, user, and supplier perspectives. It provides the Board with confidence by checking that the project is being managed according to PRINCE2 principles, themes, and processes. This independence is what distinguishes it from the Project Manager's day-to-day management responsibilities.

In PRINCE2, the trigger for preparing an Exception Plan during the Managing a Stage Boundary process is the raising of an Exception Report. This report is created when the Project Manager forecasts that stage tolerances will be exceeded, indicating that the current Stage Plan cannot be completed within its agreed tolerances. The Exception Plan then replaces the existing Stage Plan to bring the project back within tolerance.

The Project Initiation Documentation (PID) is the key output of Initiating a Project and defines the project's approach, controls, and plans.

In PRINCE2, a Request for Change (RFC) is a formal proposal to change a product, baseline, or agreed scope, while an Off-specification is a formal notification that a product or deliverable does not meet its specified requirements. The key distinction is that an RFC is a proactive suggestion for change, whereas an Off-specification is a reactive report of a deviation or failure against an agreed specification.

In PRINCE2, the Team Manager is responsible for delivering the work package and reports to the Project Manager on progress, issues, and risks. The Project Manager (Sarah Lee) is the single point of contact for the Team Manager within the project management team. Therefore, any potential delay must be reported to the Project Manager, who will then escalate to the Project Board if necessary.

The Project Manager is responsible for the day-to-day management of the project within the tolerances set by the Project Board. This includes planning, delegating, monitoring, and controlling all aspects of the project, while reporting any deviations that exceed the agreed tolerances to the Project Board.

The Stage Plan is the detailed plan for each management stage, created at the end of the previous stage.

Closing a Project involves preparing closure, handing over products, evaluating, recommending closure, and then formally closing.

In PRINCE2, the Project Board is not a day-to-day management body; it meets only when decisions are needed outside the delegated authority of the Project Manager. The correct frequency is exception-driven, meaning the Board convenes when a stage boundary is reached, an exception report is raised, or the project is ready for closure. This aligns with PRINCE2's principle of management by exception, where the Board's involvement is triggered by specific events rather than a fixed schedule.

In PRINCE2, the Team Manager is responsible for managing the delivery of one or more Work Packages. This role ensures that the work defined in the Work Package is completed according to the agreed quality criteria, time, and cost, and reports progress back to the Project Manager. The Team Manager acts as the direct supervisor of the team producing the products.

The Team Manager is responsible for the delivery of one or more Work Packages, which are defined by the Project Manager. The Team Manager coordinates the team's work, ensures quality, and reports progress back to the Project Manager. This role is focused on the technical execution of assigned work packages within the project.

Project Assurance provides independent assurance to the Project Board that the project is being managed correctly. This role is responsible for monitoring all aspects of the project's performance and ensuring that the project remains viable, and it reports directly to the Project Board.

In PRINCE2, the Project Board is responsible for appointing the Project Manager. This is because the Project Board represents the business, user, and supplier interests and has the authority to delegate day-to-day management to the Project Manager. The Project Board's responsibility includes ensuring the right person is appointed to manage the project on their behalf.

The Executive (SRO) chairs the Project Board and is accountable for the project's success.

In the Controlling a Stage process, the Project Manager is responsible for taking corrective action to keep the stage within its tolerances. Since the stage tolerance is not forecast to be exceeded, the issue remains within the Project Manager's delegated authority, so they should take corrective action without escalating. Escalation is only required when tolerances are forecast to be breached.

The Project Initiation Documentation (PID) is the definitive document created during the Initiating a Project process. It consolidates the project's scope, objectives, and management controls, serving as the foundation for project governance and decision-making. PRINCE2 mandates the PID to ensure all stakeholders have a single source of truth for how the project will be managed.

In PRINCE2, the Project Board is chaired by the Executive (also known as the Senior Responsible Owner in many organizations). The Executive is ultimately accountable for the project's success, provides business justification, and ensures the project remains viable. The chairperson role is explicitly assigned to the Executive in the PRINCE2 management structure, not to the Senior Supplier, Senior User, or Project Manager.

PRINCE2 allows the Team Manager and Project Support roles to be combined with the Project Manager role in appropriate circumstances, such as smaller projects. However, roles that require independence or represent different interests cannot be combined. Project Assurance must remain independent, and Project Board roles such as Senior User and Executive must be separate from the Project Manager to ensure proper governance and accountability.

In PRINCE2, the Team Manager is responsible for managing the delivery of Work Packages and reporting progress to the Project Manager. This role ensures that the products defined in the Work Package are created to the required quality, within time and cost constraints, and provides regular progress reports to the Project Manager.

The 'Managing a Stage Boundary' process in PRINCE2 is designed to provide the Project Board with sufficient information to review the current stage's performance, approve the next stage plan, and confirm continued business justification. This process ensures that the project remains viable and that the Project Board can make informed go/no-go decisions before committing resources to the next stage.

The PRINCE2 Project Board is composed of three mandatory roles: the Executive (Senior Responsible Owner), the Senior Supplier, and the Senior User. The Project Manager is not a member of the Project Board; instead, the Project Manager reports to the Project Board and manages the project on a day-to-day basis. Therefore, the Project Manager is NOT a mandatory role on the Project Board.

Separation ensures independent and objective assurance that the project is running correctly, free from the biases or conflicts of day-to-day management.

In PRINCE2, the Project Manager is responsible for authorizing work packages to be executed by the team. This is because the Project Manager manages the day-to-day activities and has the authority to assign work to team members or Team Managers, ensuring that the work packages align with the project plan and stage tolerances. The Project Board provides overall direction and approves stage plans, but the authorization of individual work packages is delegated to the Project Manager.

The Project Board in PRINCE2 is designed to be an exception-driven body; it convenes only when decisions are required, such as approving stage plans or exception plans, rather than on a fixed schedule. This aligns with the PRINCE2 principle of management by exception, where the board delegates day-to-day management to the Project Manager and escalates only when tolerances are forecast to be exceeded.

The Change Authority is the correct role to decide on low-impact changes when the Project Board has delegated that authority. The Project Manager assesses the change but does not decide, and the Project Board only gets involved if the change exceeds the delegated limits.

The Change Authority role exists specifically to allow the Project Board to delegate authority for approving or rejecting changes. Project Assurance, Project Support, and Team Manager do not have the mandate to make change control decisions on behalf of the Project Board. When the Project Board is too busy to handle all change requests, appointing a Change Authority with defined limits is the correct PRINCE2 approach.

In PRINCE2, the Change Authority is a body to which the Project Board delegates responsibility for making decisions on change requests and off-specifications, within defined limits. This allows the board to focus on strategic oversight while empowering a separate group to handle change control efficiently. The Change Authority is formally defined in the 'Organize' process and its authority is documented in the Project Initiation Documentation.

The Project Manager manages the project on a day-to-day basis within the tolerances delegated by the Project Board.

The Senior Supplier represents those who provide the necessary goods, services, and expertise to the project.

In PRINCE2, when a Work Package is at risk of being delivered late but remains within its agreed tolerances, the Project Manager should agree corrective actions with the Team Manager. This is because the Team Manager is responsible for day-to-day management of the Work Package, and the Project Manager's role is to support and guide without escalating unless tolerances are forecast to be exceeded. Corrective actions within tolerance keep the project on track without unnecessary escalation.

Project Assurance is the PRINCE2 role specifically designed to provide independent oversight and assurance to the Project Board. It ensures that the project is being managed effectively and that products meet quality standards. In a multi-supplier environment, this independence is essential to give the Board confidence that all parties are performing as required.

The Work Package is the correct document for authorising a Team Manager to deliver specific products. It contains all the necessary details, including product descriptions, quality criteria, tolerances, and reporting requirements, ensuring that the Team Manager has a clear understanding of what is expected. Other documents, such as the Stage Plan or Project Initiation Documentation, serve different purposes and do not provide the task-level authorisation required.

In PRINCE2, Project Support is an optional role that provides administrative services to the project, such as maintaining files, collecting progress data, and managing project documentation. The role is not mandatory because the project manager can perform these tasks or they can be delegated to a separate support function. This distinguishes it from the other roles, which have specific governance or delivery responsibilities.

In PRINCE2, the Project Support role is optional and is only required when the project is large or complex enough to need administrative or specialist support. The PRINCE2 manual explicitly lists Project Support as a role that may be filled, whereas the Executive, Senior User, and Project Manager are mandatory roles on every project.

The Change Authority is a role defined in PRINCE2's Change Control approach, responsible for reviewing and making decisions on change requests within limits of delegated authority set by the Project Board. This ensures that minor changes can be approved quickly without escalating every request to the Project Board, balancing control with efficiency.

The Change Authority role is explicitly delegated by the Project Board to make decisions on change requests within agreed tolerances. This delegation allows the Change Authority to approve or reject changes without requiring the Project Board to convene for every minor change, streamlining the change control process while keeping decisions within predefined limits.

The Project Initiation Documentation (PID) is created during the Initiating a Project process. This process takes the initial project mandate and outline business case from Starting Up a Project and develops them into a comprehensive, baselined set of documents that define the project's scope, objectives, risks, and controls. The PID is formally approved by the Project Board during this process, providing the authority to proceed with the project.

Project Assurance is an independent oversight role that reports to the Project Board. The SRO can assign technical assurance to an individual with appropriate skills, separate from the Project Manager.

Project Assurance provides independent oversight to the Project Board, ensuring the project is managed correctly from business, user, and supplier perspectives. The Executive is accountable but Project Assurance performs the checks.

The project board provides unified direction to the project, ensuring that the business, user, and supplier interests are represented and aligned. This is a core PRINCE2 principle: the board makes key decisions and approves stage plans, but does not get involved in day-to-day management.

The Project Board is responsible for approving the project initiation documentation and authorizing project closure. These are key governance decisions that ensure the project remains aligned with business objectives and is formally closed. Day-to-day management, product creation, and work package assignment are delegated to the Project Manager and team.

Facilitating leadership in PRINCE2 involves enabling and empowering the team, rather than directing them. Delegating authority and seeking recommendations encourages ownership and engagement, which directly addresses the disengagement. The other actions either maintain a directive approach, escalate unnecessarily, or take punitive measures without addressing the leadership style itself.

The Team Manager is responsible for managing the delivery of one or more Work Packages and reports to the Project Manager.

In PRINCE2, the Project Board is responsible for overall project governance, including delegating change control decisions to a Change Authority. This delegation allows the Change Authority to approve or reject change requests within predefined limits, freeing the Board from day-to-day change management while retaining strategic oversight.

Project Assurance is the role responsible for providing independent assurance that the project remains on track, as defined by PRINCE2. It ensures that the project is being conducted correctly, adheres to the business case, and meets quality standards, without being involved in the day-to-day management. This role is separate from the Project Manager and Project Support to maintain objectivity.

PRINCE2 mandates that Project Assurance be independent from the Project Manager to ensure objective and unbiased monitoring of the project's performance against plans, risks, and quality criteria. This separation prevents the Project Manager from self-assessing their own work, which could lead to skewed reporting or overlooked issues. The independence is a core principle of the PRINCE2 governance model, ensuring that assurance activities are not influenced by the day-to-day pressures of delivery.

The Project Board is the PRINCE2 management layer responsible for overall project direction and key decision-making. The Senior User is a mandatory Project Board role representing the interests of those who will use the project's products, ensuring the project delivers the required benefits. The Executive is also a mandatory Project Board role, acting as the project's ultimate decision-maker and owner of the business case.

PRINCE2's Communication Management Strategy is the formal mechanism for defining roles, responsibilities, and information flows. By revisiting it, the Project Manager can clarify the business analysts' and developers' roles in decision-making and requirements specification, directly addressing the root cause of misunderstandings. This aligns with the 'Manage by Stages' and 'Defined Roles and Responsibilities' principles, ensuring the team collaborates effectively without unnecessary escalation or personnel changes.

The separation ensures independent oversight. The Project Manager is responsible for day-to-day management, while Project Assurance provides an impartial view to the Project Board to avoid conflicts of interest.

An RFC is a proposal for a modification (change) to the project's products, while an Off-specification is a situation where a product does not meet its specification (a deviation).

The Team Manager is responsible for delivering one or more Work Packages as defined in the Stage Plan. This role focuses on the technical delivery of products within the constraints agreed with the Project Manager, ensuring quality, time, and cost targets are met for those specific work packages.

Project Assurance is an independent oversight function, performed on behalf of the Project Board, to ensure that the project is being conducted correctly and remains viable. Project Support, in contrast, is a set of administrative and advisory services provided to the Project Manager to help them manage the project effectively. This distinction is fundamental to PRINCE2's separation of 'doing' from 'checking'.

The Project Board is responsible for authorizing the movement from one stage to the next, which includes approving the Stage Plan for the next stage and reviewing the current stage's completion. This is a key control point in PRINCE2's stage-gate management approach, ensuring that the project only proceeds when the Board is satisfied with progress and the business case remains viable.

The Project Manager manages day-to-day activities, produces Highlight Reports for the board, and updates the Business Case as needed. The PM does not chair the board or perform assurance.

Team Manager and Project Assurance are PRINCE2 roles. The others are not.

The Change Authority role is specifically authorized to approve Requests for Change within delegated limits set by the Project Board. This delegation allows the Change Authority to make decisions on low-impact changes without requiring full Board approval, streamlining the change control process.

In PRINCE2, the Project Manager, Project Board, and Team Manager are all mandatory roles within the project management team. Project Support is the only optional role, as its responsibilities can be absorbed by the Project Manager or other team members, or provided by a separate office like a PMO. The PRINCE2 manual explicitly states that Project Support is not a required role, making D the correct answer.

The Senior Responsible Owner (Executive) is the single point of accountability for ensuring the project delivers value for money and remains aligned with the organization's business strategy. This role owns the business case, approves key stage boundaries, and has ultimate authority over project funding and continuation, directly linking project outputs to strategic objectives.

Project Assurance is the correct role because it is explicitly defined in PRINCE2 as the independent check that the project remains viable, compliant, and aligned with the business case. Unlike Project Support, which provides administrative services, or the Project Manager, who manages day-to-day execution, Project Assurance reports directly to the Project Board to verify that the project is being conducted correctly and that the business justification remains valid throughout the project lifecycle.

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.

The Project Board is responsible for approving the end stage report and authorizing the next stage. This is a critical governance decision that ensures the project continues to be viable and aligned with business objectives. The Project Manager prepares the report, but the Board holds the authority to proceed.

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 Senior User role is defined in PRINCE2 to represent the users' interests and ensure that the project delivers the required outcomes. They are accountable for specifying user requirements and monitoring that the solution meets them. In this scenario, the Senior User is the role that ensures user needs are met, making it the correct answer.

Documenting role descriptions in the Project Initiation Documentation and using a Responsibility Assignment Matrix both ensure that roles and responsibilities are clearly defined and communicated. These actions help team members understand their accountabilities, reduce ambiguity, and can improve motivation by providing clarity and fairness. They align with the PRINCE2 principle of defined roles and responsibilities.

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.