Understanding Project Manager Authority

A project manager needs authority to effectively lead the project team, make decisions, and manage resources. This authority typically comes from formal sources established within the organization and the project governance structure.

Sources of Project Manager Authority Analysis

Let's examine the given options to determine which one is NOT a standard source of authority for a project manager:

• Delegation from senior management: This is a primary source of authority. Senior management authorizes the project and delegates the necessary authority to the project manager to carry it out. Formal authority flows from higher levels of the organization downwards.
• Delegation from subordinates: Authority flows from higher levels down to lower levels in an organizational hierarchy, not the other way around. Subordinates report to the project manager; they do not delegate authority to the project manager. Therefore, delegation from subordinates is not a source of authority for a project manager.
• Job description for a project manager: The project manager's job description outlines their role, responsibilities, and the scope of their authority within the organization. This document serves as a formal definition of the authority granted to the person holding the project manager position.
• Project charter: The project charter is a formal document that authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities. It is a foundational document for project authority.

Identifying the Non-Source of Authority

Based on the analysis, it is clear that authority is delegated from senior management to the project manager, defined by the job description, and formalized in the project charter. Authority is not delegated *upwards* from subordinates to the project manager.

Therefore, delegation from subordinates is not one of the sources of authority for a project manager.