This terms represent an overview of Scrum. Some of them are not mandatory, but they’re commonly used in Scrum.
Daily Scrum
Scrum Event that’s in a 15 minute time box, held each day for the Developers. Here the Developers plan their work for the next 24 hours. This optimizes team collaboration and performance, by inspecting the work since the last Daily Scrum.
Definition of Done
A shared understanding of expectations that the Increment must live up to, in order to be releasable into production. Managed by the Developers.
Developers
Role within a Scrum Team accountable for managing, organizing and doing all development work required to create a releasable Increment of product every Sprint
Empiricism
Process control type in which only the past is accepted as certain and in which decisions are based on observation, experience and experimentation. It has three pillars:
- transparency
- inspection
- adaptation
Increment
Scrum Artifact that defines the complete and valuable work produced by the Developers during a Sprint. It’s the sum of all Increments from a product.
Product Backlog
A Scrum Artifact that consists of an ordered list of the work to be done in order to create, maintain and sutain a product. Managed by the Product Owner.
Product Backlog Refinement
The activity in a Sprint through which the Product Owner and the Developers add granularity to the Product Backlog.
Product Owner
Role in Scrum accountable for maximizing the value of a product, primarily by incrementally managing and expressing business and functional expectations for a product to the Developers.
Product Goal
The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against. The Product Goal is in the Product Backlog. The rest of the Product Backlog emerges to define “what” will fulfill the Product Goal.
Scrum
Scrum is a framework to support teams in complex product development. Scrum consists of Scrum Teams and their associated roles, events, artifacts, and rules.
Scrum Master
Role within a Scrum Team accountable for guiding, coaching, teaching and assisting a Scrum Team and its environments in a proper understanding and use uf Scrum.
Scrum Team
A self-organizing team consisting of a Product Owner, Developers and Scrum Master.
Scrum Values
A set of fundamental values and qualities underpinning the Scrum framework:
- commitment
- focus
- opennes
- respect
- courage
Sprint
Scrum Event that’s timeboxed to one month or less, that serves as a container for the other Scrum events and activities. Sprints are done consecutively, without intermediate gaps. It always takes 15 minutes.
Sprint Backlog
Scrum Artifact that provides an overview of the development work to realize a Sprint’s goal. Typically a forecast of functionality and the work needed to deliver that functionality. Managed by the Developers.
Sprint Goal
A short expression of the purpose of a Sprint, often a business problem that’s addressed. Functionality might be adjusted during the Sprint in order to achieve the Sprint Goal.
Sprint Planning
Scrum Event that’s time-boxed to 8 hours or less to start a Sprint. It serves for the Scrum Team to inspect the work from the Product Backlog that’s most valuable to be done next and design that work into Sprint Backlog.
Sprint Retrospective
Scrum Event that’s set to a time-box of 3 hours or less to end a Sprint. It serves the Scrum Team to inspect the past Sprint and plan for improvements to be enacted during the next Sprint.
Sprint Review
Scrum Event that’s set to a time-box of 4 hours or less to conclude the development work of a Sprint. It serves the Scrum Team and stakeholders to inspect the Increment of product resulting from the Sprint. Asses the impact of the work performed on overall progress and update the Product backlog in order to maximize the value of the next period.