driftless
Search

5.2 Collect Requirements

Find out, in detail, what stakeholders actually need from the project.

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

Why it matters

A requirement missed here surfaces later as a change request, and a late change almost always costs more than the same requirement caught at the start.

What done looks like

Requirements are documented, traced, and stakeholders agree they are complete.

First time tip

Interview stakeholders one at a time before you run a group workshop. A quiet voice gets heard alone that a loud group would talk over.

What you need (Inputs)

How you do it (Tools & Techniques)

What you get (Outputs)

Worked example

The project manager interviews the head librarian, a teen-program volunteer and an accessibility advocate separately, and learns the teen room needs power outlets at every table — a requirement none of them would have raised in a joint meeting.

Common pitfalls

How driftless helps