Flags deep dive: Build not planned for completed requirements

Modified on Mon, 3 Feb at 12:35 PM

When to use this Flag?

Leverage this flag to get visibility on completed requirements that are not planned for build.


Impact:

Process

Classification:

Requirements

Tools:

Atlassian Jira

Intent:

The intent of this flag is to connect to project management tool (e.g. Jira), unearth all the requirement stories that are completed but not planned for build. There could be valid reasons for not taking all the requirements into build but there is a good chance that it was completely missed by the Scrum team; this flags allows the team to align & leverage completed requirements for build. 

The Engineering manager/lead in alignment with the Product lead can move relevant items to Jira for execution.


Configuration:

  1. Define the age of the completed requirement issue e.g. flag when the requirements are closed beyond the configured threshold.
  2. Enable this as a compliance flag if you think this can have an impact on your internal or external regulations; this will ensure the visibility of all the artefacts violating this flag in the compliance status report.



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article