We decided there was only a couple things we actually wanted to track:
To create a new backlog item, just create a new issue.
Once a new issue has been created, assign it the right labels and/or assign it to a sprint (milestone).
Issues allow you to have a conversation about the item and even allow you to create task lists inside the issue using GitHub's markdown.
Add the following labels to your repository:
priority
labels allow you to prioritize items in your backlog e.g.:
priority: lowest
priority: low
priority: medium
priority: high
priority: highest
Highest = Within 24 Hours
High = Within 72 hours
Medium = Within 96 Hours
Low = Within 7 Days
Lowest = When time allows
point
labels allow you to to assign velocity points to individual items (issues) e.g. using Fibonacci numbers:
point: 1
point: 2
point: 3
point: 5
point: 8
point: 13
point: 21
type
labels allow you to easily filter items (issues) in the dashboard e.g.:
type:bug
: bugtype:chore
: chore, maintenance worktype:feature
: new featuretype:infrastructure
: infrastructure relatedtype:performance
: performance relatedtype:refactor
: refactortype:test
: test relatedYou can define and assign custom labels that you need within your workflow or organization.
You can create a milestone for every sprint and add items (issues) from the backlog to a milestone.
This allows you to group items in sprints and track them by milestone in your issue dashboard.
The backlog then consists of all items (issues) that have no milestone
attached to it.
TIP: Use no:milestone
in the search field on your issue dashboard to find backlog items.
Image: Scrum primer.