Portfolio

  • The portfolio is built for the agile project management.
  • The portfolio is developed by an Atlassian Inc.
  • It is developed to roll up multiple teams and projects into one portfolio-level view.
  • Portfolio provides correct view for planning and managing large work across multiple teams and projects in JIRA
  • User defined priorities can be set to make trade-off decisions so user can answer the ‘what-if’ questions and instantly see the impact in the plan
  • Set business goals and track progress to make sure, user execute on user strategy
  • JIRA Portfolio is available as an add-on for JIRA Server and JIRA Cloud

 

Features

  • Basic Data-driven agile roadmaps

The portfolio helps the user to organize and prioritize their work. It provides, builds a realistic roadmap that spans multiple teams and JIRA projects. “JIRA schedule viewprovides an easier view of scope and target release dates.

 

  • Estimation correlation

With Portfolio for JIRA, the user can estimate target start and end dates for long term plans based on user team’s velocity. It provides the user, the original estimates and current estimates that help them to understand team’s performance.

 

  • Multiple scenario planning

Portfolio for JIRA provides multiple scenario planning features that allow the user to select, save and compare the different scope and team combinations, so they can pick the best portfolio plan for their teams.

 

  • Resource and capacity planning

Assign and schedule the right resources for each team and take into account their skill sets and availability. The user can even add potential new team members or contractors as virtual hires to see the impact on the team’s velocity.

 

  • Real-time prediction

Portfolio dynamically loads all the Epics/Stories from JIRA software with which it is integrated. Due to this, plans are always up-to-date which facilitates the user to track the progress of releases and team capacity/activity.

 

  • Roll-up reporting

Portfolio analyzes different aspects of user’s plan whether it be by scope, capacity, releases, schedules, sprints or themes. It provides roll-up reporting, cross-team, and cross-project visibility so that everyone is on the same page.

 

Configuration of Portfolio

Plan configuration

The option for plan configuration is next to the plan name.

 

A user can customize portfolio plan as per his/her requirements. A user can add stages and skills as per project requirement also user can adjust the percentages that will be applied to each work stage of your plan and clicking on a particular skill will display its percentage breakdown for a user to adjust.

While plan configuration, under scheduling option user will decide whether it days, hours or story points.

 

Figure 2: Plan configure view

 

Scope

Scope displays stories and epics which are imported from JIRA software, a user can import selected stories and epics as per need, also exclude particular story or epic from the scope. JIRA portfolio provides an option to create story or epic and assigns to the users. Estimates for particular story or epic can be set from here. While working on multiple projects, a user can narrow his/her selection by using the filter available for projects. Below plan filtered by a release.

Figure 3: Scope view
 

 

Manage Teams and team members

Teams tab provides user to create team or group of teams working on projects with respect to the project plan goals. The user can select skills of a particular user from here.

Only the user with an administrative access can make changes in portfolio also to see the details of each member, user need to click on his/her name

 

Figure 4: Team view

 

Releases

Releases tab provides an option to build and fill out releases. The user can create a release for single project or cross project. Cross project release can be shared with multiple projects. The user can set release date dynamic or fixed. In a dynamic release, the user doesn’t need to specify release date but in fixed release user need to specify a start date and release date.

Figure 5: Release View

 

Reports

Reports section provides us different types of views depending on the drop-down options selected by a user. By default “Themes” is displayed under Report, here target and estimate can be set by the admin. Actuals are displayed here whenever the team updates worklog. Themes provide Pie chart representation using target, Estimate and Actual which helps to track the project progress. Similarly, other report options can be utilized for a different version of displays.

Figure 6: Reports

 

Conclusion

From above configuration, a user can start to create the first project plan. A portfolio provides a better way to handle multiple projects in a single plan. The user checks/modify/update estimated time to complete release of different projects, assign multiple members on a single story or epic and extract reports.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>


CAPTCHA Image
Reload Image