Transform your product management workflow with Jira Product Discovery, the dedicated hub for product teams to capture ideas, prioritize features, and align stakeholders. 

Jira Product Discovery is a dedicated tool for product teams to capture ideas, prioritize features with data, and build visual roadmaps that align stakeholders.

An Idea is a unit of potential value. It is where you capture, research, and score opportunities to decide what needs to be built next.

A Discovery Project in Jira Product Discovery is the dedicated command center for a specific product or team. Unlike a standard Jira Software project (which focuses on code and tasks), this space is designed for strategy and prioritization. It is the single source of truth where you house your backlog of ideas, create custom views (like roadmaps or impact matrices), and manage the fields and formulas used to score your opportunities.

Learn how to create your very first Jira Product Discovery space. This is where you are going to put your ideas and strategically determine which idea your team will pursue.

Learn your way around Jira Product Discovery.  Understand what the different views are for and how you can leverage JPD views to present critical data to your stakeholders.

Create your own views to convey important information in relation to your ideas. 

Jira Product Discovery Fields are the customizable data points that product teams use to evaluate, categorize, and prioritize their Ideas. They are the essential inputs that drive your prioritization frameworks and dynamic roadmaps.

Learn about JPD fields, how to create them and how to use them.

The JPD workflow should reflect your team's process for validating and scoring opportunities.

Learn how to modify your JPD workflow to reflect your team's actual process. 

Jira Product Discovery (JPD) Insights are the critical pieces of evidence, data, or feedback that Product Managers use to support, validate, and shape an Idea. They are the voice of the customer and the market brought directly into the prioritization process.

Learn how to capture insights for your Ideas and understand the value of capturing insights.

Jira Product Discovery (JPD) Comments are the essential tool for collaboration and asynchronous discussion surrounding a specific Idea. They are tied directly to an individual Idea record and serve as the central space where product managers, designers, engineers, and stakeholders debate, refine, and reach consensus on the Idea's value and execution.

Learn how to create comments and boost internal communication.  Add context to each idea and encourage team members to collaborate and provide their feedback on an idea.

These are the customizable field types that allow product managers to implement their specific prioritization methodologies (like RICE, ICE, or Weighted Scoring).

Learn how to create and use special JPD only fields that help provide additional context to your ideas.

The term JPD Global Fields refers to custom fields that are created by a Jira Administrator at the site level and are then reused across multiple Jira Product Discovery projects (spaces).

Learn how to create global JPD fields.  These fields can be shared with other JPD spaces.

Jira Product Discovery (JPD) Roadmaps are dynamic, customizable visualizations that display the planned future state of your product based on prioritized Ideas. Unlike static, presentation-only roadmaps, JPD roadmaps are live, interactive views of your product backlog, ensuring stakeholders are always looking at the most current prioritization decisions.

Learn how to create both single space and cross space Roadmaps in JPD.  Roadmaps allow you to visualize when ideas are planned.

Learn how you can connect a JPD idea with a Jira Software work item.  This is then used to track overall progress of the idea as it relates to all the work tracked in Jira.

The Jira Product Discovery (JPD) Delivery Feature is the critical functionality that bridges the gap between validated product Ideas and their execution by engineering teams in Jira Software. It ensures that the product team's strategic prioritization is seamlessly translated into the development backlog.

Initiatives are high-level, strategic goals that require significant cross-functional effort and typically span multiple teams, programs, and often multiple planning periods (e.g., quarters or Program Increments). They represent the largest unit of measurable business value used for portfolio-level planning

Learn how to create Initiatives in your Jira.  You'll need to be a Jira administrator to do this.

After an initiative has been created, they still need to be added to your Jira projects. 

Learn how to add Initiatives to your Jira project.  This will then allow anyone on your team to create Initiatives using the Create button in Jira.

With an Initiative now available in Jira, you can now connect a JPD idea to a Jira Initiative.  This is important for the rest of the course.

Before getting started with Jira Plans, you need to understand a few basic requirements that will make your experience with Jira Plans better.

Similar to defining your priorities, you should also define all the different types of work that your team can capture in Jira.  Not all work is created equal and your team should know how to categorize the different types of work.

Have a good definition for each of your priority levels.  This should be well communicated and documented.

Jira Plans, formerly known as Advanced Roadmaps for Jira (and originally Portfolio for Jira), is a powerful feature in Jira Software Premium and Enterprise that enables teams-of-teams to conduct large-scale, strategic planning and roadmapping.

