Scrum has been used to manage work on complex products since the early 1990s. Scrum falls within “Agile,” which is the umbrella term for several types of approaches to getting any complex, innovative scope of work done. The concept is to break large projects into smaller stages, reviewing and adapting along the way.
The term "Scrum" comes from a 1986 Harvard Business Review article in which authors Hirotaka Takeuchi and Ikujiro Nonaka made an analogy comparing high-performing, cross-functional teams to the scrum formation used by rugby teams.
Glossary of Scrum terms:
The Scrum Master helps the Scrum Team perform at their highest level. They also protect the team from both internal and external distractions.
The Product Owner is expected to do the best possible job of satisfying all stakeholders, maintain the Product Backlog, and ensure that everyone knows the priorities.
The Development Team
Development Teams are structured and empowered to organize and manage their own work. The resulting synergy optimizes overall efficiency and effectiveness.
The Product Backlog is an ordered list of everything that is known to be needed in a product. It is constantly evolving and is never complete.
The heart of Scrum is a Sprint, during which a useable and potentially releasable product Increment is created. Sprints can be one week to one month in length and happen one right after the other to keep projects moving. There are four events that happen with each Sprint:
- Sprint Planning – The Team decides what to work on for the current period.
- Daily Scrum – The Development Team meets for 15 minutes (or less) every day of the Sprint to inspect progress toward the Sprint Goal.
- Sprint Review – The Team collaborates about what was done and adapts the Backlog as needed.
- Sprint Retrospective – The Team discusses what went right, what went wrong, and how to improve.
Want to learn more? Watch our Scrum Alliance eLearning Series.
Tell me why I should get certified.
Companies choose Scrum to deliver more value to their customers and their bottom line.
They have come to understand the value that a Certified ScrumMaster®, Certified Scrum Product Owner® or Certified Scrum Developer® brings to their organization. And they’re willing to pay a premium.
Choose your path:
As a Certified ScrumMaster
, you’ll help the rest of the Scrum Team work together to learn and implement Scrum. Along with the Product Owner, you will work to protect your team from both internal and external distractions.
Ready for your next step into Scrum?
- If you’re someone who is comfortable with the "business side" of projects, you are probably the right person for a Certified Scrum Product Owner certification. You’ll monitor projects, keep tabs on priorities, and make sure the best possible job is done to satisfy all clients (a.k.a. stakeholders).
- As a Certified Scrum Developer, you will help deliver a potentially releasable increment of “Done” product at the end of each Sprint. You’ll be part of a Scrum Team that includes developers who are self-organizing, cross-functional and accountable.
- But it doesn’t stop there. You can advance your role-specific skills and evolve as a Scrum professional with an Advanced Certified ScrumMaster (A-CSMSM), Advanced Certified Scrum Product Owner (A-CSPOSM), Certified Scrum Professional®-ScrumMaster (CSP®-SM), and Certified Scrum Professional®-Product Owner (CSP®-PO) – and more!