Configuring team settings
This page discusses the usage of Portfolio for Jira live plans (any version from 2.0 to 2.27). If you're using the redesigned planning interface, see this page instead.
You can configure the scheduling methodology, and the velocity or the weekly capacity of the teams associated with your plan.
Configuring the scheduling methodology of a team:
- Go to your plan via Portfolio (in header) > View Portfolio > click your plan.
- Click the Teams tab to display the teams section below the timeline.
- In the Teams section, find the team whose settings you want to configure, then expand the team to view its details.
- From the upper-right section of the selected team, click the scheduling methodology menu.
- Select from one of the following methodology options:
- Scrum, if the team works in sprints or fixed iterations, then specify the number of weeks that comprise a sprint. If you want to define the default value for your sprints, see Configuring scheduling settings.
- Kanban, if the team works in a continuous schedule.
If your plan uses story points for estimation, the Kanban option won't be available. See Configuring scheduling settings to know more about changing the planning unit of your plan.
- Commit the changes back to your Jira instance.
Configuring team velocity
If you're using story points for estimation, you will see the following details about your team:
| 1 | Team velocity |
|
|---|---|---|
| 2 | Forecasted velocity | The team velocity that's forecasted for the next few sprints, based on:
|
| 3 | Past velocity |
|
Configuring weekly capacity
If you're using time-based estimates, the weekly capacity of your team is the total sum of the weekly hours of each team member. You can configure the weekly hours of each member in your team, to get your team's overall weekly capacity.
To configure weekly hours of a team member:
- In the Teams section, from the Weekly hours column, click the row of the team member whose hours you want to configure.
- Enter the weekly hours for the member.
- Commit the changes back to your Jira instance.
Related topics
Last modified on May 23, 2019
Powered by Confluence and Scroll Viewport.