Settings estimates with story points

Estimating and managing time budgets



アトラシアン コミュニティをご利用ください。


This page refers to Portfolio classic plans. If you are currently running Portfolio 2.0, please check this link to access the latest page version.

Portfolio for JIRA allows estimation and forecasting to be performed using story points in addition to time. Since estimating in story points is done by team, configuration involves setting a velocity for each team in your plan. Teams that do not have a velocity selected will be automatically set to the default. 

Story points are inherently focused on scheduling and planning on a team basis. This means that adding team members is optional since planning can be accomplished by simply creating teams and setting their velocities. 

See Synchronization settings for information on how to setup your plan and project(s) for syncing and Publish updates to linked projects for instructions on how to update your plan and projects. 

Setting story point estimation

When creating a new plan you can set it to story points by default, or select story points in an existing plan: 

  1. Go to your plan via Portfolio (in header) > View Portfolio > click your plan.
  2. Click more () next to the plan name > Configure > Scheduling.
  3. 見積タブをクリックします。
  4. In the Estimation Statistic field, choose story points.

See Plan Templates for more information on how to set up a plan.

Planning at the team level

Scrum methodology suggests that when you plan with story points that you should focus capacity planning on the velocity of the complete sprint. This means that determining the velocity of individual team members is not required because the velocity of the team as a whole specifies the number of story points that can be scheduled into each sprint. Planning at the team level works well if the team is stable and has a predictable velocity. 

Setting the team velocity 

You can set a velocity as a fixed number or based on a team's previous sprints. 

Set the default velocity

The default velocity is what is set if you don't specify a velocity for each team. We highly recommended that you customize the velocity for each team since velocity is a very team specific metric.  

However, if you still want to customize the default velocity for all teams:

  1. Go to your plan via Portfolio (in header) > View Portfolio > click your plan.
  2. Click more () next to the plan name > Configure.
  3. Click Scheduling.
  4. Enter a numeric value for the default team velocity in the Default velocity field.

Set team velocity using a fixed variable 

  1. Select People from the top navigation bar.
  2. Select and enter a velocity value for the team in the Velocity field. 

Setting velocity based on previous sprints

In addition to entering a fixed value for the team's velocity, if your plan is synced with a JIRA Software project(s), you can obtain an average of the previous 5 sprints for that team and use that value as the team's velocity.

 To set team velocity based on previous sprints: 

  1. Select People.
  2. Select the velocity field.
  3. In the velocity drop-down menu, select Set based on previous sprints.
  4. Select a board from the list to display a list of (up to) previous 5 sprints and the recommended velocity based on the average of those sprints. 
  5. Select Import.

Account for velocity change over time

The amount of work a team can accomplish will change over time. By working together and completing sprints, a team's velocity will ideally increase over time.  Portfolio for JIRA gives you the ability to set a value to adjust the team's velocity in subsequent sprints.  For instance, you may set your team's velocity to 20. You may also assume that over time your team will be able to complete 2 additional story points per sprint. Entering the value '2' in the 'Velocity change' field will increase the velocity of that team by 2 after each sprint. 

To set automatic velocity adjustment: 

  1. Select People.
  2. Select the velocity field.
  3. In the velocity drop-down menu, enter a figure in the Velocity change field. The adjusted forecasted velocity in future sprints will be displayed in the bar graph. 

Planning with team members

If you want to account for individual team members varying availability (vacations, onboarding time, and others),Portfolio for JIRA supports modeling individual team members and adjusts the team velocity based on their availability. 

Adjusting team velocity based on member availability

You can adjust upcoming velocity based on the availability of team members. When this option is selected, Portfolio for JIRA will calculate the impact on the team velocity for any limited presence, absences, or weekly hours set in the team member's detailed dialog. The adjusted forecasted velocity for future sprints is displayed in the bar graph. 

Portfolio for JIRA makes the assumption that every resource (team member) contributes equally to the total team velocity.

例 1:

Team A has three team members and velocity of 100 points with one team member working half time. 

Team ADefault Weekly HoursAssumed contribution to team velocity
Jim40h40 ポイント
Meredeth40h40 ポイント
Olivia20h20 ポイント
合計100h 100 ポイント


Let's assume Meredith plans a vacation for 2 weeks during sprint 2, and Olivia will be away from the beginning of sprint 3. The projected velocities when using the automatic adjustment would be as follows: 


SprintSprint 1Sprint 2

Sprint 3

Sprint 4
ベロシティ100 ポイント60 ポイント80 ポイント100 ポイント

Meredith works full time, so we assumes she contributes 40 pts per sprint, her vacation reduces the velocity accordingly.

Olivia is on leave, but since she does not work full time, the velocity increases proportionally.100%

Accounting for stages and skills in story point mode

You can still use stages and skills when using story points. Again, the capacity that can be scheduled for a particular stage or skill into a sprint is computed relative to the member's default weekly hours. 

Scenario 1: 

Team A has 3 members and a velocity of 60 story points. With the assumption that everyone contributes equally to the team velocity, Portfolio for JIRA can determine the available capacity to schedule design and implementation work. In this example, during the sprint, design would be worked on until 20 points were completed. This would be followed by implementation being carried out for a maximum of 40 points.

Team BDesign実装Assumed contribution to team velocity



20 ポイント

20 ポイント

20 ポイント
合計20 ポイント40 ポイント60 ポイント

Scenario 2: 

In this scenario the team has 3 members and velocity is 100 story points. In this case, Olivia's hours for the sprint are limited to half time (20hrs a week). This means that her contribution to the relative velocity is halved.  

Team A可用性Design実装Available Velocity




合計 4060100

Best Practices

Adding a new team member when estimating in story points

When adding a new member to a team, there is normally an adjustment period that will affect the velocity of the team.  To compensate for this, we recommend adjusting your forecasted velocity to account these changes.  One way to do this is to add exceptions to the availability of a new team member to simulate the initial onboarding learning curve.  To do this: 

  1. Select People.
  2. Select the velocity field for the team with the new member and enter the velocity of the new target value (this would be the velocity of the entire team, with all members contributing at 100%).
  3. Check Auto adjust with team member availability to set the velocity to compensate for the new team member. 
  4. Add the new team member (if you haven't already, see Adding and configuring teams.
  5. Select details.  
  6. In the 'Availability in Team field', select Add exceptions
  7. Enter the timeframe and weekly hours for that time frame that you anticipate the new employee will be able to contribute. 
  8. Repeat this process until you reach normal working hours for a week (ex: 40h).
  9. Select X to close the details dialog.
  10. Return to the velocity drop-down for that team to see the impact the new employee onboarding has on the team velocity. 

Accounting for productivity levels

Ideally, on average, everyone on a team contributes equally to the velocity. However, you may want to account for the fact that some individuals contribute more and that their absence would reduce the velocity in a higher proportion. In this instance, you can adjust the default weekly hours for the team members to account for this difference. 

最終更新日: 2017 年 9 月 16 日


Powered by Confluence and Scroll Viewport.