Changing requirement statuses
The portfolio/program manager assigned can move the requirements of the portfolio/program to different statuses throughout its lifecycle.
To change a requirement status
- Log in to the Portfolio Management application.
- Navigate to Portfolio/Program console and click the required portfolio ID to access the portfolio/program.
- On the portfolio/program details page, go to the Requirements tab and click the required requirement ID.
- On the requirement details page, click Edit.
Select the required value in the Status field. The following table lists the required status change based on actions you can perform on a requirement:
From status
Action
Change to status
New
The requirement has been discussed and assessed.
A new task can be created from the requirement in a project of the portfolio/program, then the requirement is moved to In Project automatically. If the task related to the requirement is cancelled, the requirement is moved to In Backlog automatically.
In Backlog
The requirement implementation is blocked temporally because:
- Architectural Hold.
- Idea Contributor Discussion.
- Other Portfolio Activity.
- Skill Availability.
- Technical Hold.
- Third-Party.
Status Reason required to move this status.
Pending
Scope, change, risk and the value of missing functionality have been discussed, and the requirement doesn't meet the needs of the customer.
Cancelled
The requirement meets the needs of the customer but it is not possible to implement it because of budget reasons or duplicated.
Status Reason required to move this status.
Rejected
In Backlog
The requirement has been implemented and it was not necessary to create a task in a project of the portfolio/program.
Delivered
The requirement implementation is blocked temporally because:
- Architectural Hold.
- Idea Contributor Discussion.
- Other Portfolio Activity.
- Skill Availability.
- Technical Hold.
- Third-Party.
Status Reason required to move this status.
Pending
Scope, change, risk and the value of missing functionality have been discussed, and the requirement doesn't meet the needs of the customer.
Cancelled
The requirement meets the needs of the customer but it is not possible to implement it because of budget reasons or duplicated.
Status Reason required to move this status.
Rejected
Pending
The requirement is unlocked.
A new task can be created from the requirement in a project of the portfolio/program, then the requirement is moved to In Project automatically. If the task related to the requirement is cancelled, the requirement is moved to In Backlog automatically.
In Backlog
Scope, change, risk and the value of missing functionality have been discussed, and the requirement doesn't meet the needs of the customer.
Cancelled
The requirement meets the needs of the customer but it is not possible to implement it because of budget reasons or duplicated.
Status Reason required to move this status.
Rejected
- Click Save.