Scrum is simple; it consists of six time boxes (one of which is optional), three roles, and three ‘official’ artifacts. A sprint, the first of the six time boxes, is an iteration defined by a fixed start and end date; it is kicked off by sprint planning and concluded by the sprint review and retrospective. The […]
Scrum has a small set of artifacts: the product backlog, sprint backlog, and the product increment.
The Product Backlog
The product backlog is the product owner’s ‘wish list’. Anything and everything that they (and other stakeholders) want to be implemented in the product, goes into this list. It could be infinite as there are always new ideas about how to extend a product’s features. The product owner maintains and prioritizes the product backlog, although other stakeholders (including the team) should have visibility of and the ability to suggest new items for the list. The product backlog items are ranked according to their priority and they appear at the top of the product backlog, one after another. Once a team selects items for a sprint (or iteration), those items and their priorities are locked; however, priorities and details for any not-started work may change at any time.
The Sprint Backlog
The sprint backlog reflects the product backlog items that the team committed to in sprint planning, as well as the subsequent tasks and reminders. It is owned by the team and team members update it every day to reflect how many hours remain on his or her tasks. Team members may also remove tasks, add tasks, or change tasks as the sprint is underway.
The Product Increment
The product increment is a set of features, user stories, or other deliverables completed by the team in the sprint. The product increment should be potentially shippable. The product owner is responsible for accepting the product increment during each sprint, according to the agreed-upon Definition of Done and acceptance criteria for each sprint deliverable.
You might be interested in the following courses:
Course Category: Development Methodologies
A ScrumMaster must have a deep understanding of the Scrum framework. The job of a scrum master is to help the customer and the team to work very closely ensure expected deliveries. Scrum Master facilitates the team members to reflect upon ways that they can improve their day-to-day communication and processes. It is the responsibility […]
Agile Methodology refers to the software development methodology that is centered around the idea of iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams. The various Agile Methodologies share much of the same philosophy, many of the same characteristics and practices. But from an implementation standpoint, each of these methodologies has […]