Table of Contents
Each status is part of a structured workflow to track progress, ensure accountability, and facilitate communication across teams and with clients. Some statuses can be updated by adding the appropriate hashtag in the comments section of the requirement.
The ability to update the requirement status beyond Approved or Declined using hashtags.
Status Definitions
| Status | Definition |
| New Issue |
When a new requirement is identified and sent to the project team but not yet reviewed or assigned.
|
| Waiting for Customer |
Used when the project team is waiting for input or feedback from the customer before proceeding.
|
| Verified | The requirement has been checked and confirmed as accurate and complete by the team, ready for the next steps. |
| In Review (#InReview) | The requirement was declined and is undergoing internal review to ensure it meets the necessary criteria, scope, or standards before moving forward. |
| Pending | The requirement has been requested by the client but needs verification to ensure its within scope. |
| In Progress | The requirement is actively being worked on by the development or project team. |
| Ready for Approval |
The requirement is ready to be formally reviewed and approved by a stakeholder or client.
|
| Client Approved | The requirement has been formally approved by all stakeholders and is ready for the next phase of build completion. |
| Approved - In QA | The requirement has been approved and is now undergoing testing by the QA team to ensure it meets all acceptance criteria and is defect-free. |
| QA Completed - Ready for UAT | QA testing has been completed successfully and the requirement is now ready for User Acceptance Testing (UAT) by the client or end users. |
| In UAT (#inuat) |
The requirement is currently in the UAT phase, where the client or end users validate that it meets their expectations.
|
| UAT Passed (#pass) |
The requirement has successfully passed UAT and is ready for final deployment, with no further changes needed.
|
| UAT Failed (#fail) |
The requirement did not meet expectations during UAT and requires revisions or corrections before it can move forward.
|
| Canceled | The requirement has been canceled and will not be pursued, often due to a change in scope or priorities. |
| Blocked (#blocked) | The requirement is unable to proceed due to external or internal blockers, such as dependencies or waiting for input. |
| Change in Requirement (#change) |
The original requirement has changed, and the team needs to revisit it to incorporate new details.
|
Updating Requirement Status from the Requirement beyond Approved or Declined
Some statuses can be updated by including the relevant hashtag in the comments section of the requirement. Only designated approvers have the authority to approve or decline requirements. However, both approvers and non-approvers can update the requirement status beyond Approved or Declined by using the appropriate hashtags listed below.
| In Review | #review |
| In UAT | #inuat |
| Final Statuses (Note: Once a final status is entered, it cannot be updated further.) | |
| UAT Passed | #pass |
| UAT Failed | #fail |
| Blocked | #blocked |
| Change in Requirement | #change |
Contributing Guides
-
Video Recordings and Documentation: Implementation Services Training
- Comprehensive Guide to Creating, Reviewing, and Updating Requirements
