Requirements Management

Define requirement lifecycle, review states, and traceability practices.

Overview

Requirements Management controls how scope is captured, reviewed, changed, and reported. A consistent lifecycle reduces rework and improves auditability.

Key Concepts

• Lifecycle: status and review stages for requirements
• Acceptance criteria: objective conditions for validation
• Traceability: links to tasks, tests, and artifacts
• Change control: modification and rejection patterns that preserve context

How It’s Used

Use this structure for weekly scope reviews. Use it for approval workflows and change control.

Benefits

• Reduced rework from unclear scope
• Cleaner approvals through standardized review states
• Faster impact analysis through traceability

Setup Steps

1

Define statuses and meanings

Standardize requirement statuses across Projects. Use a small set of review states for approvals.

2

Standardize review views

Create shared Save Views for repeatable scope reviews.

• Requirements View

3

Define modification and rejection patterns

Use controlled change patterns to preserve context and downstream alignment.

• Requirements Modification
• Requirements Rejection

Best Practices

• Require acceptance criteria for approval-ready requirements.
• Link tasks and tests to requirements early.
• Use Segments and Processes for reporting consistency.

Summary

Requirements Management standardizes scope lifecycle and change control. Save Views and traceability support repeatable review and governance.

Related:

• Requirements
• Create and Assign Tasks
• Linking Tests to Requirements