After successful installation, you will be able to see “Capacity Tracker” icon on the left-hand side panel in JIRA. Please refer following step by step guide to start working with Capacity Tracker.
...
Step 1: Go to Capacity Tracker
...
Step 2: Select
...
iteration and start with configurations
If you have single period iteration (sprint/version) then it will be pre selected to get started. If you have multiple periods (sprints/versions) of those in the board , start with then select the most recent and active period(sprint/version) configurationor active iteration and start configuring it.
...
Step3: Set up appropriate permissions in order to edit configurations.
...
If Jira permission control is disabled or you already have appropriate permission granted, you will not see an error message and instead you will be able to click on “Edit“ and navigate to configuration page. For more details on permissions refer here https://inprowiser.atlassian.net/wiki/x/AQBAE
...
Step 4: Add or import users for tracking.
...
Once team members are added, you can do the following:
Assign role: you can select predefined roles or you can create custom roles
...
.
Define team members working days.
Add Days off the team members.
Configure their daily capacity. (Note: If the capacity type is selected as hours then the daily capacity will be represented as
...
hrs/day, if the capacity type is selected as Story Points then the daily capacity will be represented as
...
StoryPoints/day.
...
Step 6: Setup board configurations.
The board These configurations are global configurations settings for the board. These settings are applied They apply to all periods iterations (sprints/versions) in the selected project board.
Choose the capacity type as per your project needs and working practices. Ensure that they are aligned with your project and team’s estimations practices.
Setup Configure default working days for the entire team according to the company policyyour needs for the project board.
Add team holidays to account for general unavailability of team members for the selected perioditeration.
...
Save & Close after all configurations are set. You will be redirected to the Capacity Tracker list page.
...
| Info |
|---|
Please ensure Jira’s default time tracking feature is enabled. Estimation fields are configures in your project schemes and screens. Jira’s default Remaining Estimate field is used to estimate and track the remaining work. |
...
NOTE : Following details are going away. I have only kept them for reference here for the time being.
...
Key summary Steps
Pre-requisite Steps
...
...
Breakdown period stories into sub-tasks.
...
Estimate them with the Remaining Estimate field into person-hours or person-days. E.g. 3h or 1d
...
Assign stories and sub-tasks to team members.
...
Add and configure team members in Capacity Tracker.
Configuration Steps
Import or add users who supposed to work on the period.
Configure team members’ daily capacity. Most teams consider 6 to 7 hours as daily capacity, instead of 8 hours. This allow teams to discount the time spent on daily meetings, team discussions, and other non-productive hours. This is however up to users/teams to decide how many hours they want to configure as daily capacity for their project. In another example let’s say you have a team member who is only 50% available during the period and/or shared with another team. You can configure his capacity as 3-4 hours in order to indicate he is available partially.
19Defining roles, this is an optional, but can be useful to view an abstract capacity plan per role or skill level.
Configure days off, public holidays and working days.
Configure public holidays and weekly working days.
Set period start and end date for the future period. You don’t need to set this up for the current period as it refers it from the JIRA’s actual period dates.
Tracking Steps
View workload bar charts anytime during the Sprint and figure out work allocation issues.
You can drill-down work allocation through expandable bar charts.
You can click on the work items (stories/sub-tasks) and reassign them.
Edge cases and notes
Here are some edge cases that may prevents Capacity Tracker from working as intended and as a result you will not be able to view team capacity and workload bar charts as expected.
If users team members are not added and configured for the sprint. You will need to add users to plan their capacityiteration.
If your sprint iteration/board is blank/empty. i.e. You don’t have any stories or sub-tasks in it.
If you have not allocated the stories and sub-tasks to team members.
If you have not used the remaining estimate field to estimate the stories and sub-tasks of your project while your capacity type configured for hours based tracking.
If you have not used the default story points to size the stories in your project while your capacity type is configured for story points based tracking.
If you are working on a future perioditeration, but you haven’t configured start and end date.
If you are using custom fields for estimations.
Operational workflow and stage instructions
Stage 1: Beginning
You may have a blank period at the beginning. There are no stories or tasks planned yet, and user are not configured.
SCREENSHOT of backlog at Stage 1:
...
SCREENSHOT of Capacity Tracker at Stage 1:
...
Stage 2: Configuration
Still you haven’t planned any stories or tasks for the period, but you want to have an overview of team capacity.
Inputs/Recommended steps:
...
Add users through “Manager Users” functionality and configure their capacity, role and days off.
...
.
...
Outcome:
You will be able to view total team capacity (in person-hours) as well as you will be able to view capacity per role and for individual team members.
However, since the task remaining estimate field isn’t filled and allocations are due; it won’t show you work distribution.
SCREENSHOT of Capacity Tracker at Stage 2:
...
Stage 3: Planning
At this point, you have a rough capacity plan for your team. Teams usually work out story/task breakdown, estimation and work allocation during the sprint planning process. They can conduct these steps in any order. Also, it is not necessary to begin with stage 3 only after stage 2. Their order can be switched or executed in parallel. Users can start the sprint in JIRA with actual start and end date.
Inputs/Recommended steps:
Story breakdown into sub-tasks
Estimating sub-tasks into hours or days.
Allocation of stories and sub-tasks to team members.
Outcome:
Workload bar charts: Team can see the current capacity and work distribution across team members. This allow teams to calibrate and adjust work distribution for the optimal efficiency and outcome. Team can avoid situations where some team members are over or under.
a. RED bar chart indicates over-allocation or schedule slippage.
b. GREEN bar chart indicates work on track or free team capacity/bandwidth.Users can review capacity planner during sprint, monitor progress, identify risks, and resolve proactively.
Following are the SCREENSHOTS of sample sub-tasks, estimation and allocation.
SCREENSHOT1 (New Jira interface):
...
SCREENSHOT2 (Old Jira interface):
...
SCREENSHOT of Capacity Tracker at stage 3:
...
...