Is a ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team.
The backlog can contain new features, improvements, known defects and other changes. It grows with the product itself and changes based on business requirements, market conditions or other relevant factors.
The Product Owner is responsible for the Product Backlog, including its content, availability and ordering.
The items present into a Product Backlog and their characteristics are dependent of the domain. Its common to have those fields described in a backlog item:
- Description
- Order
- Size
- Value
- Acceptance Criteria
Product backlog items that can be Done by the Scrum Team within one Sprint are deemed ready for selection in a Sprint Planning event. Product Backlog refinement is the act of breaking down and further defining Product Backlog items into smaller more precise items.
Developers who will be doing the work are responsible for the sizing. The Product Owner may influence the Developers by helping them understand and select trade-offs.
Product Backlog Refinement: the act of adding detail, estimatives and order to items in the Product Backlog. The objective is to have list of items ordered by priority with very well clarified with smaller manageable chuncks tha can be done in a sprint.
The backlog items that can be done in the next sprint as deemed as ready for selection. This means that the items are small enough to fit within a sprint, detailed enough and immediately actionable, meaning that the developers can start working on them right away. A Product backlog item is ready when the scrum team agrees it can be done.
References
ïœĄïœ„:*:ïŸâ ,ïœĄïœ„:*:ïŸâ ïœĄïœ„:*:ïŸâ ,ïœĄïœ„:*:ïŸâ ïœĄïœ„:*:
Contact Info:
E-mail: pamabeltrani@gmail.com
Discord: pamnawi