Understand how it works and when to use the Scrum methodology

Scrum is the name of a methodology based on agile principles, created with the objective of managing projects and delivering value to the customer in a fast and continuous way.

The concept can help in the productivity of companies, as it allows adapting the product to changes in the market and user needs, in addition to bringing other benefits.

According to an article published by UFCG (Federal University of Campina Grande), the emergence of agile methodologies like this is a reflection of continuous changes in different contexts, including project development.

According to the study, the method was created in 1993, with principles and values ​​defined a few years later.

Despite the benefits, the article also warns of possible management problems caused by incorrect implementation of the method, identified by Jeff Sutherland, one of the creators of the concept.

Understanding how the methodology works is a step that can avoid these problems in the company.

What is scrum?

Developed to manage agile projects, scrum is a structure that brings together a set of practices, tools and principles with the aim of guiding teams to organize themselves with a focus on adaptation.

The management tool’s main function is to allow the teams to self-organize, as well as to seek efficient management of projects, according to article published by the Federal University of Campina Grande, previously highlighted.

According to Jeff Sutherland, one of the main developers of the method and author of the book “Scrum: The art of doing twice the work in half the time”, the framework has Japanese roots.

The author tested the concept for the first time after reading an article published by the Harvard Business Review, authored by two Japanese business professors.

In his book, Sutherland says that the article compares the performance of the best development teams to a rugby formation with the same name as the method.

In sport, the technique consists of bringing the whole team together for the same objective: to gain possession of the ball.

Scrum vs Agility: what are the differences?

Although complementary, scrum and agility are not synonymous. While the first concept is a specific method of organizing work, agility has a broader definition and is a way of thinking.

Agility does not determine a single way of doing things, but brings together a set of values ​​and principles that can guide different types of work.

In practice, this philosophy encompasses several agile methodologies, including the scrum framework – which can be applied to achieve more agility in processes.

Other differences between the concepts can be found in the Agile Manifesto, the document responsible for defining the method structured by Jeff Sutherland.

Along with 16 other authors who used different agile methods, according to the UFCG article, Sutherland created the Manifesto in 2001.

It is possible to verify these definitions that list values ​​and differentiate the methodology of agility, such as:

• working software above documentation;
• responses to change above following a plan;
• collaborating with the client above negotiating contracts;
• individuals and interactions over processes and tools.

How does scrum work?

The concept divides projects into short cycles called sprints, which last from two to four weeks and involve four main ceremonies:

• sprint planning (planning meeting): moment in which the person responsible for the product presents the desired requirements for the project and the team defines tasks;
• daily meetings: quick meetings to monitor the development of activities and possible difficulties;
• sprint review (review meeting): demonstration of results to the person responsible for the product and feedback to validate the delivery;
• sprint retrospective (retrospective meeting): analysis on team performance and project results.

Each sprint has a specific duration and a set of goals to achieve. Deliveries made at the end of each cycle aim to add value to the business.

What is the importance of scrum?

The project management method can bring many benefits, such as better quality, higher return on investment, shorter delivery time, greater collaboration between team members and greater employee satisfaction.

In search from the Federal University of Itajubá, carried out with a small technology company, it was concluded that the application of the framework improved communication, reduced costs and optimized the time invested in tasks.

In addition, the study pointed to other benefits identified during the analysis, such as increased productivity and team motivation, reduced risks in the development of new products and increased customer satisfaction – with a reduced complaint rate.

As a result of these benefits, the analysis identified a gain in competitive advantage for the company.

In his book, Jeff Sutherland cites productivity as one of the main positive factors of the method. The author highlights that the correct implementation of the concept can bring an improvement between 300% and 400% in the productivity of the team.

Principles of scrum methodology

The methodology is based on a series of principles, which serve as a guide for implementation, with adaptation, transparency and inspection being the three main pillars.

Know the principles:

• focus on value : the team must prioritize activities that generate more value for the customer, according to the product backlog;
• adaptation : ability to adapt the project according to changes in the process and customer needs;
• transparency : project information, such as scope, priorities and progress, must be accessible to everyone involved in the process;
• inspection : the work carried out must be monitored, verified and evaluated throughout the cycle, in daily, review and retrospective meetings;
• collaboration : the team’s work must be collaborative and integrated, sharing knowledge, solutions and responsibilities;
• autonomy : the team must have the autonomy to organize tasks and define how to perform each one of them, according to guidelines from the leader and the person responsible for the product.

What are the Scrum artifacts?

Research by the Federal University of Itajubá also clarifies the artifacts used by the methodology, which involve a set of rules and management practices.

Understand what these artifacts are, according to the study.

product backlog

Product backlog, or product backlog, is a list of features to be developed during sprints, usually defined in the planning meeting, held with everyone involved in the process.

This list is prioritized according to the purpose and needs of the project.

sprint backlog

This is a subcategory of the product backlog, whose function is to define the list of specific features for each sprint, as well as to distribute roles and responsibilities.

The determination also happens in the planning meeting and can be evaluated during the sprint reviews, which take place at the end of each sprint and serve to analyze mistakes, successes and points of improvement for future projects.

increment

The increment, also known as the sprint goal, is the deliverable that comes from a cycle. It is the final usable version of the product presented to the customer, which will be evaluated and receive feedback.

It is a way to add value to the product and can be added as backlog items are completed. These are details that can be integrated into the product, contributing to the consumer’s experience.

Another artifact cited by the article is the burndown chart, which tracks the progress of each sprint. He is responsible for indicating how much work has been done and what still needs to be done on the project.

Members of a Scrum Team

The structure of this agile methodology also has a group of professionals, responsible for executing the sprints.

This team meets during the method’s events, such as the planning meeting and daily meetings, with the aim of aligning goals, monitoring the progress of actions and making adjustments when necessary.

In this scenario, the UFCG study highlights three roles of the structure.

responsible for the product

The product owner, or person responsible for the product, has the function of defining and prioritizing the product’s functionalities, representing the needs of customers and stakeholders.

Scrum Leader

The leader, also called the scrum master, is the facilitator and guardian of the process. He is responsible for helping the team follow the principles and practices of the methodology, as well as for resolving conflicts.

In addition, this professional also values ​​the continuous improvement of the team and seeks to remove possible impediments throughout the process.

Development team

The development team is the group of professionals responsible for executing the tasks and producing the project deliverables.

This team is self-organized and works collaboratively to achieve the goals defined in each sprint.

When is the Scrum methodology recommended?

The method is indicated to organize more dynamic projects, which tend to change during development. Typically, they involve smaller, multidisciplinary teams.

Therefore, this agile methodology is usually applied by organizations in the field of technology, in processes such as software development, for example.

In this process, tests and adaptations take place to ensure that the software is working correctly when it reaches the final consumer.

In addition, the technology sector grew by more than 60% during the pandemic, which also drives the search for techniques to meet market demands and changes.

Despite being more common in the technology area, the concept can be implemented by companies of different sizes and segments, in projects that seek to deliver value to the customer quickly and continuously.

Catch the top tech news on CNN