CCNA People: organizations, teams, and leadership Questions

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.

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 Project Manager is delegated the authority to manage the project on a day-to-day basis within agreed tolerances.

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.

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.

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.

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 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.

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 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.

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.

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.

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.

Project Assurance is a PRINCE2 role responsible for providing independent oversight of the project's adherence to standards, regulations, and business justification, ensuring the project remains viable. In contrast, a quality review is a specific management technique used to assess whether a product meets its defined quality criteria, involving a structured meeting of reviewers. Option C correctly distinguishes the role (Project Assurance) from the technique (quality review).

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.

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.

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.

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.

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.

Defined roles and responsibilities is the PRINCE2 principle that ensures every member of the project team understands their role, accountability, and reporting relationships. In a dispersed team, applying this principle means explicitly defining who does what, who reports to whom, and how communication will flow, which directly addresses the need for clear accountability and effective communication across time zones.

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 principle 'defined roles and responsibilities' is essential for ensuring that all team members understand their roles and how they contribute to the project. In a remote, multicultural setting, this clarity is vital for effective collaboration and cohesion. Other principles like manage by exception or focus on products are important but do not directly address the team's need for role clarity.

In PRINCE2, the Project Board is responsible for defining project-level tolerance levels for time, cost, quality, scope, risk, and benefits. This is because the Project Board represents the business, user, and supplier interests and sets the boundaries within which the Project Manager can operate without needing to escalate. The Project Manager works within these tolerances and only escalates if forecasts exceed them.

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.

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 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.

In PRINCE2, the Project Initiation Documentation (PID) provides a comprehensive baseline for the project, including defined roles and responsibilities. When team members are unclear about their roles, the PID is the management product that formally documents these assignments, ensuring everyone understands their accountabilities. This aligns with the PRINCE2 principle of 'defined roles and responsibilities' and the 'People' domain focus on organizational clarity.

The Project Initiation Documentation (PID) is the key document produced as an output of the Initiating a Project process. It consolidates the Project Brief, Business Case, and detailed plans into a single source of information that defines the project's scope, objectives, and controls, and is used to obtain authorization to proceed.

In the RACI model, accountability (A) means ultimate ownership and answerability for the task or decision, while responsibility (R) means actually performing the work. There should be only one accountable person per task, but multiple people can be responsible. This distinction ensures clear ownership and execution.

Project Assurance is independent from the Project Manager and reports to the Project Board.

The Project Manager assesses each Request for Change, evaluates its impact on the project's baselines, and provides the necessary information to the Change Authority for a decision. This ensures that the Change Authority can make an informed choice. The Project Manager is accountable for the change control procedure and acts as the link between those raising changes and those deciding on them.

Project Assurance is an ongoing, independent oversight role that ensures the project remains aligned with its business justification and adheres to standards throughout the project lifecycle. In contrast, a quality review is a specific, time-boxed event (e.g., a PRINCE2 quality review technique) used to evaluate a completed product against its quality criteria. The key difference is that Project Assurance is a continuous role, while a quality review is a discrete event.

In PRINCE2, the Project Manager is responsible for preparing the Project Initiation Documentation (PID) during the Initiating a Project process. The PID is a key management product that defines the project's scope, objectives, and controls, and the Project Manager must compile it based on input from the project board and other stakeholders.

Project Assurance is a role within the PRINCE2 framework, responsible for ensuring that the project remains viable and compliant with its business case, while quality review is a technique used to assess the quality of products. The correct relationship is that Project Assurance is a role, and quality review is a technique, making option C correct. They are distinct concepts: one is a governance role, the other is a specific method for evaluating deliverables.

Separation ensures independent oversight. Project Assurance provides an objective check on the project's health, free from the PM's day-to-day pressures.

The Team Manager produces the Checkpoint Report for the Project Manager to report progress of a Work Package.

Project Assurance provides independent oversight to ensure that the project is managed correctly. If the Project Manager also performed assurance, it would compromise objectivity and independence.

The Executive is ultimately accountable for the project's business justification, including ensuring value for money. Concerns about cost versus benefits must be escalated to the Executive, who owns the Business Case and has the authority to approve changes or stop the project if value is not being delivered.

In PRINCE2, the Team Manager is responsible for producing Checkpoint Reports to inform the Project Manager about progress, status, and issues within a Work Package. Checkpoint Reports are the routine progress communication from the team level up to the project management level, typically at frequency defined in the Work Package's tolerances.

