Scrum methodology in a nutshell: these are the key elements of scrum and how it works
The scrum methodology is the most widely used methodology in agile project management. It is a framework that has evolved to solve simple, easy-to-understand and explicitly complex problems in an ever-changing environment. Although it is primarily used in software development, it is now increasingly implemented in other areas, such as service development or organisational management projects.
In this article, we will review what scrum is and clarify the most important related concepts and roles.
What is the scrum methodology?
Scrum is a framework that facilitates effective teamwork in complex product development. It is able to accept and manage unexpected events and changing requirements during development and facilitates effective adaptation. The result is more customer-centric, more efficient development, greater cost-effectiveness and reduced risk.
The scrum framework consists of pre-defined elements, all of which serve a specific purpose and are necessary for the methodology to work effectively. The framework is described in a code of practice, the Scrum Guide describe.
The main elements of the scrum methodology:
- The scrum team and its roles
- Ceremonies
- Products
- Rules
The term scrum is derived from rugby, and the methodology is likened to a rugby training session, where team members run and pass the ball between each other. In practice, this means that a small group of professionals with expertise in different areas work together in parallel at all stages of development. This is a big difference from the traditional waterfall method of project management, which is more like a relay race, with different teams of experts working on each phase of development.
What are the elements of the scrum agile methodology?
At the heart of scrum is the scrum team. Various roles, events, work materials and rules are defined around this. Work is done in 1-4 week iterations, in sprints. During the sprints, a working, presentable product part, an incrementum, containing some functionality, is created and presented to the customer at the end of the sprint. Finally, the product is assembled from these increments.
Let's see what the key concepts mean!
Structure of the scrum team: what are the main roles of the Product Owner, Scrum Master and development team?
A scrum team is a small self-organising team, which means that the team organises its own work autonomously. It is important that team members work in the same place and are able to communicate verbally with each other.
Of course, the situation during an epidemic does not always allow this, as we wrote in our article 8 practical tips for scrum masters in times of a pandemic.
The members of the scrum team are the developers, the product owner i.e. product owner and the scrum master i.e. scrum master. In 2020 Scrum Guide update states that these actors are all part of the team and are jointly responsible for the results. But what do these roles mean?
Product Owner
The product owner represents the client during development and is responsible for ensuring that the team focuses on the tasks that are really important to the business and maximises the value created.
Main activities:
- Constantly communicates with the client and the needs from the client's point of view (User Story, Epic) expands the product to-do list, i.e. product backlog
- Manage the Product Backlog in such a way that the items in it are clear and transparent to everyone, and the information is sufficient to work effectively
- Prioritise items according to their business value and the investment required to realise them. In estimating the latter, the development team will support
For the product owner to be successful, it is essential that his or her decisions are respected throughout the organisation and that no other external sources are directly involved.
scrum master
The primary task of a scrum master is to promote the Scrum methodology itself and to support its operation. He or she helps the team to understand the values and rules set out in the Scrum Guide and to apply them as effectively as possible in practice.
The scrum master is a servant supportive leadership role with the ultimate goal of maximising team performance, removing obstacles to work, optimising interactions with external stakeholders. This is a particularly complex activity:
- Agile/lean expert: helps you understand agile values
- Facilitator: helps set the operational framework, moderates meetings, administers, documents
- Coach: helps team members to function and supports organisation and team interactions
- Obstacles: removing obstacles to progress
- Teacher: helps with the introduction of Scrum and other methods
- Mentor: helps to customise Scrum by keeping the essential elements
In practice, it is often the case that someone who has been in a different role is appointed as Scrum Master. We recommend our article "I have been appointed as a Scrum Master, what should I do?
Scrum Development Team (Developers)
The development team is responsible for making the product. It is a small (3-9 people), self-organised and cross-functional team, which means that the team includes representatives from all the disciplines needed to successfully develop the product. The goal of the development team is to have a working, presentable, potentially deliverable increment at the end of each sprint. These increments are selected from the product backlog items at the beginning of the sprint.
Other stakeholders
There are other stakeholders in product development who, although not an integral part of the scrum methodology, need to be continuously involved in product development. These stakeholders include product users, business stakeholders and managers.
What are the scrum ceremonies according to the Scrum Guide?
Scrum events are pre-defined meetings that provide a framework for product development.
Sprint planning (sprint planning)
Prior to each sprint, the sprint planner will meet with you to select from the product backlog the tasks to be completed during the sprint. This is a joint activity between the product owner and the Development Team, where the time needed to complete the tasks is estimated and a promise is made to complete the tasks. It aims to:
- compile the sprint backlog (the sprint to-do list)
- a plan to implement it and to present the completed increments
- and the team is committed to implementing the plan
The duration of sprint planning varies, depending on how many weeks the sprint consists of. Each week should take about 2 hours of planning, so for a 2-week sprint, the sprint planning meeting should take about 4 hours.
Sprint planning is critical to product development, as explained in our post on the 8 steps of sprint planning.
Daily Scrum or Daily Stand-up
This is a short, daily status meeting, lasting up to 15 minutes, aimed at creating focus and coordinating tasks. The following questions should be answered by each participant:
- How have I helped you reach your sprint target since the last meeting?
- What do I plan to do before the next meeting?
- Are there any factors that are preventing me from doing my job?
Sprint Review, Demo (Sprint review)
At the end of each sprint, an overview of what was (and was not) completed during that sprint is given. The completed working increments are also presented to the Product Owner and other stakeholders. The Product Owner is responsible for receiving the completed deliverables. Typical duration is 2-4 hours.
Sprint Retrospective (Retro, retrospective)
The purpose of this often (and wrongly) neglected event is for team members to evaluate the sprint, give their opinions and make suggestions for improving workflow. Its low popularity is due to the fact that people are less inclined to talk about themselves and their mistakes. Developed self-reflection is needed to learn lessons. At the end of the event, concrete actions should be formulated to improve cooperation from the very next sprint.
Scrum Artifacts: Product Backlog, Sprint Backlog and Increment
The products of the scrum methodology are working documents that support product development, make the process transparent and allow progress to be tracked.
Product Backlog (product requirements list)
This is where the high-level requirements for the whole product and their specifications are defined. It is managed by the product owner. The product backlog should include:
- The main functions of the product and the customer's wishes and ideas related to it
- Estimates of the business value of each element and the expenditure required to implement it
- Each element should be ranked in order of priority
Sprint Backlog (Sprint to-do list)
This working document describes what features and how the team will build them during the sprint. The tasks are broken down into subtasks that typically take 4-8 hours to complete. This makes it clear to everyone what needs to be done and allows team members to select the subtasks that are right for them based on their priorities, needs and expertise.
Increment (Incrementum)
An increment is a working and presentable product part at the end of the sprint that meets the Definition of Done criteria set by the team. Each increment adds value to the product and contributes to the overall final product.
A sprint can produce several increments, but only results that are fully completed, integrated and potentially publishable are presented at the sprint review. This means that the increment:
- working, tested and ready to use,
- fits in with the previously prepared increments,
- meets quality standards and the Definition of Done,
- is of value to the customer.
The incrementum is one of the most important products of the scrum methodology, as it is the tangible result through which the progress of the team and the development of the product can be measured.
Scrum progress tracking tools: burndown chart, burnup chart and velocity
Although the use of these tools is not mandatory for scrum to work, they provide useful information on performance and progress. The most common tools are:
- sprint burndown chart: a graph, updated daily, showing how much of the sprint to-do list is left.
- burnup chart: shows the number of tasks completed and the number of tasks on the task list in a graph
- velocity: team's delivery speed, showing the approximate amount of tasks the team can deliver in a sprint.
Want an internationally recognised agile qualification?
Thanks to its simplicity and flexibility, the scrum methodology is becoming more and more common in everyday business practice, and it is already being used successfully in many industries outside software development. However, this simplicity can often be misleading: while the basics are easy to learn, applying it at a master level requires a lot of experience and expertise.
If you need help, our agile coaches, trainers and consultants, who are active as certified scrum masters and product owners and have a background in development, can provide practical solutions and support.
Looking for a hands-on programme where you can experience the most common challenges of the scrum master role? Contact us!
Frequently Asked Questions about the scrum methodology
What exactly does the scrum model mean in practice?
The scrum model is a framework that organises development in short iterations and creates a working product at the end of each cycle. The model is based on transparency, empirical decision making and continuous learning to ensure that the team is always focused on the most important value-creating tasks.
How does the scrum methodology differ from other agile frameworks?
Scrum relies on iterative sprints, continuous feedback and self-organizing teams, while other agile approaches (e.g. Kanban) mainly support a continuous flow or visual workflow. The scrum model offers a more rigid structure with defined roles and ceremonies.
What are the benefits of scrum project management for complex projects?
For complex tasks, the advantage of scrum project management is that it does not try to predict the outcome of the whole project. Instead, the team delivers value in each sprint, so the client sees the outcome incrementally, while the team can continually react to changing needs and new information.
What makes a scrum sprint effective?
The effectiveness of a sprint depends on how accurately the team defines the sprint target, how clear the sprint backlog is, and how consistently the team keeps the focus on the tasks undertaken. A well-defined Definition of Done and regular progress tracking are also key.
When should you use the scrum methodology in a project?
Scrum works best when the requirements can change, the solution is not fully known in advance, and quick feedback loops are needed. It is particularly beneficial in environments where team autonomy and collaboration create significant value.
Why is the scrum agile approach popular in modern product development?
The flexibility of scrum agile allows the team to react quickly to changing expectations and continuous feedback. Iterative operations reduce risk and ensure that each sprint delivers tangible value to users.
How does the Scrum Guide support the work of teams?
The Scrum Guide provides a unified framework that defines roles, events, products and their objectives. This enables teams to work consistently and makes collaboration easier to coordinate at the organisational level.
What are the most common challenges when implementing scrum?
The biggest challenge for many organisations is to make the real shift to iterative thinking and self-organising teams. Shifting from the familiar hierarchical way of working takes time, confidence and practice. Without clarification of roles and consistent adherence to ceremonies, scrum agile can easily become distorted.
