Requirements Management

Features

Industries

Reference

More

Start now
  1. Requirements Management
  2. Process
  3. Verification and change review
Process · Verification and change review

Verification and change review

Verification findings and change impacts are linked to the project. They help the team decide whether work is ready to accept and what a change means for schedule or effort. The owner and status of each concern should show its current next action.

Start now Download Proto

Step by step

  1. Verify delivery QA Engineer

    QA Engineer records an open finding with title, severity, project, reporter note and owner when a check exposes a problem.

    • Creates a project-linked finding with severity and owner.
    • Updates Verification findings, Projects

  2. Investigate finding QA Engineer

    The owner moves the finding through triaged and in progress while working on it; QA Engineer verifies a fix before closure.

    • Tracks investigation, fix and verification status.
    • Updates Verification findings, Team members

  3. Assess change Project Manager

    Project Manager records a change impact with category, probability, impact and mitigation, linked to the affected project.

    • Records the impact category, likelihood, effect and mitigation.
    • Updates Change impacts, Projects

  4. Track response Project Manager

    Project Manager monitors the impact until mitigation is complete or the concern is closed. A changed acceptance expectation returns to the requirement and baseline review.

    • Keeps the project concern current and revisits affected scope.
    • Updates Change impacts, Requirements, Baselines

Where it usually breaks

And how to keep it from happening.

  • A finding has a severity but no owner. Assign it before the next review so there is a person to act.
  • A fixed finding is assumed verified. QA Engineer should check the result and record the verified state.
  • A change impact has a risk rating but no mitigation. The Project Manager should record the planned response, not just a score.
  • Scope changes while an older baseline is awaiting review. Revisit the requirement revision and baseline before accepting the wrong version.

Who does what

Roles and permissions
QA Engineer
Records and checks findings; Project Manager assesses impacts; Delivery Lead reviews project exposure; Business Analyst revises affected requirements.

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