Successfully added
Scrum
by John
Sprint Backlog
The sprint backlog should contain all the information the team needs to successfully plan and complete work within the time allotted without having to rush at the end.
Before start planning your sprint, you’ll want to have created, prioritized, and estimated the backlog and defined the sprints.
...see more
A Product Backlog Item (PBI) is a single element of work that exists in the product backlog. PBIs can include user stories, epics, specifications, bugs, or change requirements. The Product Owner of an Agile team compiles and prioritizes the product backlog, putting the most urgent or important PBIs at the top.
...see more
As an activity, Product Backlog refinement has the following purposes in Scrum:
- Clarifying items on the Product Backlog that are too unclear to start work on. This is preferably done directly with the people you’re building the items for (the stakeholders)
- Breaking down items that are too big to pull into a Sprint (which generally also means that they’re too unclear)
- Re-ordering the Product Backlog as needed to make the upcoming Sprints as smooth and valuable as possible
- Adding or removing items from the Product Backlog as new insights emerge
- Estimating the effort involved in implementing particular items. This does not have to be as ‘formal’ as assigning story points (an optional practice in Scrum), T-shirt sizes or whatever sizing technique you use. A gut feeling (“Yeah, we know well enough what needs to be done and it feels doable in a Sprint”) is fine too
Referenced in:
Leave a Comment
All fields are required. Your email address will not be published.
Comments