From the course: Learning Jira Software
Schalten Sie den kompletten Kurs noch heute frei
Join today to access over 23,400 courses taught by industry experts.
Leveraging backlogs and sprints - Jira Tutorial
From the course: Learning Jira Software
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 to-do list. New tier issues are generally stored in the backlog until they're estimated, prioritized and scheduled for work. When it's time to determine contents of work in the next cycle, the highest priority backlog items are selected first. If a developer has extra capacity, they can pull additional items from the backlog and into a sprint. But don't forget to check that QA can accommodate additional testing work. We need to keep our QA partners happy. A sprint is a time-boxed iteration where teams complete work from the backlog. Sprint durations are generally short to help teams deliver software in small, frequent chunks. And when I was writing code, we used two-week sprints to deliver a set of issues or achieve a specific goal.…
Inhalt
-
-
-
(Locked)
Software project types13m 20s
-
(Locked)
Common issue types13m 52s
-
(Locked)
Using software workflows7m 50s
-
(Locked)
Leveraging backlogs and sprints7m 5s
-
(Locked)
Estimating work and tracking time10m 40s
-
(Locked)
Using fix versions8m 54s
-
(Locked)
Types of boards7m 38s
-
(Locked)
Types of reports7m 19s
-
(Locked)
Common integrations4m 27s
-
(Locked)
-
-
-
-
-
-