What is Scrum?
Scrum is an agile framework for teamwork, emphasizing iterative development and continuous improvement. It is based on three pillars: transparency, inspection, and adaptation, working in short, focused cycles called Sprints. Scrum teams are comprised of a Product Owner, Scrum Master, and Developers, with specific roles and responsibilities. The Scrum Guide, written by Ken Schwaber and Jeff Sutherland, provides a detailed explanation of the framework, including its five events, three artifacts, and overarching principles. Trust is crucial for a Scrum Team's success, as it fosters a collaborative environment where the Scrum Values—Courage, Focus, Commitment, Respect, and Openness—are embraced.
Professional Scrum goes beyond the mechanics of the framework, requiring mindset shifts and a supportive environment. This involves adopting the Scrum Values and embracing a continuous learning mindset. The Scrum community offers a wealth of resources, including The Scrum Guide, the Scrum.org Blog, and the Scrum Forum, providing valuable insights, guidance, and opportunities for interaction with other practitioners. This comprehensive approach ensures the effective implementation of Scrum, leading to improved team collaboration, increased value delivery, and a culture of continuous learning.
If you are just getting started, think of Scrum as a way to get work done as a team in small pieces at a time, with continuous experimentation and feedback loops along the way to learn and improve as you go. Scrum helps people and teams deliver value incrementally in a collaborative way. As an agile framework, Scrum provides just enough structure for people and teams to integrate into how they work, while adding the right practices to optimize for their specific needs. You may be thinking, that sounds great! But, how do I get started?
It starts with understanding the Scrum framework which is defined in The Scrum Guide and was first introduced to the world in 1995 as a better way of team collaboration for solving complex problems. The Scrum framework is fairly simple being made up of a Scrum Team consisting of a Product Owner, a Scrum Master and Developers, each of which have specific accountabilities. The Scrum Team takes part in five events and produces three artifacts. Scrum co-creators Ken Schwaber and Jeff Sutherland wrote and maintain The Scrum Guide, which explains Scrum clearly and succinctly. The guide contains the definition of Scrum, describing the Scrum accountabilities, events, artifacts and the guidance that binds them together.
So, why is it called Scrum? People often ask, “Is Scrum an acronym for something?” and the answer is no. It is actually inspired by a scrum in the sport of rugby. In rugby, the team comes together in what they call a scrum to work together to move the ball forward. In this context, Scrum is where the team comes together to move the product forward.
Scrum is an empirical process, where decisions are based on observation, experience and experimentation. Scrum has three pillars: transparency, inspection and adaptation. This supports the concept of working iteratively. Think of Empiricism as working through small experiments, learning from that work and adapting both what you are doing and how you are doing it as needed.
One critical Scrum Team characteristic that binds all of the elements together is Trust. If Trust is not present on a Scrum Team, there will likely be tension and bottlenecks in the way of getting work done. The Scrum Values are also critical for Scrum Teams to adhere to as they help to guide how you work and drive trust. The Scrum Values of Courage, Focus, Commitment, Respect, and Openness, are all important elements that Scrum Team members must consider when working together. The Scrum Values are particularly important in environments where experimentation is core to making progress.
In a nutshell, Scrum requires an environment where:
- Increments of valuable work are delivered in short cycles of one month or less, which are called Sprints. Ongoing feedback occurs during the Sprint, allowing for inspection and adaptation of the process and what will be delivered.
- The Scrum Team has a Scrum Master, a Product Owner and Developers, who are accountable for turning the selection of the work into an Increment of value during a Sprint.
- The Scrum Team and other members of their organization, business, users or customer-base known as stakeholders, inspect the results of the Sprint and adjust for the next one.
If this is Scrum, what is meant by Professional Scrum?
To be effective with Scrum requires something more than just following the mechanics and fundamentals of the framework. Sometimes Scrum Teams fall into the habit of simply going through the motions. Professional Scrum requires mindset changes for ways of working and thinking, and an environment that supports it including trust. It also requires you to embrace the Scrum Values in your work. We call this Professional Scrum.
Learn more from the Scrum Community
There are many books, presentations, videos and other resources to help you learn Scrum, but it all starts with The Scrum Guide, which is considered the definition of Scrum.
We recommend that you read insights from the experiences of Professional Scrum Trainers (PSTs) who are experts in their field as well as expertise from Scrum.org staff on the Scrum.org Blog. Articles, white papers, videos, webinars and other materials are published regularly by the community and are available in the Resources section of our website as well. Lastly, if you have questions or want to learn from what questions others have had, check out the Scrum Forum as an additional way to connect with and learn from the community.
In this 18 part series of short Scrum Tapas videos, Professional Scrum Trainer Ryan Brook walks viewers through the Scrum Framework piece-by-piece, explaining each area and providing insights into how Scrum is used.