9.3 Acquire Resources
Actually get the people and materials the plan says you need.
Executing / Resource · ← PMBOK reference · See it on the map
Why it matters
A great resource plan is worthless if the named people are unavailable or the materials cannot actually be obtained on the schedule the plan assumed.
What done looks like
The people and physical resources the plan requires have been secured and are ready.
First time tip
Confirm availability with each person's actual manager, not just the person themselves. A verbal yes from the individual is not the same as a released commitment.
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 - 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 Requirements
- Resource Calendars
- Enterprise Environmental Factors
- Organizational Process Assets
How you do it (Tools & Techniques)
What you get (Outputs)
Worked example
The two painters are confirmed with their own supervisor rather than only with them, and the scaffold is reserved in writing for the week the schedule needs it, not for the month around it.
Common pitfalls
- Taking an individual's yes as a commitment their manager has released.
- Securing the people but leaving the equipment to be found later.
- Booking a resource for roughly the right time rather than the scheduled week.
How driftless helps
- Pre Assignment can be run here.
- Virtual Teams can be run here.
- Physical Resource Assignments can be created in the wizard.