Authority

The formal power to assign and direct project resources, commit funds, make decisions, and issue approvals.

Key Points

  • Formally granted by the organization or sponsor, often documented in the project charter or agreements.
  • Defines what the project manager can approve, including spending limits, resource assignments, and certain scope or schedule changes.
  • Scope of authority varies by organizational structure; it is narrower in functional/matrix settings and broader in projectized environments.
  • Authority can be delegated with clear limits, while overall accountability remains with the delegator.

Example

A project manager is authorized to approve up to $25,000 in contingency spending and reassign team members across work packages without seeking sponsor approval. When a testing bottleneck occurs, the PM buys additional test equipment and temporarily moves two engineers to testing to keep the schedule on track.

PMP Example Question

Which action best demonstrates a project manager's authority?

  1. Coaching a team member to improve performance
  2. Negotiating a discount with a supplier
  3. Approving use of contingency funds to purchase extra test equipment
  4. Facilitating a lessons learned workshop

Correct Answer: C — Approving use of contingency funds

Explanation: Authority is the formal power to commit resources and spending, make decisions, and issue approvals. Option C reflects that formal decision-making power.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Seven sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Build the Sprint Reporting System, Not Another Prompt

AI Systems with Claude is our own course for Scrum Masters and Agile Project Managers, taught against one running project across seven sections. You build five working systems and keep them: the sprint report machine, the retro intelligence system, the stakeholder comms engine, the backlog health monitor, and the risk and dependency tracker. Direct from HK School of Management, not on Udemy.

See What Is Included