4-5 minutes<\/p>\n
Scrum is a light-weight framework with a minimal set of rules. The rules help people to empirically make the most out of every single day of creating software products.<\/p>\n
The product backlog , sprint backlog , and potentially shippable product increment are examples of Scrum artifacts .<\/p>\n
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, and typically in the form of user stories. <\/span><\/p>\n The sprint backlog is the list of refined product backlog items chosen for development in the current sprint , together with the team\u2019s plan for accomplishing the work. It reflect the team\u2019s forecast of what work can be completed. Once the sprint backlog is established, the development team begins work on the new product increment. <\/span><\/p>\n Every sprint produces a product increment, the most important Scrum artifact. A product Increment is the \u201cgoal line\u201d for each sprint and, at the end of the sprint, it must: <\/span><\/p>\n A Scrum product backlog is simply a list of things to do for the project. The Product Owner creates, maintains, and regularly re-orders a list of feature to be implemented for a product for adapting to emerging requirements, customer feedback, and market changes.<\/span><\/p>\n Product Backlog Grooming <\/span><\/p>\n Product Backlog items at the top of the Product Backlog should be refined and likely to be included soon in next sprint planning . Items further down the backlog need less concrete and can reflect bigger ore more complex ideas. These larger chunks will need to bebroken down into smaller pieces as they approach the top of the Product Backlog as shown in the Figure below as suggested by Gunther Verheyen\u2019s article \u2013 The Value of the Product Backlog :<\/span><\/p>\n Groundwork of Product Backlog for Sprint Planning<\/span><\/p>\n In the product backlog above, product backlog items (PBIs) are classified as three different categories readily for the sprint planning:<\/p>\n By maintaining a well categorized product backlog like the structure above, your teamshould be more readily to proceed to the sprint planning process.<\/p>\n","protected":false},"excerpt":{"rendered":"Sprint Backlog <\/span><\/h3>\n
Product Increment<\/span><\/h3>\n
\n
Product increment Product Backlog Grooming <\/span><\/h3>\n
Groundwork of Product Backlog for Sprint Planning<\/span><\/h3>\n
\n