9.6 Control Resources

Make sure the equipment, materials and facilities you secured stay available when needed.

Monitoring and Controlling / Resource · ← PMBOK reference · See it on the map

Why it matters

A physical resource acquired once can still be pulled away to another project or run out partway through; this is what catches that before it stalls the work.

What done looks like

Actual resource use is tracked against the plan and any shortfall has been resolved.

First time tip

Check resource availability at the start of every reporting period, not only when something has already gone wrong. A shortfall is cheaper to fix early.

What you need (Inputs)

• 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
• Issue Log
  How Scrum/Kanban projects satisfy this — counted from: impediments (driftless/models/agile.py:Impediment) — an impediment IS an issue raised against the team's progress; healthy once none are open or in progress
• Physical Resource Assignments
• Project Schedule
  How Scrum/Kanban projects satisfy this — counted from: releases (driftless/models/agile.py:Release) — a release with a target date is the agile reading of a project schedule when there is no sprint or milestone to read one from
• Resource Breakdown Structure
• Resource Requirements
• Work Performance Data
• Agreements

How you do it (Tools & Techniques)

• Data Analysis
• Problem Solving
• Interpersonal and Team Skills
• Influencing
• Project Management Information System

What you get (Outputs)

• Work Performance Information
  How Scrum/Kanban projects satisfy this — counted from: sprints under way (driftless/models/delivery.py:Sprint) for an agile project, or service levels and incidents (driftless/models/operations.py) for an operations-cadence one — a sprint under way is the work performance data an agile team reads instead of a baseline-and-actuals pair; an operations-cadence project reads the same question off its service levels and the incidents raised against them
• Change Requests

Worked example

Halfway through, the scaffold's rental is about to run out while the high wall still needs a second coat. The period check catches it in time to extend the booking, rather than the morning it disappears.

Common pitfalls

• Checking availability only after something has already stalled.
• Tracking the team's time but not the equipment and materials.
• Assuming a resource secured once stays secured to the end.

How driftless helps

Driftless does not yet help run this process — no technique here is runnable and no output is producible in the wizard.