What is the Product Backlog - Agile Scrum
Product Backlog
In agile scrum, a product backlog is a prioritized list of features that has short descriptions on all the various functionalities desired in a product.
Unlike a requirements document, with scrum, there is no need to struggle with producing a lengthy product backlog at the beginning of the project and then leave it on your shelves to collect dust.
Basically, the PO, scrum master and scrum team brainstorms on the work needed to finish the product/project and then puts it on the product backlog, in priority order.
This initial product backlog can be used for the first sprint but the team continues to make the necessary changes to it as they learn more and more about the product and its customers.
Generally, a scrum product backlog contains anything relating to the product:
Factors that influence product owner’s prioritization include:
Paul VII. Agile Product Management: User Stories: How to capture, and manage requirements for Agile Product Management and Business Analysis with Scrum (scrum, ... development, agile software development) (pp. 18-19). Pashun Consulting Ltd.. Kindle Edition.
http://pashunconsulting.co.uk/blog/productbacklog.html
In agile scrum, a product backlog is a prioritized list of features that has short descriptions on all the various functionalities desired in a product.
Unlike a requirements document, with scrum, there is no need to struggle with producing a lengthy product backlog at the beginning of the project and then leave it on your shelves to collect dust.
Basically, the PO, scrum master and scrum team brainstorms on the work needed to finish the product/project and then puts it on the product backlog, in priority order.
This initial product backlog can be used for the first sprint but the team continues to make the necessary changes to it as they learn more and more about the product and its customers.
Generally, a scrum product backlog contains anything relating to the product:
✓ Features (New features (functional and non-functional requirements) or product extensions to address new opportunities or markets, or features requested by customers or internal stakeholders )
✓ Technical stuff (engineering stuff, enhancements, UI and usability changes or improvements )
✓ Bugs (that need fixing)
✓ Knowledge acquisition (research, risks)Features can be described using; use case, personas and scenarios, and user stories.
Click To See The Baclog |
Click To See The Priotrized and Estimated Backlog |
✓ Customer priorityRefrences
✓ Relative implementation difficulty
✓ Urgency of getting feedback
✓ Symbiotic relationships between work items (e.g. B is easier if we do A first)
Paul VII. Agile Product Management: User Stories: How to capture, and manage requirements for Agile Product Management and Business Analysis with Scrum (scrum, ... development, agile software development) (pp. 18-19). Pashun Consulting Ltd.. Kindle Edition.
http://pashunconsulting.co.uk/blog/productbacklog.html
Comments
Post a Comment