Jira Portfolio for Project Managers teaches you everything that you need to know to use Portfolio for Jira with your scrum and kanban boards, issue filters, and projects. You build a plan, modify and analyse it, and learn every feature that is available in Portfolio for Jira. This combination of video lectures and hands-on activities doesn't require Jira administration permissions, so if you are a project administrator and can create Portfolio plans, then you're ready to begin today.
Learn about the function and purpose of Jira Portfolio in relation to agile project management, Jira Core, and Jira Software. We also teach about the iron triangle of project management and the philosophy that drives Jira Portfolio and its calculations.
Introduction to Portfolio
Jira Portfolio's Methodology and the Iron Triangle
Global Setup and Permissions
In reviewing the organisation of Jira Portfolio, you learn how all of its settings are interconnected and how almost everything needs to be configured before it can really work well for you. We teach you about all of the configuration options and what you need to think about for your settings. This chapter does not cover configuration that is only accessible to Jira Administrators. The course Jira Portfolio for Jira Administrators cover those settings.
How Portfolio is Organized
Configuring Your Portfolio Plan
Sourcing and Portfolio Permissions
Building Scope in Portfolio
In this chapter, you learn how to build the scope for a Portfolio plan and conduct advanced scope management including setting dependencies, default estimates, how to override defaults, create issues directly from Portfolio, and more. You also modify the display of the plan to suit your needs and add initiatives for higher level planning and reporting. Lastly, we talk about three different ways to approach building your scope so you can decide which is right for you.
Defining Your Scope
Advanced Scope Management
Initiatives in Agile Portfolios
Three Approaches to Scope Development
We start with how releases are used in Jira without involving Portfolio, and the limitations of releases in Jira Core and Jira Software. We will teach you how to use Portfolio to create releases and associate issues with them and then dive into Jira Portfolio's cross-project release capabilities. We also discuss the difference between scheduled and fixed-date releases in Portfolio and help you to understand the differences between them and how they impact your schedule.
How Releases Are Used in Jira
Building Releases Using Jira Portfolio
Teams of People Working in Stages With Their Skills
Jira Portfolio's resource management can be confusing because of its multiple layers. We start by helping you understand how Jira Portfolio uses the scheduling and skill information that you provide, and the limitations inherent in Portfolio for schedule management. In addition to teaching you all of the configuration and capabilities of the Teams menu, we also cover four options for handling the team configuration and the best practice that works for many companies.
The Strengths and Weaknesses of Jira Portfolio's Teams Functionality
Building and Managing your Team in Portfolio Plans
Building Stages and Skills in Portfolio Plans
Sharing Teams and Skills Globally
How to Use Stages and Skills
Visualizing What-if Scenarios
Now that Portfolio is all setup how we need it, we can begin to get value from it and experience the benefits of what-if analysis. In this chapter, we teach you about how to modify key pieces of information in your scope and team plans and analyse the impact on your schedule for priority and capacity planning. We cover what can and cannot be changed to test what-if scenarios, and teach you how to commit or revert your changes.
Introducing What-if Analysis with Scenarios
Committing and Reverting Changes
Reporting with Jira Portfolio
In the final chapter of Portfolio for Project Managers, we review Portfolio's built-in reports, and also teach you how to use Portfolio to generate reports for your executives and stakeholders. You learn how to interpret what Portfolio is telling you, and how to communicate those results to agile team members, other project managers and scrum masters, executives, and external stakeholders.
Configuring and Interpreting Portfolio Reports
Creating a Program
Portfolio Reporting to Scrum Masters / Project Managers