Jira Fundamentals 2026: Effective Agile Project Management

Get a clear picture of what Jira is and who uses it, from software teams to business teams. You'll meet its building blocks (work items, spaces, workflows, boards, reports and customisation) and see how Jira fits alongside Confluence and Rovo, Atlassian's AI. You'll also find out why work items used to be called issues and spaces used to be called projects. By the end, you'll be able to explain what Jira does and recognise its main parts.

A five-minute introduction to Agile, starting from the 2001 Agile Manifesto and its four values. You'll see what each value means in practice, and why Agile is a philosophy rather than a methodology, a process or a tool. By the end, you'll be able to explain the four Agile values and how frameworks like Scrum and Kanban build on them.

A quick, practical tour of Scrum, and why Jira leans on it so heavily. You'll meet the key roles (product owner and Scrum master) and terms (user stories, the product backlog, effort estimates and sprints), and see how they fit together into a repeating cycle. By the end, you'll be able to write a user story that covers who, what and why, and recognise Scrum terms when you see them in Jira.

Find out what a Jira space is (it used to be called a project) and why the word project now means something else in Jira. Using the online store as an example, you'll see the three things every space brings together: work items, workflows and people. By the end, you'll be able to describe what a space holds and tell the two meanings of project apart.

When you create a space, Jira asks whether it should be team-managed or company-managed, and the answer is hard to change later. You'll compare the two: who controls each one, what each is good for, and where the choice appears on screen. By the end, you'll be able to choose the right type for your situation and explain why your screens might not match a tutorial.

Create a Jira space from scratch with the Scrum template and see every decision Jira asks you to make. You'll choose a template, pick team-managed or company-managed and watch the form change, and set a name and a space key worth getting right first time. By the end, you'll be able to create a space deliberately and check any space's type in the Spaces directory.

Tour all eleven screens of Space settings in a team-managed space, from Details and Access to Automation, Fields, Work types and Features. You'll see which settings are safe to change, why the space key is best left alone, and where Jira's AI agents are configured. By the end, you'll be able to find any space setting quickly and explain why a company-managed space shows many more screens.

Find out what a Jira work item is, and why you'll also hear it called an issue or a ticket. Using two everyday examples, a holiday checklist and a list of software fixes, you'll see how ordinary tasks become work items and move through To Do, In Progress and Done. By the end, you'll be able to turn a list of work into Jira work items and describe the default workflow.

Meet Jira's standard work item types: stories, bugs, tasks and epics. You'll sort a real list of software work into the right types and group related items under epics such as User Authentication and User Profile. By the end, you'll be able to decide which type fits any piece of work, and when an epic is worth creating.

Break the online store's requirements down into epics and stories, ready to go into Jira. You'll map each requirement to the epics that cover it, add epics for non-functional work such as alerting and monitoring, and define the first stories, with printable maps in the lesson resources. By the end, you'll be able to turn a list of requirements into an epic and story structure that covers the whole scope.

See how work items move through Jira using statuses, workflows and transitions. You'll find out why teams add statuses such as In Review or QA, how the workflow shapes your board and your reports, and how to open a diagram of the workflow from any work item. By the end, you'll be able to explain the difference between a status, a workflow and a transition, and change a work item's status.

Put the course project into Jira, first by hand and then all at once from a CSV file. You'll add the missing Bug work type, create epics and stories three different ways, explore the main work item fields, bulk-delete sample data, and import 37 work items with their parent epics. By the end, you'll be able to create work items whichever way suits the moment and import a whole backlog from a spreadsheet.

Compare Jira's two kinds of board: Scrum, built around sprints, and Kanban, built around continuous flow. You'll see why a new Scrum board stays empty until a sprint starts, how to tell the two apart from their tabs, and where the choice is actually made. By the end, you'll be able to pick the right board for the way your team works.

Groom your backlog so the most important work sits at the top. You'll put the epics in priority order, see why epic priority doesn't cascade to the stories inside them, and reorder work items with the row menu and drag-and-drop, using the prioritised backlog in the lesson resources. By the end, you'll be able to prioritise a Jira backlog quickly and keep it groomed.

Estimate effort for every work item using the Fibonacci sequence and story points. You'll see why approximate estimates beat precise ones, then enter estimates straight from the backlog, from the row menu or on the work item itself, using the estimates in the lesson resources. By the end, you'll be able to estimate a whole backlog in Jira and have it ready for sprint planning.

