How 'Resource Allocation' report values are calculated in Jira Align

Summary

This article explains how the Resource Allocation (aka program increment allocation) report values are calculated in Jira Align.

• This report provides a roll-up by team members, of story ownership and task and defect allocations across a selected PI.

• It can be used to understand if team members are being over-utilized or under-utilized during a PI.

Solution

Pre-requisites

1. Team Members should be assigned for the Sprints.

2. Team members should have allocation defined in the Sprints.

3. Maximum burn hours should be specified in the sprint.

4. Stories and their respective tasks should be assigned to the team members for each sprint.

5. Effort hours should be added to the Tasks.

Calculations Overview

For a specific Sprint:

1. Hours: Planned / Actual

   1. Planned hours come from the Sprint associated with the PI's member allocation (Task hours planned for the members * No.of days in Sprint)

   2. Actual comes from the effort hours logged on the task associated with the stories.

2. Allocation: Planned / Actual

   1. Planned comes from the member allocation values in the Sprint associated with the story

   2. Actual Allocation = Total effort hours in the task /(max burn hours*no.of.days of the Sprint)*100

3. Defect Hours: Planned / Actual

   1. Same as Tasks.

4. Defect Allocation: Planned / Actual

   1. Same as Tasks.

Overall Report: The sum of all the sprint values should be reflected in the overall report value.

Calculations Explained

Programs > [PROGRAM] > Reports > Resource Allocation

For ease of understanding, we have taken 2 Sprints and 3 team members under a specific Team and performed only task calculations.

Step 1: Filter by Sprint by clicking on Extra Configs and choosing a specific Sprint as shown below > Click Apply.

Step 2: Report Values now reflect only for the specific Sprint (SivaRPPI SRP SRP1).

Step 3: Navigate to the Sprint chosen (example = SivaRPPI SRP SRP1).

Step 4: Find the Tasks associated with the team members for the respective Sprint Stories. This can be done in 2 ways.

• Click on the Story link associated with each member from the report and check their tasks.

• Navigate to Items > Tasks and filter by PI and Sprint(SivaRPPI SRP SRP1)

Calculations For Sprint (example = SivaRPPI SRP SRP1):

1. Planned Task Hours= Task hours planned for the members*No.of days in Sprint

   1. Siva- Program Manager Test: 3 * 5 = 15

   2. Siva- Super Admin Test: 4.2 * 5 = 21

   3. SivaShanmathi A: 6 * 5 = 30

2. Actual Task Hours= Effort hours logged on the task associated with the stories.

   1. Siva- Program Manager Test (SP): 4

   2. Siva- Super Admin Test (SS): 3

   3. SivaShanmathi A(Pic): 2

3. Planned Task Allocation: Member allocation values in the Sprint associated with the story

   1. Siva- Program Manager Test: 50%

   2. Siva- Super Admin Test: 70%

   3. SivaShanmathi A: 100%

4. Actual Task Allocation= (Total effort hours in the task /(max burn hours*no.of.days of the Sprint))*100

   1. Siva- Program Manager Test: 400 / (6 * 5) = 13.33 ie. 13%

   2. Siva- Super Admin Test: 300 / (6 * 5) = 10%

   3. SivaShanmathi A: 200 / (6 * 5) = 6.66 ie. 7%

Calculations For Sprint (SivaRPPI SRP SRP2):

Repeating steps 2-4 for Sprint SivaRPPI SRP SRP2:

• Report Values:

  

• Sprint Details:

  
  

• Tasks Associated with Sprint's Stories:

  

1. Planned Task Hours= Task hours planned for the members*No.of days in Sprint

   1. Siva- Program Manager Test: 4.5 * 5 = 22.5 ie. 23

   2. Siva- Super Admin Test: 3.3 * 5 = 16.5 ie. 17

   3. SivaShanmathi A: 5.4 * 5 = 27

2. Actual Task Hours= Effort hours logged on the task associated with the stories.

   1. Siva- Program Manager Test (SP): 0

   2. Siva- Super Admin Test (SS): 0

   3. SivaShanmathi A(Pic): 0

3. Planned Task Allocation: Member allocation values in the Sprint associated with the story

   1. Siva- Program Manager Test: 75%

   2. Siva- Super Admin Test: 55%

   3. SivaShanmathi A: 90%

4. Actual Task Allocation= (Total effort hours in the task /(max burn hours*no.of.days of the Sprint))*100

   1. Siva- Program Manager Test: 0 / (6 * 5) = 0%

   2. Siva- Super Admin Test: 0 / (6 * 5) = 0%

   3. SivaShanmathi A: 0 / (6 * 5) = 0%

Overall Report Calculations:

• Even though there are 4 Sprints associated with this PI, there are only 2 Sprints that has the pre-requisites defined and hence other sprints won't be considered.

• Overall ReportValue:

  

• Overall Calculations= Sprint1 + Sprint 2 Values.

  1. Planned Task Hours

     1. Siva- Program Manager Test: 15 + 23 = 38

     2. Siva- Super Admin Test: 21 + 17 = 38

     3. SivaShanmathi A: 30 + 27 = 57

  2. Actual Task Hours

     1. Siva- Program Manager Test (SP): 4 + 0 = 4

     2. Siva- Super Admin Test (SS): 3 + 0 = 3

     3. SivaShanmathi A(Pic): 2 + 0 = 2

  3. Planned Task Allocation: Sprint Avg

     1. Siva- Program Manager Test: (50 + 75) / 2 = 62.5%

     2. Siva- Super Admin Test: (70 + 55) / 2 = 62.5%

     3. SivaShanmathi A: (100 + 90) / 2 = 95%

  4. Actual Task Allocation: Sprint Avg

     1. Siva- Program Manager Test: (13.33 + 0) /2 = 6.67 ie. 7%

     2. Siva- Super Admin Test: (10 + 0) / 2 = 5%

  5. SivaShanmathi A: (6.66 + 0) / 2 = 3.33 ie. 3%

References

Report article: https://help.jiraalign.com/hc/en-us/articles/115004909647-Program-increment-allocation