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.
...
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.
...
| 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. |
...
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.
If users are not configured for the sprint. You will need to add users to plan their capacity.
If your sprint 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 of your project while your capacity type is configured for story points based tracking.
If you are working on a future period, but you haven’t configured start and end date.
If you are using custom fields for estimations.
...
NOTE : Following details are going away. I have only kept them for reference here for the time being.
...
Key summary Steps
Pre-requisite Steps
The basic unit of all measurements and presentation in Capacity Tracker is the person-hours, it is essential that users have time tracking on and tasks are estimated.
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.
...
If users are not configured for the sprint. You will need to add users to plan their capacity.
...
If your sprint 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.
...
If you are working on a future period, but you haven’t configured start and end date.
...
.
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 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.
...
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.
...