Work out your team's capacity and how many sprints the project needs, then create them in Jira. You'll do the capacity arithmetic for a two-person team, see why numbered sprint names cause mix-ups, and create and rename seven sprints in the backlog. By the end, you'll be able to calculate sprint capacity and set up clearly named sprints for a project.

aFill your sprints with work while keeping each one within the team's capacity. You'll move stories into sprints with the row menu and by dragging, use Jira's running estimate total to fill each sprint exactly, and see why dependencies can outrank backlog order. By the end, you'll be able to plan a sprint that's full but not overloaded.

See how Jira Plans brings several spaces and teams together in one view. You'll create a plan from two spaces, look at its views for timelines, capacity and dependencies, and find out why changes in a plan don't touch anyone's board until you commit them. Plans is a Premium feature, so the lesson is worth watching even on the Free plan. By the end, you'll be able to explain when a team needs a plan rather than a board.

Run your first sprint from start to finish. You'll assign work, add descriptions, start the sprint with a custom duration and a sprint goal, move cards across the board, use comments and the activity history, check progress in Sprint insights, and close the sprint. By the end, you'll be able to start, monitor and complete a sprint in Jira.

Use Jira's three everyday collaboration tools: assignees, @mentions and watchers. You'll assign work, pull a teammate into a comment with a mention, watch work items, and check your personal notification settings so you know which emails Jira will send. By the end, you'll be able to keep your team coordinated and the discussion attached to the work, without leaving Jira.

Find work fast as your Jira site grows. You'll filter a backlog or board as you type and by person, search across Jira and other Atlassian tools from the top bar, and use the full search screen, including the default 30-day filter that quietly hides older work. By the end, you'll be able to find any work item, board or filter in seconds and edit results straight from the list.

Go beyond basic search with JQL, Jira Query Language. You'll switch between the basic and JQL views, build a query from fields, operators and AND, sort the results, and save the search as a filter with the right sharing permissions. By the end, you'll be able to write simple JQL queries and save them as filters you and your team can reuse.

Find out why Jira's screens say space and work item, while JQL, automation and the API still say project and issue. You'll see why Atlassian renamed the interface but kept the old vocabulary underneath, and where you'll keep meeting the old words. By the end, you'll be able to move between the two vocabularies without confusion and use older Jira tutorials with confidence.

Get a clear overview of Rovo, the AI built into Jira and Confluence. You'll see its four parts (chat, search, agents and the small AI assists on everyday screens), how it's priced in credits, and why the Free plan doesn't include it. By the end, you'll be able to recognise Rovo features when they appear and decide when to double-check what the AI gives you.

Run a second sprint over three real days, and this time not everything goes to plan. You'll use backlog order and priority to manage a dependency, read the burndown while the sprint is runing, and close the sprint with an unfinished story moved into the next one. By the end, you'll be able to spot a sprint at risk early and handle unfinished work when you close it.

Find out what Jira reports can tell your team, and how to pick the right one for the question you're asking. You'll group common questions into themes (efficiency, certainty, plan, scope and quality), add the Reports tab to your board, and see which reports a team-managed space offers. By the end, you'll be able to open Jira's reports and choose the one that answers what you want to know.

Use Jira's sprint burndown chart to see whether a sprint will finish on time. You'll open it for the course project, then read three real sprints: one that finished early, one that stalled halfway and one still running. By the end, you'll be able to read the guideline and the remaining-work line, spot added scope, and see trouble coming while there's still time to act.

See how the burnup chart separates scope from completed work, which a burndown chart can't do. You'll read it on the course project, then on real sprints where work was added, removed and reopened. By the end, you'll be able to tell from the chart whether a team finished its work or dropped it, and decide which of the two charts suits your team.

Use the sprint report to see exactly what happened to every work item in a sprint. You'll find it in a team-managed space (underneath the burndown chart) and in a company-managed space, then read a real team's report: completed and unfinished work, changed estimates, work added and work removed. By the end, you'll be able to use the sprint report to run a well-informed retrospective.

Find out how much work your team can really do in a sprint with the velocity chart. You'll see why two sprints aren't enough to measure velocity, then read a real team's chart where commitments swung widely while completed work stayed steady. By the end, you'll be able to read velocity from completed work and use it to plan sprints realistically.

Read the cumulative flow diagram, the one Jira report that works with or without sprints, so Kanban teams can use it too. Using three months of a real team's work, you'll read the top edge as scope, the bottom band as finished work and the bands in between as work in progress. By the end, you'll be able to spot a bottleneck and see when and where work started piling up.