Scrum Methodology
The Scrum methodology is, in essence, a framework for developing products and services. Known as the most widely used framework worldwide, it’s likely that you’ve already heard of Scrum, its artifacts, and events. This Agile framework follows the Scrum Guide, which, although a brief document, is highly comprehensive and explanatory. In the Scrum Guide, basically, you’ll find all the information you need on how Scrum functions, the roles within Scrum, and the responsibilities of each role. Additionally, it also explains the reasons behind each element, the benefits, and when to use the Scrum framework. Be sure to read the guide, especially since a new version was released at the end of 2020, which clarified and refined certain aspects of Scrum.
Scrum is based on the pillars of empiricism and Lean thinking. Now, let’s dive into a more detailed exploration of this framework.
The Scrum Methodology Process
Before the Sprint in Scrum Methodology
In Scrum, the client, known as the Product Owner, creates a prioritized list of requirements called the Product Backlog. Then the team organize these requirements into themes, epics, and stories:
- Themes: A grouping of requirements.
- Epics: Large requirements that the team has not detailed yet.
- User Stories: Detailed requirements seen from the perspective of the product user.
Next, the team estimates these requirements by the team using techniques such as Planning Poker. During Sprint Planning, the Product Owner describes the prioritized requirements to the team, enabling a more detailed plan for the activities needed to develop these priorities. Based on this plan, the development team confirms the requirements to be addressed in that Sprint. If it’s not possible to complete all the requirements within the available time, the team and Product Owner negotiate the deliverable requirements, considering their complexity and priority.
The team then decides how to implement the requirements and updates the Sprint Backlog.
During the Sprint in Scrum Methodology
The team has a set amount of time—usually between 1 to 8 weeks—to complete their work. Every day, the team holds a meeting to assess progress (Daily Scrum). During this period, the Scrum Master ensures that the team remains focused on its objectives.
The Sprint concludes with a Sprint Review, where the team presents the product to the client and stakeholders. Finally, the team gathers to conduct a Sprint Retrospective. This reflection on past performance helps improve processes for future Sprints.
At the end of the Sprint, the work should be ready for delivery to the client and integration into the existing product. The first delivery to the client is typically the Minimum Viable Product (MVP).
New Sprint
When a new Sprint begins, the client and team select additional items from the Product Backlog to work on, repeating the entire process until the final Sprint. This approach brings the team closer to the client, allowing for ongoing validation of progress and adjustments as necessary. While there may be mistakes along the way, these will be identified sooner, making them more cost-effective to fix. As a result, it increases client satisfaction and project success.
Next, we recommend reading the post about Scrum Certification and the Scrum Master course.
For a deeper understanding of the Scrum Methodology, we suggest the following courses: