Perfecting Scrum Basics
Find clear definitions and the original thinking behind the core Scrum Framework.
One of the core principles in Scrum is the idea of continuous improvement. Each Sprint the Team engages in an inspect-and-adapt cycle during the Retrospective meeting. Beyond that though, the Scrum Guide doesn’t offer much insight into how to run a successful Retrospective and how to use the meeting to improve production, quality, and velocity. Visit the full course page.
How To Launch a Scrum Team
Join us as we share how we help clients launch teams. We share our step-by-step backlog for launching new teams or reinvigorating old. Three different perspectives from three Scrum Inc. coaches on what to do, what the common impediments are, how to avoid the worst and conquer the inevitable. Visit the full course page.
All Topics on Scrum Basics
Product Backlog Items (PBI) Product Backlog Items (PBIs) are the elements that make up the Product Backlog. Estimated time for this course: 5 minutesAudience: BeginnersSuggested Prerequisites: Scrum Framework Upon Completion you will: Know what kinds of items can be...read more
Product Owner The Product Owner is the Team member who knows what the customer wants and the relative business value of those wants. He or she can then translate the customer's wants and values back to the Scrum team. Estimated time for this...read more
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...read more
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 increment of work. Estimated time for this course: 5...read more
Scaling Agile for the Enterprise Scaling Agile for the Enterprise is a challenge that many large organizations face as they implement Scrum Teams across more and more of their operations. Coordinating multiple Teams that are working on multiple projects can seem…read more
Scrum Pitfalls Part I The iterative nature of Scrum is a risk management mechanism that, even when poorly implemented, usually results in at least a 30% improvement in productivity. The rules of Scrum are simple and straightforward, and the underlying principles are...read more
Why Management Needs Scrum The question is always the same: “How do I deliver the best product for the lowest cost and the highest profit?” Scrum has repeatedly answered this question, but often management still has a hard time grasping the business case for…read more
Agile Contracts As Scrum and Agile practices become mainstream and fundamentally change the way companies work internally, it is only natural that the way companies work with each other will also change. Unfortunately, many procurement departments are ill equipped to…read more
Sprint Burndown Chart The Sprint Burndown Chart makes the work of the Team visible. It is a graphic representation of the rate at which work is completed and how much work remains to be done. Estimated time for this course: 8 minutes Audience: Beginner Suggested...read more
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 User Stories. Estimated time for this course: 5...read more
Impediments An Impediment is anything that keeps the Team from getting work Done and that slows Velocity. Impediments come in many forms: a sick team member, a missing resource, lack of management support or even a cold team room. If it's blocking the team from doing...read more
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 Team and shows all items...read more
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. Estimated time for this...read more
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 the Sprint Planning Meeting....read more
Product Backlog Refinement Because requirements in Scrum are only loosely defined, they need to revisited and clearly defined before they come into the Sprint. This is done in during the current sprint in a ceremony called Product Backlog Refinement....read more
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...read more
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. The Scrum Master facilitates...read more
Potentially Shippable Product A 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 because when work is divided into...read more