Requirements View

Review requirements with consistent columns, filters, and Save Views.

Overview

Requirements View is the primary list view for reviewing scope. A stable view reduces review churn and improves reporting consistency.

Key Concepts

• Save View: stored configuration for repeatable review lists
• Columns: fields used for triage and reporting
• Filters and grouping: focus reviews by status, owner, process, or segment

How It’s Used

Use a default Requirements View for weekly scope reviews. Use dedicated Save Views for approval, change control, and delivery readiness.

Benefits

• Faster triage during scope reviews
• More consistent reporting across Projects
• Reduced rework from inconsistent filtering

Setup Steps

1

Open Requirements

Navigate to a Project. Open Requirements.

2

Configure columns

Show fields used for scope reviews. Typical fields include Status, Owner, Process, Priority, and Due date.

3

Create Save Views

Create Save Views for repeatable reviews, such as Requirements — In review and Requirements — Approved.

Best Practices

• Keep shared Save Views stable.
• Duplicate shared views before major changes.
• Use consistent naming patterns across Projects.

Summary

Requirements View standardizes how scope is reviewed. Save Views provide repeatable review lists.

Related:

• Filtering and Sorting Data
• Save Views and Templates