Management by Exception is the PRINCE2 principle that defines tolerances for each management level and empowers the level below to act autonomously within those tolerances, escalating only when a forecast breach occurs. This is precisely the mechanism by which the Project Board delegates decision-making to the Project Manager within agreed boundaries.

The Senior Supplier is the Project Board role accountable for the technical integrity of the project's products and for providing the necessary technical expertise. The other roles focus on user interests, independent assurance, or team-level production, and therefore do not satisfy the requirement for supplier-side technical accountability.

Separating Project Manager from Project Assurance ensures objectivity and independence of assurance activities. The Project Manager is responsible for day-to-day management and cannot objectively assess their own work.

The Project Board consists of three roles: the Executive (Senior Responsible Owner), Senior User(s), and Senior Supplier(s). In this question, the two roles from the Project Board that are listed are Senior User (Option A) and Executive (Option E). Team Manager, Project Manager, and Project Support are not Project Board roles.

In PRINCE2, the Checkpoint Report is the formal progress report provided by a Team Manager to the Project Manager on a regular basis. It details progress against the Work Package, including achievements, next steps, and any issues or risks, enabling the Project Manager to monitor work at the team level.

In PRINCE2, the Project Board should meet at the end of each stage and when exceptions occur. This is because the Board is responsible for stage boundary decisions and for handling exceptions that threaten the project's tolerances. Regular meetings are not prescribed; the frequency is driven by stage boundaries and exception events.

In PRINCE2, the Project Board is the ultimate decision-making body responsible for approving key project documentation, including the Project Initiation Documentation (PID). The Project Manager prepares the PID, but it must be formally approved by the Project Board to authorize the project to proceed to the next stage. This ensures that the business case, risks, and plans are accepted at the appropriate governance level.

Project Assurance is a role defined in PRINCE2, responsible for ensuring the project remains viable and compliant with its business justification, while a quality review is a technique used to assess the quality of a product or deliverable. The key difference is that Project Assurance is an ongoing role performed by individuals independent of the Project Manager, whereas a quality review is a specific, time-boxed event or technique for inspecting deliverables. Option A correctly identifies this fundamental distinction between a role and a technique.

Tailoring is the PRINCE2 principle that requires the project management approach to be adapted to the project's size, complexity, and environment. For a globally dispersed team, tailoring communication methods, meeting schedules, and collaboration tools ensures that the team can work effectively together. The other principles address governance, product focus, and learning, but not the specific need to adapt to the team's context.

The Team Manager is responsible for managing the team on a day-to-day basis and ensuring that products are produced to the required quality criteria. These responsibilities are defined in the Work Package and are essential for the successful delivery of the project's products.

The Team Manager should report the issue to the Project Manager via a Checkpoint Report or exception process, as they are accountable for delivery within tolerances.

The Senior User is accountable for ensuring that the project's products will deliver the expected benefits. This role represents the user community and is responsible for specifying their needs, confirming that the solution meets those needs, and realizing the benefits. While the Executive is ultimately accountable for the business case, the Senior User provides the user perspective and confirms benefits realization.

The Project Board is responsible for overall direction and control of the project, including authorizing deviations from tolerances and approving Stage Plans. These duties ensure the project remains aligned with business objectives and governance requirements.

The Team Manager is responsible for managing the delivery of a Work Package within a PRINCE2 project. This role coordinates the team members, ensures the work is completed according to the agreed specifications, and reports progress 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 PRINCE2 principle 'Defined roles and responsibilities' requires that roles are clearly defined and that assurance roles are independent from management roles. Assigning the Project Manager also as Project Assurance violates this principle because Project Assurance must be independent of the Project Manager to provide objective oversight.

The Team Manager is responsible for delivering Work Packages and reporting progress to the Project Manager. In PRINCE2, the Team Manager coordinates the work of the team, ensures the Work Package is completed to specification, and provides regular progress reports to the Project Manager, who manages the overall project.

In PRINCE2, Project Assurance is a separate role from the Project Manager to ensure objective oversight of the project's adherence to standards, plans, and business justification. The Project Manager is responsible for day-to-day management and delivery, so allowing them to also perform Project Assurance would create a conflict of interest, as they would be reviewing their own work. This independence is critical for the integrity of the assurance function, which must provide unbiased checks on the Project Manager's decisions and outputs.

Project Assurance is the correct answer because in PRINCE2, Project Assurance is a distinct role responsible for monitoring and reporting on the project's adherence to the management and technical standards, independent of the Project Manager. It ensures that the project remains aligned with the business case, quality requirements, and stakeholder expectations, acting as the 'eyes and ears' of the Project Board.