View in Atlassian Marketplace
This guide is for Jira Administrators to install the Sprint Capacity Planning & Tracking Cloud app.
| Child pages (Children Display) |
|---|
Configuration Overview
There are a few configurations a Jira administrator is required to perform in order to get Sprint Capacity Planning & Tracking ready for work. These include setting Roles, which are used to decide teams to disciplines, defining Global Teams that can be reused in sprints, selecting several toggles according to the desired functionality, etc.
...
Configuration menu should then appears in the left bar.
...
Teams and Roles Page
This configuration pages deals with the following.
Global Teams
The Sprint Capacity Planning & Tracking app uses two types of teams, which are app specific and not used by Jira itself: Global Teams (set here by an Administrator, and can be used multiple times in multiple projects and boards), and Board Teams (set by the planner, specific to a Board).
Teams are used for planning and tracking sprint work. They group resources (team members) with their daily development capacity. For example, team Cloud may group four resources (members), each with a planned capacity of 8 hours per day (or story point count, if your process uses those), where two resources are assigned the role of Developer, one the role of QA and the last the role of Design.
To provision Global Teams:
Click on the app admin menu option Teams and Roles
Click New Team → Create.
In the dialog enter a name for the team.
Click Add.
You can now add (+Add Participant), modify and remove (trash can icon) members in the global team.
For each resource in the team you can set daily commitment, representing the work capacity of that person in hours and/or story points. You can also set a role for the resource.
...
Roles
The roles are available later to be assigned to sprint participants. This allows you later to review planning and tracking information by the roles you defined.
For example, a team named “Front End”, can have members with roles such as “Designer”, “React Dev”, and QA. When you analyze resources for a specific sprint, you can view planning information by roles, to refine your insights about the your plan. Note that you can define as many role as you need, and that they are not connected to other grouping definition within Jira.
To provision Roles:
Click on the app admin menu option Teams and Roles
Find the section Roles Configuration
In the Roles box, type a name of a role. You can add as many as you want. Note that, as roles are labels, no spaces are allowed within a role name (the order of roles in field is also the drop-down roles order when a team member is assigned a role; First role in in the field will be shown on top of the list (and also be the default role).
When you are done with role modification, click Save.
...
Sprint Planers
here you can select Jira Groups as well as individual users who are allow as sprint planners. They will have the ability to add, modify and delete sprint teams.
To provision Sprint Planners:
Click on the app admin menu option Teams and Roles
Find the section Sprint Planner Configuration
Select Jira Groups and Users which are authorized as planners
...
Setup and Migration Page
Story Points
This setup allows you to decide how issues are defined as completed. When an issue is completed, their story points are considered as value earned. When tracking they will be counted as delivered. The accounting can be done through Jira issue Done status, through issues added with a resolution or done; or only to issues that were associated with a resolution.
To select the needed Story Point setup:
Click on the app admin menu option Setup and Migration
Find the section Story Point Configuration
Select your option
...
Issue Changes during active sprint
This setup allows you to control how strict you are in sprint planning. You may want to prevent your planner from changing sprint commitments AFTER the sprint was launched. With this state, changes that are done in effort during the sprint will not be accounted for in tracking metrics. Alternatively, you may allow in-sprint effort updates, as the team learns about them.
Note: In the default setting Freeze estimation at sprint launch of the app, issue estimations are frozen at the moment a sprint becomes active. If estimations are changed during the sprint, that change is not taken into account (as this is post “planning”). This will be perceived as a difference between the changed, new, effort of issues, and the values in the tracking panel - which can be confusing.
...
Note: When an issue is (removed and added) to an active sprint, the modified issue is taken in account with its lates effort value. This will resync the tracking calculation.
Virtual Expert
This option allows you to enable (default) or disable the Virtual Expert feature.
...