We know that Scrum can be a little overwhelming, so we wanted to make it easier to understand with this glossary of Scrum Terms. Don’t see something that you think should be here? Contact us at email@example.com!
3-5-3-5 (occasionally 3-5-3)
An easy way to remember the basic components of Scrum.
Scrum has 3 Roles: Product Owner, Scrum Master, Developers.
Scrum has 5 Events: Sprint Planning, Sprint, Daily Scrum, Sprint Review, and Sprint Retrospective.
Scrum has 3 Artifacts: Product Backlog, Sprint Backlog, and Product Increment.
Scrum has 5 Core Values: Courage, Focus, Commitment, Respect, and Openness.
16th Minute (Parking Lot)
An unofficial extension of a meeting that often follows The Daily Scrum. The members of the Scrum Team that are required to reach the resolution can discuss in-depth issues, impediments, or topics that go beyond the scope of the Daily Scrum.
One of the three Scrum Pillars. After inspection, if one or more aspects of a product deviates outside of the acceptable limits, the resulting product will be unacceptable. The work must be adjusted.
A term used to describe what needs to be done for the Product Backlog Item (PBI) to be considered complete. This helps teams estimate, test, and accomplish their work.
Items which represent work or value.
An ordered and prioritized list of work, created by the Product Owner (PO), to be done by the Scrum Team.
An item that represents a piece of work to be done by the Scrum Team.
The ongoing process of estimating, adding detail, and ordering items in the Backlog. Backlog Items can be updated any time at the Product Owner’s discretion.
A pattern for allowing emergent work or interrupts to be brought into the Sprint and worked on as it comes in. The Scrum Team sets an amount of story points or capacity to a buffer based on Yesterday’s Weather.
One of the five Scrum Values. People personally commit to achieving the goals of the Scrum Team.
One of the five Scrum Values. The Scrum Team members have the courage to do the right thing and work on tough problems.
One of the 5 Scrum Events. This meeting has a timebox of fifteen minutes and happens every workday at the same appointed time and place. The information needed to assess progress is presented, and any impediments are noted.
A visualization of any dependencies, collaborations and events that will impact the teams during the Sprint. It provides a way to manage the flow of work within a Scrum of Scrums and should be reviewed and updated daily.
Definition of Done
A term that represents the organization’s formal definition of quality for all Product Backlog Items (PBIs). If an organization does not have one, the Scrum team should set its own.
Definition of Ready
Information needed by the team in order to understand and complete a Product Backlog Item.
Also known as, the Team, consists of people who work on Sprint Backlog Items. It acts as one team and should have all the skills needed to produce a working, tested increment each Sprint.
A foundation of Scrum. The belief that knowledge comes from experience and making decisions based on what is known.
The act of predicting how much effort will be needed to complete work on a Product Backlog Item. Most commonly occurs during Product Backlog Refinement.
A series of numbers starting with 0 or 1 where each subsequent number is the sum of the prior two numbers. Often used as a way for Scrum Teams to estimate the amount of effort it will take to complete each Product Backlog Item.
One of the five Scrum Values. Everyone focuses on the work of the Sprint and the goals of the Scrum Team.
Anything that slows the Team down or prevents them from completing work. The Scrum Master helps the Team remove impediments they can’t remove on their own.
Increment (Potentially Shippable Product)
The value delivered for the Customer via the Product Backlog Items completed during a Sprint. Each Increment should work with prior Increments and stand alone as an addition of value to the Product.
One of the three Scrum Pillars. Scrum users must frequently inspect Scrum artifacts and progress toward a Sprint Goal to detect undesirable variances. Inspections are most beneficial when performed by skilled inspectors at the point of work and at Scrum events.
A Scrum pattern. A method of allowing emergent work or interrupts to be brought into the Sprint and worked on as it comes in. The Scrum Team allocates a set amount of Sprint capacity to a buffer.
An acronym that details the elements an individual Product Backlog Item needs to meet the Definition of Ready.
Immediately Actionable, Negotiable, Valuable, Estimable, Small, Testable
Minimum Viable Bureaucracy
Having the least amount of governing bodies and processes needed to carry out the functions of an organization, without impeding the delivery of customer value.
Minimum Viable Product
A version of a product which allows a team to collect the maximum amount of validated learning about customers with the least amount of effort.
A Scrum Value. An agreement between the Team and the Stakeholders to be open about all the work and the challenges had while doing it.
A priority ordered list of everything that is known to be needed in developing the product. The source of requirements for any changes to be made to the product.
Product Backlog Item (PBI)
A change to be made to the product in a future Sprint. Higher ordered Product Backlog Items are usually more detailed than lower ordered ones.
Product Backlog Refinement
A whole team activity led by the Product Owner. The on-going process of adding detail, estimates, and order to the items in the Product Backlog.
Stakeholder input that is analyzed to inform the next iteration, and path of a product or service.
One of three Scrum Roles. Responsible for creating a compelling product vision that is executable. Other responsibilities include curating and prioritizing a Product Backlog, spending 50% of their time with customers and stakeholders, and 50% working closely with the team.