4. Managing your teams
- 1. Installing Portfolio for Jira
- 2. Preparing your planning environment
- 3. Creating plans
- 4. Managing your teams
- 5. Managing your releases
- 6. Working with your plans
- 7. Customizing your plans
- 8. Sharing your plans
Depending on how your organization is structured, the content on this page is meant for Portfolio for Jira administrators or plan owners.
To help you set your teams up for success, we've prepared this getting started guide that discusses how to set up Portfolio for Jira with your existing Jira instance.
The guide discusses the typical end-to-end path that users and administrators may find themselves taking part in when using Portfolio for Jira. You'll also find high-level content on concepts, as well as some recommendations and optional steps you can consider, as you flesh out your plan.
You can add Jira users as team members to your plans. For each plan, you can create new teams, choose the scheduling method for, and assign tasks to these teams as well.
Teams can be plan-specific or shared across plans. Plan-specific teams are called private teams in Portfolio for Jira, and these let you play around with what-if scenarios for plans that aren't formally established yet.
Before you begin, note that accessing the functionality of teams is different between plans with the improved interface and live plans (versions 2.0 to 2.27).
- Accessing teams in plans with the improved interface
You can access the functionality of teams via the teams view at the top left section of your plan.
- Accessing teams in live plans
You can access the functionality of teams via the teams tab at the top right section of your plan.
Whether you're using a live plan or a plan with the improved interface, you can perform the following basic team management tasks:
- Creating and deleting teams
- Editing and sharing teams
- Assigning work to teams
Best practices when managing teams
Once you've created your plan, we recommend to keep in mind the following best practices for your team configurations. Note that these are only recommendations, and your configurations should be aligned with how your teams work in your organization. In saying that, always keep in mind velocity and capacity metrics when you're setting up your teams.
- For Scrum boards, we recommend that you figure out the sprint velocity of your teams, and then manually input this when creating your teams. You can manually change this at any time, to account for any necessary changes later on.
- For Kanban boards, we recommend to set the average hours of work per week that the team gets through. Remember that this is just the average number of hours of work completed, which is not the same as the number of hours the team is at work.
When auto-scheduling a plan, individual capacity is calculated by dividing the weekly team capacity by the number of members. This applies to Kanban teams and Scrum teams that use time-based estimation.
Private and shared teams
Depending on how your teams work, you may want to consider creating shared teams in your plan.
A private team is sufficient if you're sure that the team will only be working on the issues covered in that plan. However, if you know that your Mobile development team will be working on issues in both iOS expansion and Android expansion plans, then making the team a shared one might be beneficial.
We also recommend using shared teams if you want to have the same team in different plans, for high-level planning. For example, your teams have their own plans, but you need a high-level department plan to get visibility across all teams. Ideally, you'd want to have the same shared team in both plans.
Using the team field in Jira
This pertains to the team custom field that comes from Portfolio for Jira, i.e. it's not one of the default fields that would readily appear in your Jira issues. We recommend that you make the team field display in your issues for visibility, so you can set the team field when editing or creating issues in Jira. Any assigned teams in your plans will also surface in the corresponding issues in Jira.
You can also use the team field as a quick filter — perhaps filter for work at the epic hierarchy level of your board, so you can quickly show how work is distributed across multiple teams.