What is Scrum?
Scrum is a simple framework that helps you and your team build complex products. In other words, it provides a structured approach to development, which improves teamwork and efficiency.
Scrum focuses on learning through experience. You don’t need all the answers at the start. Furthermore, it recognises that the team doesn’t have all the answers. As a result, you adapt as the project progresses. Therefore, Scrum allows teams to adjust based on real-time feedback.
Scrum is designed to respond quickly to changing conditions. It uses short-release cycles. Which means you can continuously improve the product. Thus, teams can adapt to needs as they arise.
Scrum is based on four key principles:
- Creating cross-functional teams
- Establishing a regular rhythm (i.e. sprints)
- Delivering working software at the end of each sprint
- Having team members work together to inspect and adapt their process
The Scrum GuideTM helps people, teams, and organisations create value with adaptive solutions for complex problems.
The Origins of Scrum
The origin of Scrum can be traced back to 1986. It began with a Harvard Business Review article titled “The New New Product Development Game” Which was written by Hirotaka Takeuchi and Ikujiro Nonaka. They used examples from companies like Honda, Canon, and Fuji-Xerox to show how they developed products with different principles than their competitors. They saw their new processes as ways to develop products quickly and flexibly without the limits of outdated organisations.
Takeuchi and Nonaka used sports as metaphors to describe how these companies worked together. They focused on a new rugby-like approach, where the team moves as one working toward a single goal and overcoming obstacles along the way.
Scrum, a software development process, emerged in 1993. Jeff Sutherland, John Scumniotales, and Jeff McKenna were the first to implement it at the Easel Corporation.
In 1995, Jeff Sutherland and Ken Schwaber jointly presented a paper, ”The SCRUM Development Process”, at Object-Oriented Programming, Systems, Languages & Applications (OOPSLA) Conference ‘95 in Austin, Texas.
In 2001, seventeen software developers, including Sutherland and Schwaber, met in Snowbird, Utah, to discuss the future of software development. This led to The Agile Manifesto., urging developers worldwide to adopt a new approach to software development.
Since then, Scrum has been adopted by a growing community, creating high-performing teams worldwide.
Scrum Teams

A Scrum Team is a problem-solving unit. It consists of three roles:
- Scrum Master
- Product Owner
- Developers
A few people – often fewer than 10 in total. They come to solve complex problems and produce products and services that delight customers.
What makes the unit unique? They often don’t have all the answers at first. But each member brings passion, expertise, and creativity. By working together, they find new ways to help customers. Whether creating something new or solving tough problems, they work hard to deliver valuable solutions. This is why the Scrum Team is key to driving continuous improvement.
Learn more…
Scrum is an Agile framework co-created by Jeff Sutherland and Ken Schwaber after years of working with…
Yes, they do. Whilst Scrum and the Agile Manifesto were initially created by software engineers to help…
Continue Reading Do Scrum Masters work outside of Software Engineering Environments?
In short, no, you don’t need project management experience to become a Scrum Master. Project Managers have…
Continue Reading Do you need project management experience to become a Scrum Master?
A Scrum Master differs from a Project Manager in so many ways. Project Managers are traditionally interested…
Continue Reading How does a Scrum Master differ from a Project Manager?
They can be. There is nothing in the Scrum guide or framework that prevents a software developer…
Continue Reading Is a Scrum Master a member of the development team?
The difference between a Scrum Master and a Product Owner really boils down to their focus. A…
Continue Reading What is the difference between a Scrum Master and a Product Owner?
Can’t find what you’re looking for? Check out our frequently asked questions or our roles pages for more on Scrum.
How can we help?
Need help applying Scrum in your organisation?
Book a call to see how we can help you or
check out our Introduction to Agile & Scrum course to help refresh your knowledge.