How does a backlog work?
A backlog is a prioritized list of new functionality, features, bugs, and any other new work items to be considered for the next work cycle. Ideally, stories in the product backlog contain enough information to allow the project team to provide an estimate for the work required to execute on each item as well as understand the relative priority of each item in relation to other work being considered.
Learn more about how backlogs work in this article and short video.
How do I let the Website Platform Team know about new work that my department needs support with?
Please add new items to Jira and they will be discussed at the next backlog grooming meeting. Alternatively, goals and needs can also be captured as new user stories during regularly scheduled check-ins and discussed at upcoming backlog grooming meetings.
...
| Info |
|---|
For examples and background on user stories: |
Sprint Cycle
Our team runs in 2-week sprints that start on Wednesdays every other week. This is a typical sprint cycle:
Mon | Tues | Wed | Thurs | Fri |
|---|---|---|---|---|
Backlog grooming | Sprint Day 1 | Sprint day 2 | Sprint day 3 | |
Sprint day 4 | Sprint day 5 | Sprint day 6 | Sprint day 7 | Sprint day 8 |
Sprint day 9 | Sprint close |
Sprint Dates:
Sprint Start | Sprint Close |
|---|---|
9/22 | 10/5 |
10/6 | 10/19 |
10/20 | 11/2 |
11/3 | 11/16 |
11/30 | 12/1 |
12/14 | 12/15 |