The Complete JIRA Agile Project Management Course

***Update on Jira Project Types*** Please note that Classic Project types are now called "Company Managed Projects" and "Next-Gen Projects" are now called "Team Managed Projects.

Create a free Jira Software Cloud account which is required for this course:
https://www.atlassian.com/try/cloud/signup?bundle=jira-software&edition=free

In this lesson, we'll create a new company-managed project type that will be used for following along with this course. ***Please note: Next-Gen projects (now called "Team-managed projects") are a newer project type with a more simpler interface and they do not contain most of the setup covered in this course (i.e. components, board settings etc) as of this recording, so please ensure you create a company-managed project type before moving forward with future lessons.***

In this lesson, we'll walk through how to setup project components.

***Please note, components are ONLY available in "Company-Managed" Project types. Team-Managed projects will not have the component feature.

Create your 1st Epic using the ***DOWNLOAD RESOURCE BELOW*** to copy and paste the Epic Name, Description or just type it out manually.

Create your Stories using the ***DOWNLOAD RESOURCE BELOW*** to copy and paste the Story Name, Description/Acceptance Criteria or just type it out manually.

If you haven't already, download your Epic and Stories examples to copy and paste them into your JIRA project using the resources below.

In this video, you'll discover what release management is including the different styles of Waterfall vs Agile releases and how you can leverage this feature to deliver your digital products in your Jira Company-Managed/Classic Projects.

In this lesson, we'll walk through how to create your Jira Release versions and tag your issues to each release, as well as cover some release management best practices in Jira.

Quick intro to why backlog management is critical to your project's success.

Many product owners want to hold onto everything 'In Case' they need it in the future. Chances are, if you haven't gotten around to working on an issue over a long period of time, it isn't really important. In this lesson, you'll learn to embrace the mindset of 'cleaning house' so that your backlog only contains true priorities.

Let's knock out some misconceptions that may keep you from keeping a clean backlog. In this lesson, you'll learn how to leverage some Agile Scrum team practices to support your backlog maintenance efforts while continuing to deliver value in each sprint.

Purging your backlog is the most critical activity to backlog maintenance when it comes to keeping the number of issues in your project backlog down. If you don't do this on a scheduled basis (at least once each quarter), then your backlog can quickly become a nightmare of useless issues.

Track the total scope independently from the total work done. This helps your team track progress to better understand the effect of scope change.

Track the total work remaining and project the likelihood of achieving the sprint goal. This helps your team track and manage progress and take appropriate action.

Displays the statuses of issues over time. This helps you identify possible bottlenecks that need to be investigated to improve flow.

Track the amount of work completed from sprint-to-sprint. This helps you identify your team's velocity and estimate the work they can realistically achieve in future sprints.

Displays the cycle time for your product, version or sprint. This helps you identify whether data from the current process can be used to determine future performance.

Team-managed (formerly Next-Gen) project types are a new feature in the Jira Software Cloud experience. Flexible and easy to use, Jira Team-managed projects are more user friendly and don't require a certified Jira Admin to manage your Jira setup. Learn more about some of the key ways these projects can help you streamline your workflow.