Flags deep dive: Members in active sprint are overloaded

Modified on Tue, 4 Mar at 8:25 PM

When to use this Flag?

Leverage this flag to get an understanding of all members who are overloaded either based on effort estimates or number of assigned issues.


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 members in a sprint who are overloaded either based on computed effort estimates or based on number of issues assigned to a member. This flag will help the Engineering lead/manager to a better view on members who are overloaded (based on data extracted from all the sprints currently active in the connected projects/epics in the Jira configuration).  


Configuration:


  1. Select the effort calculation model (estimates or issue allocation). 
    1. Note: the estimation based assessment is based on the capacity per day (from work hour settings in the workspace).
  2. Define the type of sprints to be monitored by the platform (active sprint, planning sprint or all types of sprints).
  3. Enable auto-resolution settings and select "notifying via email" as the option, this will ensure that the platform automatically notifies the admins of the workspace as soon as this issue is discovered.


Note: Maintain the work hours per day in the work hours settings (Workspace settings):

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