Requirements Management

Features

Industries

Reference

More

Start now
  1. Requirements Management
  2. Process
  3. Project and requirement setup
Process · Project and requirement setup

Project and requirement setup

A project starts with a known organization, owner and schedule. The Business Analyst then records individual requirements under that project. These links let the team review scope and revisions without confusing work from different engagements.

Start now Download Proto

Step by step

  1. Set project context Project Manager

    Project Manager records the project name, organization, owner, delivery method and planned dates. The project begins planned and moves to active when delivery starts.

    • Links the engagement to its organization, schedule and owner.
    • Updates Organizations, Projects, Team members

  2. Register requirements Business Analyst

    Business Analyst adds each requirement with a clear name, description, owner, revision and project reference.

    • Gives each requested outcome a project, owner and revision.
    • Updates Requirements, Projects

  3. Break down work Business Analyst

    Business Analyst creates requirement items, sets priority and estimate, and names an assignee for each piece that is ready to work.

    • Makes smaller delivery work assignable under a parent requirement.
    • Updates Requirement items, Requirements, Team members

Where it usually breaks

And how to keep it from happening.

  • A requirement is entered under the wrong project. The Project Manager should check the project before a baseline or time entry is added.
  • A requirement is marked in progress without an owner or clear description. The Business Analyst should make the requested outcome understandable to the assigned team.
  • Items are created without their required parent requirement. The parent link is what lets later work and time be traced back to scope.
  • Dates mean different things across projects. Agree whether they describe delivery work or review targets before using the schedule for commitments.

Who does what

Roles and permissions
Project Manager
Owns project context; Business Analyst owns requirement detail; Team Member takes assigned items; Delivery Lead reviews cross-project 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