Requirements Management

Features

Industries

Reference

More

Start now
  1. Requirements Management
  2. Process
  3. Baseline review
Process · Baseline review

Baseline review

A baseline brings the revision, acceptance criteria and target date into one review record. Submission creates a trace of the version put forward. The Project Manager then reads that version and records the decision on the baseline.

Start now Download Proto

Step by step

  1. Prepare baseline Business Analyst

    Business Analyst names the baseline, links its project and parent requirement, adds acceptance criteria and records its revision and due date.

    • Sets the reviewed scope, criteria and target date.
    • Updates Baselines, Requirements, Projects

  2. Submit baseline Business Analyst

    Business Analyst sets the baseline to submitted. The submission action stamps the review time and writes an operation receipt with a stable key and expected revision.

    • Stamps the submission and records the expected revision.
    • Updates Baselines, Operation receipts

  3. Review baseline Project Manager

    Project Manager compares the submitted criteria with the requirement and supporting evidence, then approves or rejects the baseline and records the decision date.

    • Records the acceptance decision on the submitted version.
    • Updates Baselines, Requirements, Record attachments
    ApprovalA person approves before the work moves on.

  4. Resolve outcome Business Analyst

    Business Analyst responds to a rejection or uses the accepted revision to guide later verification. Pending and missed target dates remain visible for schedule review.

    • Returns rejected work for correction or continues delivery against the accepted scope.
    • Updates Baselines, Requirement items

Where it usually breaks

And how to keep it from happening.

  • The baseline points to a different project than its parent requirement. Check both references before submission.
  • The requirement changes after submission. Compare the expected revision on the receipt with the version the reviewer is asked to accept.
  • The acceptance criteria are too vague for the Project Manager to make a repeatable decision. Revise the criteria before submitting again.
  • A due date is treated as the approval decision. Keep approval and target-date outcome distinct on the baseline.

Who does what

Roles and permissions
Business Analyst
Prepares and responds to the baseline; Project Manager decides; Delivery Lead monitors due dates and exceptions.

Set up Requirements Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

Start now Download Proto

How to get started