Book Review: Mastering the Requirements Process
A clear, story-led review of Volere’s toolkit for turning fuzzy intent into measurable, buildable requirements without ceremony.
Kickoff, Tuesday 9:00. Marta scans the slide, then asks, “So what exactly ships in v1?” Heads tilt. Someone opens a blank wiki page. The churn warms up.
Suzanne and James Robertson’s Mastering the Requirements Process (3rd ed.) offers the antidote. It packages the Volere approach as a flexible toolkit of processes, templates, and artifacts, enabling teams to discover the real problem, partition the work around external events, and make every requirement measurable. This review is for analysts, product teams, and stakeholders who want rigor without ceremony and objective acceptance.
The Core Mindset: Value, Testability, and Evidence
Volere opens with pragmatic truths:
Stakeholders won’t hand you “the answer”.
An orderly but adaptable process beats improvisation.
Iteration doesn’t excuse not understanding.
Anything unmeasurable isn’t a requirement.
You’ll convert events → BUCs → PUCs → testable requirements.
Two tiny fields do heavy lifting:
Fit criterion = the measurement that proves a requirement is satisfied.
Rationale = the “why” behind the requirement.
Together, they anchor decisions to value and testability from day one. When every item carries a fit criterion and rationale, reviews speed up, “done” stops being negotiable, and acceptance turns into numbers, not hand‑waving.
Want to learn more?
Check out the Courses, Follow us on LinkedIn, and Explore the Guide
