Scrum Methodology: The Complete Guide and Best Practices

The world has changed. Why is this happening? Smartsheet transforms your work.

Scrum is a common method for managing digital projects.
A Project Management Institute study found that Scrum is used at least partially by more than half of project managers who use an agile framework (75%).
A PMI survey found that 55% of organizations use Scrum. Source: Project Management Institute
A PMI survey found that 55% of organizations use Scrum. Source: Project Management Institute
This article will cover the history of agile Scrum, key terms and the important things you need in order to use Scrum in your projects.
Here’s a table that allows you to jump to the sections that interest you:
What is Scrum Methodology?
A Brief History of Scrum
Scrum vs Agile
Scrum vs Kanban
What are the Scrum Principles?
What are the 3 Artifacts of Scrum?
The Scrum FrameworkScrum RolesScrum Development Team
Scrum Master
Product Owner

Scrum Meetings (a.k.a. Scrum Ceremonies
Sprint Planning Meeting
Sprint Review Meeting
Sprint Retrospective Meeting

Scrum Software
Best Scrum Resources
Scrum Terms
What is Scrum Methodology?
Scrum methodology can be described as a project management approach that proposes principles and processes to improve delivery.
Scrum project management solves the time and cost requirements for projects. Scrum uses time boxes, backlogs, and meetings to achieve this. It’s highly adaptable and helps to complete projects faster. Projects are managed using Scrum. They move through sprints. Each sprint produces a deliverable increment.
Scrum is a framework that empowers teams to create healthy tension between delivering the right things, the right way, and as quickly as possible.
Scrum’s goal is to improve communication, teamwork and speed of development. Scrum is the foundation of concepts such as Sprints (or Scrums), Backlogs (or Burndown), and other concepts like Backlogs or Scrums.
A Brief History of Scrum
1986: Hirotaka Takeuchi, Ikujiro Noaka publish “New Product Development Game” in Harvard Business Review.
1995: Jeff Sutherland, Ken Schwaber present Scrum to OOPSLA.
2001: Sutherland and Schwaber, along with 15 other developers, create the “Manifesto of Agile Development.”
2002: Schwaber starts the Scrum Alliance, and offers Scrum certification.
2016: Formalization of the first fully scalable Scrum.
1986
1986 was the year that Scrum was first started. Hirotaka Takeuchi (Japan) and Ikujiro Noaka (Japan), published the article “New New Product Development Game” within Harvard Business Review. This was the first time that product development could be done faster and more easily.
It would take Jeff Sutherland nine more years to develop Scrum.
1995
Sutherland and Ken Schwaber, his work partner, made Scrum a formal process in 1995. The idea was presented at the Object-oriented Planning, Systems, Languages and Applications Conference (OOPSLA).
This was Scrum’s debut to the outside world.
2001
In 2001, Sutherland and Schwaber created the “Manifesto For Agile Software Development” and shortly thereafter published the first book about Scrum and Agile development.
2002
Scwaber created the Scrum Alliance in 2012 and began offering ScrumMaster certification. Over 100,000 people have been certified in Scrum to date.
2016
Scrum continues to evolve. In 2016, the first fully scalable Scrum was established. Scrum recognizes the importance of distributed teams and two Product Owners. Scrum is gaining popularity and more organizations are now willing to use Scrum to organize their teams.

Previous post Scrum Master vs Project Manager vs Product Owner
Next post SDLC in Project Management (All SDLC phases with examples)