Scrum Framework Scrum Inc.

Click the Infographic for an Interactive Tour

Welcome to ScrumLab Open. Below, you will find all the core Scrum elements as well as a few recommended patterns to help you get started.

Even the most hyper-productive teams should revisit the basics to make sure they are getting the most out of Scrum. Click the image on your right to browse an interactive graphic of the Scrum framework.

In addition to the topics is a series of very accessible videos that will give you a quick introduction to some key Scrum concepts.

Once you are familiar with the basics, ScrumLab Prime has an entire library of online courses and an array of media developed by the industry's fore-most thought  leaders.  Join anytime.

 


All Open Videos



All Open Topics


Backlog Item (PBI)

Product Backlog Items (PBIs) are the elements that make up the Product Backlog. They can range from specifications and requirements, to use cases, epics, User Stories, or even bugs and chores. Each PBI must have these qualities: Description: What ...

Value Stream Map Image

Backlog Refinement

A crucial guideline in Scrum is that five to ten percent of every Sprint must be dedicated to Backlog Refinement. As the slides illustrate, this includes: detailed requirements analysis splitting large items into smaller ones (epics to User Stories) estimation of new items re-estimation of ...

Product-Backlog-Refinement-copy5

Burndown Chart

The Sprint Burndown Chart makes the work of the Team visible. It is a graphic representation that shows the rate at which work is completed and how much work remains to be done. The chart slopes downward over Sprint duration and across ...

Sprint Burndown Scrum nc.

Definition of Done

Each Scrum Team has its own Definition of Done. What matters is that each Team has a shared definition that every one understands. The Team's Definition of Done is used to assess when work on a User Story has been completed.Here’s ...

Scrum Inc. Definition of Done

Definition of Ready

Having a Definition of Ready means that stories must be immediately actionable. The Team must be able to determine what needs to be done and the amount of work required to complete the User Story or

Definition of Ready Scrum Inc.

eXtreme Manufacturing

The term eXtreme Manufacturing (XM) was coined by Team WIKISPEED, a non-profit car manufacturer, to describe how it manufactures automobiles combining the Scrum framework, Object-Oriented architecture and eXtreme Programming (XP). Blending these three practices, WIKISPEED invented a new manufacturing process that can shorten time-to-market, ...

eXtreme Manufacturing xm manufacturing wikispeed

Impediments

An Impediment is anything that keeps the Team from getting work Done and slowing Velocity. Impediments come in many different forms: a sick team member, a missing resource, lack of management support or even a cold team room. If it's ...

Scrum Impediment

Potentially Shippable Product

Potentially Shippable Product is the sum of the Product Backlog Items delivered each Sprint. Delivering Potentially Shippable Product each Sprint is fundamental to the Scrum framework because when work is divided into simple pieces it can be finished in ...

Potentially Shippable Product

Product Backlog

The Product Backlog is a prioritized list of everything that might be included in a product. The Product Owner creates, maintains, and regularly re-orders the Product Backlog. The Product Owner uses the Product Backlog to adapt to emerging requirements, customer feedback, and market ...

Product Backlog Features

Product Owner

The Product Owner is the Team member who knows what the customer wants and the relative Business Value of those wants. He can then translate the customer's wants and values back to the Scrum team. The Product Owner must know the business ...

Product Owner

Scrum at Scale Part I

Jeff Sutherland and the Scrum Inc. team present Scrum at Scale Part I - an object-oriented model for scaling Scrum across the business. The modular approach allows for the overall system to work together even if individual modules aren't agile. This allows the framework to support many different ...

Scrum Inc. Scrum at Scale http://scruminc.com/

Scrum at Scale Part II

Jeff Sutherland and the Scrum Inc. team present Scrum at Scale Part II - an object-oriented model for scaling Scrum across the business. The modular approach allows for the overall system to work together even if individual modules aren't agile. This allows the framework to support many different ...

Scrum Inc. Scrum at Scale http://scruminc.com/

Scrum at Scale Part III

Jeff Sutherland and the Scrum Inc. team present Scrum at Scale Part III - an object-oriented model for scaling Scrum across the business. The modular approach allows for the overall system to work together even if individual modules aren't agile. This allows the framework to support many different ...

Scrum Inc. Scrum at Scale http://scruminc.com/

Scrum Board

A Scrum Board is a tool that helps Teams make Sprint Backlog items visible. The board can take many physical and virtual forms but it performs the same function regardless of how it looks. The board is updated by the ...

Product Backlog Item

Scrum Master

The Scrum Master is tasked with making Scrum work. They work intimately with the Team, sometimes as a member. Their primary task is to remove Impediments and guide the team in Scrum practices. The Scrum Master does whatever it takes to help the team ...

Scrum Master - scrummaster

Sprint Backlog

The Sprint Backlog is an ordered list of Product Backlog Items, preferably User Stories, that the Team believes it can complete during the coming Sprint. These items are pulled from the top of the Product Backlog during ...

Sprint Backlog

Sprint Planning

Sprint Planning opens each sprint. The Product Owner discusses the sprint goal with the team and the Scrum Master. They then collaborate to reach a mutual understanding of the sprint goal and the work needed to achieve it. The Team then estimates ...

Sprint-Planning-140x170

Sprint Retrospective

The Sprint Retrospective, the last ceremony in the Sprint takes place after the Sprint Review and before the next Sprint Planning. The meeting should be time-boxed to no more than an hour per week of Sprint length. ...

Sprint Review Scrum Kaizen

Sprint Review

The Sprint Review takes place at the end of the Sprint and is designed to gather actionable feedback on what the Team has completed. This ceremony, also known as the "Demo", is an exciting opportunity for the team to showcase its work and to inspect ...

Sprint Review cropper

The Daily Scrum

After Sprint Planning, the Team gets to work and meets every day for the Daily Scrum. All team members working on the Sprint Backlog need to attend and should standup to help keep the meeting short (no longer than ...

Daily-Standup

The Scrum Team

The Scrum Team is made up of the people who actually work on Product Backlog Items during a Sprint. In a software context, this group is most often called the Development Team. In other contexts, the simple term Team ...

sl_team_main

The Sprint

The Sprint is the heart of Scrum. It is a short, consistent cycle no longer than four weeks. The goal is to have an iteration short enough to keep the team focused but long enough to deliver a meaningful ...

Scrum Inc. The Sprint

Velocity

Velocity is a measure of the amount of work a Team can tackle during a single Sprint and is the key metric in Scrum. Velocity is calculated at the end of the Sprint by totaling the Points for all fully completed ...

Velocity in Scrum

Yesterday’s Weather

Yesterday’s Weather is a Scrum pattern that helps Teams quickly calculate how many Points they will likely complete in the upcoming Sprint. The name comes from the fact that the best predictor of today’s weather is ...

Yesterday's Weather