Contract Requirement Lifecycle

The Requirement policy defines the lifecycle states of a contract requirement.

The Requirement lifecycle includes these states:

This page discusses:

Private

Contract Requirements are created in the Private state by the Leader or the Contracts Manager. The contract reqirement is not visible to others in the Private state. The Contracts Manager or the owner of the contract requirement can promote the contract requirement to the In Work state.

In Work

The contract requirement is validated. The Leader, Contracts Manager, or the owner of the contract requirement can promote the contract requirement to the Frozen state after it has been validated.

Frozen

The contract requirement is reviewed by those assigned in the approval route. Once it has been approved, the Leader or the owner of the contract requirement can promote the contract requirement to the Release state. The connected sub-contract requirements must be in the Release state before you can promote the contract requirement to the Release state.

Release

The contract requirement is valid and ready to be planned. A feature is created to satisfy the contract requirement. The Leader or the owner of the contract requirement can promote to the Obsolete state.

Obsolete

The contract requirement is complete and no longer needed.