Requirements Modification

Update requirements while preserving change history and approval intent.

Overview

Requirements change as discovery and design progress. A controlled modification approach preserves context and auditability.

Key Concepts

• Change intent: why a requirement is changing

How It’s Used

Use modification when scope changes or wording needs clarification. Use it to update acceptance criteria and linked artifacts.

Benefits

• Reduced rework through clear change communication
• Better auditability through explicit change history
• Faster impact analysis across linked work

Setup Steps

1

Locate the requirement

Open Requirements. Find the requirement using Global Search or filters.

2

Update the requirement

Update title, description, and fields. Update acceptance criteria when the expected outcome changes.

3

Validate links

Review linked tasks, tests, and artifacts. Update links when scope boundaries changed.

4

Move back into review

Set status to an in-review state when approvals are required.

Best Practices

• Capture rationale in comments for high-impact changes.
• Avoid changing meaning without updating acceptance criteria.
• Re-run testing coverage checks after major changes.

Summary

Requirements Modification supports controlled scope change. Links and review status keep delivery work aligned.

Related:

• Requirements
• Linking Tests to Requirements