In Scrum, each iteration (Sprint), a team chooses a prioritized set of Product Backlog Items (PBIs) that they are confident they can complete. The set of PBIs that the team decides to work on during that Sprint is collectively referred to as the Sprint Backlog. Teams are wise to be selective about how many PBIs...Read More

In Scrum, there is an artifact that consists of a prioritized list of the new features, changes to existing features, bug fixes, infrastructure changes or other activities that a team may deliver to achieve a specific outcome, such as the creation of a new product or modifications to an existing product. The name of this...Read More

In Scrum, there is a meeting that focuses on continuous improvement, for a single team. A Sprint Retrospective occurs at the end of an iteration (Sprint), where a team reflects on its process, celebrates things that are going well, and identifies actionable steps associated with areas of potential improvement. A Scrum Team might choose to...Read More

It is common to have a meeting that focuses on continuous improvement, for multiple teams. One term for this kind of meeting is “Program Retrospective,” which reflects its cross-team nature, and which often occurs at a strategic inflection point, such as just after a product release, or after a certain number of iterations. Unlike a...Read More

Many organizations have gatherings that focusing on continuous improvement. In Scrum, at the individual team level, there is a Sprint Retrospective at the end of each iteration (Sprint). And at the cross-team level, some organizations choose to have a “Program Retrospective,” where the period of time under discussion is typically more than a single iteration,...Read More

An output from human activity, such as a product, along with things that can potentially support or constitute a product, such as code, test scripts, user manuals, and so on. In Scrum, there are three artifacts: Product Backlog; Sprint Backlog; and Increment. Related Media Artifact Video Artifact Podcasts Artifact Example Related Subjects Product Backlog Sprint...Read More

There is a set of values and principles, which was articulated via the Agile Manifesto. Agile product development maximizes customer value while minimizing waste and shortening time to market. A related set of values and principles originated with Lean, which includes five elements: the goal, kaizen (continuous improvement), product development flow, respect for people and...Read More

Agile teams employ short statements that serve as indicators of what “done” means for a specific user story. That is, Acceptance Criteria define desired behavior and determine whether a work item has been successfully developed. Acceptance Criteria work in conjunction with the Definition of Done, in that Acceptance Criteria are user-story-specific, while the Definition of...Read More

In Scrum, there is a way of formally articulating the nature of the commitment for any work that is consider complete, and thus part of the “Increment.” Thus a Definition of Done (DoD) is an agreement for a team or teams that sets a standard for achieving a “Done” user story, in conjunction with user-story-specific...Read More

It is common for Scrum teams to employ a number that expresses the total volume of work they have completed during an iteration (Sprint), where those completed work items all satisfy the work-item-specific Acceptance Criteria, along with a global Definition of Done. A Sprint is a recurring event, and through the repetition of a set...Read More