It would be nice to have statusses like:
- In progress - requirement is being worked on.
- Approved - The key stakeholder has agreed to the requirement and the developer has agreed that it is possible to create
- Implemented - Code has been designed and is ready for review
- Verified - The requirement is tested and is functioning correctly
- Deleted - An approved requirement is deleted. An explanation is needed of why and by whom the decision was made to delete it.
- Rejected - The requirement is not approved. The why and by whom it has been rejected is relevant.
- Deprecated - The requirement is no longer in use and has been replaced by a new requirement.
Best answer by Anne BuitView original
The status will change to approved or disapproved as soon as the requirement is either approved or disapproved in a baseline. As long as the requirement has not been approved or disapproved in a baseline, the status will be new.
If the requirement name or description has been modified since this approval or disapproval, the status will be modified.
Over the last year, we've received a lot of input when it comes to the status of requirements. We have found no no middleground when it comes to the set of statuses.
One thing that's quite certain is that the requirement status will be split into two different statuses:
Keep an eye out for any blogs regarding requirements, as soon as we have the last details hammered out we'll share it with everyone.