Jira Boards | Everything You Need To Know | Agile Projects

Welcome to the section! Here we'll cover some basic/core concepts you'll need to understand to be successful using Jira Boards.

Kanban and Scrum are two types of agile project management that Jira Boards support. Understanding their underlying concepts will help you work with teams and better use Jira to support their needs.

Jira can be confusing - especially if you don't understand some basics! Here we'll go over the core ideas and concepts you'll need to be successful.

Workflows describe how work items can move in Jira. This is critical as our boards rely on them to allow team members to move items between columns.

The type of project you're using has a big impact on the features you have access to (or don't have access to!). Here we'll dig into some of the high-level differences.

Get a quick look at what a company-managed kanban board looks like.

Get a quick look at what a company-managed scrum board looks like.

Get a quick look at what a team-managed Kanban board looks like.

Get a quick look at what a team-managed scrum board looks like.

Sprints are only found in scrum boards, but they have to be created by someone with access. Here we'll see how it's done.

After a sprint is created work items can be moved into it, but it must be started to become the active sprint (the one the teams work in).

Sprints won't close on their own, someone has to go in and complete them. This offers some options on what to do with remaining, open, items. See what it looks like here.

Welcome to our section on permissions and filters! These topics are some of the most frustrating for folks (and the ones I deal with the most as an admin!).

Dig into some concepts around how boards are created, who can administer them and permissions related to these topics.

Board filters are incredibly important as they determine what appears on the board. Get a high-level overview of the topic here.

See how to create a company-managed board (either scrum or Kanban!).

Company-managed boards rely on filters to populate work items. Understanding how to create them, modify them, and give people access is critical to being a board admin.

Sub-filters are only available on company-managed kanban boards, but let you more finely control what work items appear.

Company-managed boards have a specific permission called "Board Administrator" that allows admin access.

Team-managed board access is granted to project admins (which can be... dangerous!).

Team-managed projects allow admins to control features via a menu. Here we'll see which ones are important for boards.

Welcome to this section on columns (vertical parts of a board) and swimlanes (horizontal parts of a board). These are important concepts and have a huge impact on how your team uses boards.

Columns are the vertical aspects of the board that help define a process or flow for work.

Team managed projects can manage their columns right in project settings.

Company managed boards can manage their columns from board settings.

Swimlanes are the horizontal aspects of a board that help teams easily break up work by some criteria.

Team managed projects have a few options for creating swimlanes - including by Epic and Assignee.

Company managed projects expand on the basic ones in team managed projects, but also allow admins to define their own via queries.

Welcome to this section on board appearance and estimation! What the board looks like will have a big impact on how your team uses it, and how the board calculates estimates directly impacts the team's ability to work.

Somethings visual appearance has a big impact on how people interact with it. Here we'll cover the various options you have to adjust the look and feel of your board.

Company-managed project boards allow some control over what fields are displayed on their cards.

Company-managed project boards allow you to color-code cards via several methods (including JQL).

Company-managed project boards let you define "quick filters" which let folks easily filter the board based on an underlying JQL statement. (Note - this is called "custom filters" in a team-managed project).

Team-managed project boards let you define "custom filters" which let folks easily filter the board based on an underlying JQL statement. (Note - this is called "quick filters" in a company-managed project)

Whether it's by time, story points or something else, a large part of agile is estimating work. Get a high-level overview of your options here.

Team-managed projects allow for two methods of estimation - story points and time.

Jira offers a number of reports that help you understand what's going on with your project.

Get an overview of what to expect on an Atlassian exam.

Dig in and understand what taking an exam is like, including strategies for answering questions.

See how to schedule your exam.

Congrats on getting to the end! Remember this course is intended to be a reference and will be continually updated. I hope you had a 5-star experience, but please leave a review so I know what you think of it!