From the course: Learning Jira: Leveraging Sprints, Releasing Features, Fixing Bugs, and Tracking Development

Unlock this course with a free trial

Join today to access over 24,900 courses taught by industry experts.

Leveraging backlogs and sprints

Leveraging backlogs and sprints - Jira Tutorial

From the course: Learning Jira: Leveraging Sprints, Releasing Features, Fixing Bugs, and Tracking Development

Start my 1-month free trial Buy for my team

Leveraging backlogs and sprints

“

- [Instructor] In this section, we'll discuss how the backlog and sprint features help Scrum teams manage work, and as usual, here are some definitions. A backlog is essentially a team's might-do list. New Jira items are generally stored in the backlog until they're estimated, prioritized, and scheduled for work. A sprint is a time-boxed iteration where teams complete work pulled from the backlog. Sprint durations are generally short to help teams deliver software in small, frequent chunks. When I was writing code, we used two-week sprint to deliver a set of items or achieve a specific goal. At the end of a sprint, new sprint starts with a new goal and set of items. Here's an example backlog in a Scrum project. The backlog contains work to estimate and prioritize in time for the next scheduling discussion. There's no limit to the number of items in the backlog, but it's best to limit the list to items that are likely to be…

Contents