1.1 Project Roles and Stakeholder Responsibilities

Current PK0-005 Exam Identity and Blueprint

This guide is for CompTIA Project+ V5, exam PK0-005. CompTIA's current certification page lists a November 8, 2022 launch, a maximum of 90 questions, multiple-choice and performance-based items, 90 minutes, and a passing score of 710 on a 100–900 scale. It recommends 6–12 months of hands-on experience managing projects in an IT environment and lists English, Japanese, and Thai delivery.

An older Version 6.0 objectives PDF says “maximum of 95 questions,” but CompTIA's current live certification page says maximum of 90. Use the live page for current logistics; use the objectives document for the detailed scope below.

The four domains contain 24 numbered objectives in total. This guide maps every objective to real teaching and uses the official weightings to set study priority. Project Management Concepts and Project Life Cycle Phases together account for 63% of the scored blueprint, but Tools/Documentation and IT/Governance remain required rather than optional.

Project Roles and Stakeholder Responsibilities

Projects are essentially driven by people. Without clearly defined roles and responsibilities, a project can quickly descend into chaos, with duplicated efforts, missed deadlines, and misaligned expectations. In this section, we will deeply explore the key players in a project environment and what the CompTIA Project+ exam expects you to know about their specific responsibilities. The success of any project, large or small, hinges not just on the technical skills of the team, but heavily on the interpersonal dynamics, clearly defined authorities, and the diligent management of stakeholder expectations. When studying for the exam, it is vital to clearly delineate the boundaries of authority for each role to properly diagnose scenario-based questions.

The Project Sponsor

The project sponsor is the champion of the project. They are typically a senior executive or manager who has a vested interest in the project's outcome. The sponsor is the person who secures the funding, approves the project charter, and provides high-level direction. You can think of the project sponsor as the project's ultimate patron and protector within the corporate hierarchy.

Key Responsibilities of the Sponsor:

• Providing Funding: The sponsor holds the purse strings. They ensure the project has the necessary budget to proceed, often fighting for these resources during corporate budgeting cycles. Without the sponsor's financial backing, the project is merely an idea. They review and approve the cost baseline and are the primary point of contact when additional funds are required due to unforeseen, massive scope changes.
• Championing the Project: The sponsor advocates for the project at the executive level, securing buy-in from other senior leaders and removing high-level roadblocks that the project manager cannot handle alone. When other departments are hesitant to provide resources, the sponsor uses their political capital to smooth the way.
• Approving the Project Charter: The sponsor signs off on the charter, formally authorizing the project and granting the project manager their authority. This document is the bedrock of the project, formally authorizing the work and defining the project manager's authority within the organization.
• Ultimate Decision Maker: While the project manager handles day-to-day decisions, the sponsor has the final say on major changes, especially those impacting budget or schedule. Depending on the governance model, the sponsor or another authorized governing body may approve cancellation.

Exam Trap: On the exam, distinguish between who manages the project (the PM) and who authorizes it (the sponsor). If a question asks who signs the project charter or provides funding, the answer is almost always the project sponsor.

The Project Manager (PM)

The project manager is the person assigned by the performing organization to lead the team that is responsible for achieving the project objectives. They are the focal point for all project activities. The PM must balance the competing constraints of scope, schedule, budget, quality, resources, and risk. They must be both a leader and a manager, inspiring the team while also meticulously tracking progress. The PM is the glue that holds the project together, serving as the central hub of communication and coordination.

Key Responsibilities of the PM:

• Day-to-Day Management: The PM manages the execution of the project plan, ensuring tasks are completed in the correct sequence. They do not necessarily do the technical work, but they facilitate its completion.
• Communication: The PM is the primary communicator, ensuring stakeholders are informed of progress, risks, and issues. They must tailor their communication style to suit different audiences, from technical deep-dives with developers to high-level executive summaries with the sponsor.
• Resource Management: The PM ensures team members have what they need to complete their tasks, whether that's software licenses, physical equipment, or training. They manage team dynamics, resolve conflicts, and foster a collaborative environment.
• Scope, Schedule, and Budget Management: The PM monitors these constraints constantly to ensure the project stays on track, employing change control processes when deviations occur. They are responsible for updating baselines and mitigating risks proactively.

The Project Team

The project team consists of the individuals performing the actual work of the project. Their roles can vary wildly depending on the project's nature, but their primary responsibility is execution. A high-performing team is self-motivated, communicative, and skilled in their respective disciplines. They estimate task durations, identify technical risks, and report on their progress.

Specialized Roles within the Team:

• Project Coordinator: Often found in weaker matrix organizations, the coordinator assists the PM with administrative tasks, scheduling, and communication, but has limited decision-making authority. They help keep the trains running on time but do not drive the train. Their existence implies a structure where the PM might be overwhelmed or lacks full authority.
• Project Scheduler: In larger, more complex projects, a dedicated scheduler may be responsible for developing and maintaining the project schedule, updating sophisticated software tools, and tracking progress against baselines. This allows the PM to focus on broader strategic issues rather than getting bogged down in Gantt charts.
• Business Analyst: Frequently heavily involved in the early stages, they gather and document requirements from stakeholders, bridging the gap between business needs and technical solutions.

Stakeholders

A stakeholder is any individual, group, or organization that may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project. This is a very broad definition! It includes the sponsor, PM, and team, but also customers, end-users, regulatory bodies, and even the local community.

Stakeholder Management

• Identification: You must identify stakeholders as early as possible. Missing a key stakeholder early on can lead to disastrous scope changes later. Tools like stakeholder registers and power/interest grids are essential here. If a department head is ignored during planning, they might reject the final deliverable, causing massive rework.
• Engagement: Keep stakeholders engaged throughout the project. Their input is vital for requirements gathering, risk identification, and user acceptance. Failing to manage stakeholder expectations is one of the leading causes of project failure. You must actively communicate, manage expectations, and address concerns to maintain support.

Understanding these distinct roles is critical for both the CompTIA Project+ exam and real-world project management success. Make sure you can clearly delineate who is responsible for what. When you encounter scenario questions, first identify which role the protagonist is playing, and then apply the rules of responsibility.