9.1 Plan Resource Management

Decide, up front, who does what and what physical resources you need.

Planning / Resource · ← PMBOK reference · See it on the map

Why it matters

Without a clear plan for roles and resources, two people quietly assume the same task belongs to the other, and neither of them does it.

What done looks like

Roles, responsibilities, and needed physical resources are written down and assigned.

First time tip

Name a single owner for each role, even on a small team wearing several hats. A shared role without a named owner is where accountability disappears.

What you need (Inputs)

• Project Charter
• Project Management Plan
• Scope Baseline
  How Scrum/Kanban projects satisfy this — counted from: committed backlog items and definition-of-done items (models/agile.py) — a committed backlog (status ready/in_progress/done) plus a written definition of done is what an agile team baselines scope against
• Requirements Documentation
  How Scrum/Kanban projects satisfy this — counted from: backlog items (driftless/models/agile.py:BacklogItem) — a backlog item's description IS its requirement statement; present once any item has one, healthy once every item does
• Risk Register
• Stakeholder Register
• Enterprise Environmental Factors
• Organizational Process Assets

How you do it (Tools & Techniques)

• Expert Judgment
• Data Representation
• Organizational Theory
• Meetings

What you get (Outputs)

• Resource Management Plan
  How Scrum/Kanban projects satisfy this — counted from: project roles (driftless/models/agile.py:ProjectRole) — naming who holds each agile role (product owner, Scrum Master, developer, stakeholder proxy) is how an agile team plans its resources, in place of the stored prose plan a predictive project writes
• Team Charter
• Assumption Log

Worked example

The renovation names one owner per role — the director accepts deliverables, the project manager runs the schedule, one coordinator handles the teen-room volunteers — and lists the physical resources too, down to the scaffold the high wall needs.

Common pitfalls

• Letting two people share a role with no single named owner.
• Listing the people and forgetting the physical resources the work needs.
• Writing the roles down but never telling the team who holds which.

How driftless helps

• Organizational Theory can be run here.
• Meetings can be run here.
• Resource Management Plan can be created in the wizard.
• Team Charter can be created in the wizard.
• Assumption Log can be created in the wizard.