Requirement Lifecycle

The lifecycle of a requirement consists of the states shown below.

The Requirement lifecycle includes these states:

Propose

A Product Manager or Requirement Manager creates a new requirement either stand-alone or in the context of a product or feature, and defines use cases and test cases.

Approve

A Product Manager or Requirement Manager assigns the requirement for impact analysis and defines an approval route.

Validate

A Product Manager or Requirement Manager performs a gap analysis against existing products.

Review

The requirement is reviewed by those assigned in the approval route. Before a requirement can be promoted from the Review to the Release state, any subrequirements must be in the Release state.

Release

The requirement is valid and can be planned. A feature can then be created to satisfy the requirement. When requirements are promoted to the Release state, any unreleased parent products, features and requirements are connected to the new revision. Email notification is sent to the owners of the parent objects stating that the requirement has been replaced with its latest revision.

Obsolete

The requirement is no longer needed.