Creating a Plan in Jira is the process of setting up a centralized, multi-team, multi-project roadmap for strategic planning.

Learn how to create a plan in Jira.  You'll learn how to name the plan, determine access, and which work items get pulled into your plan.

Using a Plan in Jira  is about moving beyond individual project roadmaps to strategic, cross-team planning, and scenario modeling for large Initiatives.

Once you have created and configured a Plan, you primarily use it as a dynamic sandbox to sequence work, manage dependencies, and balance team capacity.

Learn how to navigate around the Jira Plan.  Understand the different tabs and views and how you can use them to help you be more strategic with your planning.

Initiatives drive everything downstream.  Jira Plans can be configured to be centered around the Initiatives that your team has prioritized.

Learn how to configure your Plan view to center around your Initiative(s).

The out of the box configurations for Plans are not very sophisticated.  All your fields and custom fields aren't automatically included.  Learn how to pull in critical project information into your plan.

Learn how to add custom fields to your plan.  Then learn how to display your custom fields in your plan.  You'll also learn how to add other default fields to you plan as well.

Utilize start and due dates to visually see them on your plan's timeline.

Learn how to add a start and due date to your plan.  Also learn how to configure which date fields can be used to drive the date data on your plan.

With dates on each of your Initiatives, dependencies can now be easily visualized.  Dependencies help you understand the order of operations (the order in which you need to perform each Initiative.

Learn how to physically connect related Initiatives in Jira Plans. 

Cross project releases facilitate having a single releases that can contain all important artifacts that will be released to the customer.

Learn how to create space specific releases and then how to create a cross project release in your Jira Plan.

With releases available at the space and plan level, each work item (initiatives and epics) needs to be associated to its appropriate release. 

Learn how to apply a value to the fix versions field of each work item (initiatives and epics).  This will associate the work item to the appropriate release.

Having a clear structure for Confluence makes it much easier for your team to find useful information. Permissions define what someone can do in Confluence.

Get a hands-on look at how you can plan, and build, your content structure in Confluence.

Get a hands-on look at how you can setup permissions in Confluence to best support your team.

Content restrictions allow you to prevent individuals or groups from viewing, or editing, specific pieces of content.

Confluence is a great place to brainstorm for your project, sprint or anything else. Get a look at how pages and whiteboards can help you with this critical process.

Get a hands-on look at how you can use pages and whiteboards to brainstorm in Confluence.

Templates let you quickly add formatting to a page and make content creation repeatable!

Confluence is also a great place for storing team-related documentation including processes, definitions and more. See how here!

Jira is where your team will track the progress of all the work that will ultimately have to be completed in order to deliver a project. 

Every epic ultimately needs to be broken down into stories.  Stories will be the work that individual contributors pull into their sprints.

Learn techniques for breaking down epics into stories.

All stories associated to the epics end up in the backlog.  But they are added in the order they are created.

Learn how to understand how your backlog is populated and how to add additional work to your backlog.

Refining allows you to make sense of your backlog.  It allows you to move items that are more ready for the development team to be towards the top of the backlog and the items that aren't quite ready to be moved towards the bottom.

Learn how to move items in your backlog.  Learn about ranking and how Jira's UI helps you move work around.

With a fully refined backlog, you can easily plan a sprint.  Move work from your backlog to your Sprint until all team members have reached their capacity.

Learn how to create a sprint and move work from your backlog into your sprint. Also learn how to estimate work and assign work to individual contributors.

After you have planned your sprint, you can then start your sprint.  The name of the game is to help your team move work from To Do -> Done within the bounds of the sprint.

Learn tips and tricks to help your team execute their sprint commitments. 

A Confluence page is a great place to store a retrospective - especially when you use templates.

See how whiteboards can be used to manage retrospectives.

When you close a sprint you'll have the option of making a retrospective right away.

You can schedule an automation to make a new retrospective page for you and the team to fill out.

You can also create an automation to trigger on sprint completion to create a retrospective for you and the team to fill out.

Rovo (Atlassian's AI tool) can be used to perform retrospectives.

Having videos all to yourself is great... but sharing them with your team (and others) is even better!

Connecting your calendar is the first step in Loom auto-recording your calls.

Loom can sit in meetings and take notes for you. This frees up your time to focus on more important things.

Eventually you'll get a ALOT of stuff in Loom. Making time to organize it will help keep things useful.