Product Backlog VS Sprint Backlog
Product Backlog is a collection of list of items to be developed i.e. It is the list of functional and non-functional requirements ordered based upon the priority of requirement. In other words Product Backlog is simply a list of all things that needs to be done within the project. It replaces the traditional requirements specification artifacts. These items can have a technical nature or can be user-centric e.g. in the form of user stories.
As per SCRUM, The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering. A Product Backlog is never complete. The earliest development of it lays out the initially known and best-understood requirements. The Product Backlog evolves as the product and the environment in which it will be used evolves. The Product Backlog is dynamic; it constantly changes to identify what the product needs to be appropriate, competitive, and useful. If a product exists, its Product Backlog also exists.
What is Sprint Backlog ?
The sprint backlog is a list of tasks identified by the Scrum team to be completed during the Scrum sprint. During the sprint planning meeting, the team selects some number of product backlog items, usually in the form of user stories, and identifies the tasks necessary to complete each user story.
As described in the Scrum Guide, the Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal. The Sprint Backlog is a forecast by the Development Team about what functionality will be in the next Increment and the work needed to deliver that functionality into a “Done” Increment.
The Sprint Backlog makes visible all the work that the Development Team identifies as necessary to meet the Sprint Goal. To ensure continuous improvement, it includes at least one high priority process improvement identified in the previous Retrospective meeting.
What is difference between Product and Sprint backlog ?
The Product Backlog is defined as:
- The requirements.
- A list of all desired work on the release.
- Ideally expressed such that each item has value to the users or customers of the product.
- Expressed as customer-oriented features (not as technical tasks !).
- Prioritized by the product owner.
- Re-prioritized at the start of each sprint.
Top Priority features from the Product Backlog that would be developed by the end of the Sprint Members volunteer to work on task.
How Do the Product Backlog and the Sprint Backlog Work Together?
For a team to work efficiently, they must understand the difference between a product backlog and a sprint backlog, and how these two helps to achieve project goals. Therefore, during the sprint planning meeting, everyone on the development team should discuss what must be done and how it would be achieved. There is the product backlog list and the items from that list are then moved to a sprint backlog list. At this point each item on the sprint backlog is broken down into tasks, or steps, that will be taken to complete the item. All of this must be clearly communicated and agreed upon, for, as noted above, once started there can be no changes to the tasks and steps needed to complete them.
Who Prioritizes the sprint backlog?
In real Scrum, the Product Owner is the one that prioritizes the product backlog. However, it is the Development Team that decides how many of the prioritized stories it can fit in the upcoming Sprint.
Comments
Post a Comment