Flag deep dive: Planned hours exceeded for build issue

Modified on Tue, 4 Mar at 4:43 AM

When to use this Flag?

Leverage this flag to get an understanding of all the build issues in active sprint where the effort estimation has exceeded beyond the planned estimate.


Impact:

Process

Classification:

Effort

Tools:

Atlassian Jira

Intent:

The intent of this flag is to connect to the project management tool (e.g. Jira), unearth all the build issues that are being executed  which have exceeded the planned effort estimation; getting a comprehensive view of Planned Vs. Actual enables the team to arrive at the right velocity for the team. 

As a secondary benefit, this flag will also help Engineering managers/leads to manage the quantum of work allocated to team members effectively (to avoid overloading).


Configuration:

  1. Select the issue types that must be used to compute this flag.
  2. Set-up thresholds for effort breach for build issues in active sprint, this includes threshold breach for low/medium priority issues & threshold breach for high priority issues.
  3. 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