Add Your Heading Text Here
Requirements baseline
A requirements baseline is a reviewed and approved set of requirements, frozen at a point in time to serve as the agreed reference for the work ahead. Once baselined, requirements only change through a controlled process, which gives the team a stable foundation to design, build, and test against instead of a moving target.
What it means
Without a baseline, requirements quietly drift. Someone tweaks a line, a stakeholder adds a 'small' extra, and soon the version being built no longer matches the version that was agreed. A baseline draws a line in the sand: this is what we committed to. Any change after that is visible, discussed, and recorded, rather than slipped in unnoticed.
Baselines matter most where change has to be justified, which is exactly the case in regulated development and any project with formal scope. They also make impact analysis possible, since you can compare what changed against a known starting point. Native Azure DevOps has no true baselining, so teams that need it turn to tools like Modern Requirements to capture and version baselines around their work items.
In practice
An automotive team baselines its requirements before starting a development phase. Three weeks in, a supplier requests a change to a sensor interface. Because there is a baseline, the team can see exactly what the change touches, weigh it through change control, and keep a record of what moved and why, rather than discovering the drift at integration.
Foire aux questions
What does it mean to baseline requirements?
Why is a requirements baseline important?
Manage requirements the modern way
Modern Requirements brings documentation, traceability, and reviews together inside Azure DevOps.
