
Project Authority Resources: Roles, Responsibilities, and Decision Rights
PMBOK v8 Definition
Authority is defined as "the right to apply project resources, make decisions, sign approvals, accept deliverables, and influence others to carry out the work of the project." A Role is "the function assumed by, or assigned to, a person in the project," with examples including civil engineer, business analyst, and testing coordinator. Responsibility is the work assigned to a team member, and team members operate best when their individual levels of authority match their individual responsibilities.
Why It Matters for the Exam
This concept appears frequently in PMI exam questions about Resource Management, particularly in scenarios involving team conflict, unclear decision-making, or project delays. Questions test your ability to distinguish between Role, Authority, and Responsibility, and to identify when a mismatch between authority and responsibility creates project problems.
Key Points to Remember (for the exam)
-
Core Distinction: Role = function assigned; Authority = right to apply resources and make decisions; Responsibility = work assigned. These three are distinct but interdependent.
-
Critical Rule: "Team members operate best when their individual levels of authority match their individual responsibilities." This is a direct PMBOK principle frequently tested.
-
Authority Scope Includes: Applying project resources, making decisions, signing approvals, accepting deliverables, and influencing others.
-
Examples of Authority Decisions: Selecting a method for completing an activity, setting quality acceptance criteria, and determining how to respond to project variances.
-
Key Output Document: The Resource Management Plan, which includes "Roles and responsibilities" as a core component.
-
Leadership vs. Authority: Authority is "the position of control given to individuals within the organization," whereas leadership is about "inspiring and motivating others through leading by example." These are different concepts.
-
Resource Management Plan Components: Includes identification of resources, acquiring resources guidance, and roles and responsibilities documentation.
Typical PMI Exam Example
A project manager notices that the testing coordinator is making decisions about quality acceptance criteria without consulting the project sponsor. The testing coordinator has responsibility for testing activities but no authority to approve quality standards. What is the MOST likely outcome? → The team member's authority does not match their responsibility, leading to potential rework, conflict, and project delays.
PMI Exam Traps
-
Trap: Confusing "Role" with "Authority"
-
Reality: Role is the function assigned (e.g., business analyst); Authority is the right to make decisions and apply resources. A person can have a role without having corresponding authority.
-
Trap: Thinking authority and responsibility should always be separated
-
Reality: PMBOK states they should MATCH. Mismatch creates operational problems.
-
Trap: Confusing "Authority" with "Leadership"
-
Reality: Authority is positional control given by the organization; Leadership is about inspiring and motivating through example. They are different and not exclusive to any specific role.
-
Trap: Assuming authority only applies to the project manager
-
Reality: Authority is defined for each role in the project. Different roles have different levels of authority for different decisions.
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Resource Management Plan | Contains | Roles and responsibilities are documented within this plan; exam tests what components belong here |
| Project Management Team | Executes Authority | The team (or sole PM) exercises authority to manage resources and make decisions |
| Leadership | Distinguished from | Authority = positional control; Leadership = inspiring others. Both are needed but different |
| Responsibility Assignment Matrix (RAM) | Related Tool | RAM shows who is responsible for what work; Authority is about decision rights, not just task assignment |
| Physical Resource Management | Complementary | Authority applies to both team resources AND physical resources (materials, equipment) |
Quick Review Questions
-
A project team member has been assigned the role of testing coordinator but lacks the authority to approve test results. According to PMBOK, what is the likely impact on project performance?
-
What are the five specific rights included in the definition of "Authority" in project management?
-
A project manager selects a method for completing an activity without consulting the team. Does this fall within the definition of Authority? Why or why not?
-
What is the difference between Authority and Leadership as defined in PMBOK v8?
-
In which document would you find the documented roles and responsibilities for a project?
PMBOK v8 Reference
Section 2.5 - Project Management Roles Section 3.6.1 - Project Impact (Leadership vs. Authority distinction) Resource Management Plan components (Identification of resources, Acquiring resources, Roles and responsibilities)