{"id":84682,"date":"2025-04-10T20:10:55","date_gmt":"2025-04-10T20:10:55","guid":{"rendered":"https:\/\/mailrelay.com\/glossary\/scrum\/"},"modified":"2025-04-10T20:10:59","modified_gmt":"2025-04-10T20:10:59","slug":"scrum","status":"publish","type":"glossary","link":"https:\/\/mailrelay.com\/en\/glossary\/scrum\/","title":{"rendered":"Scrum"},"content":{"rendered":"\n

Scrum is an agile framework that helps teams work incrementally by delivering products in short cycles called sprints. <\/strong><\/p>\n\n

Each sprint usually lasts two to four weeks<\/strong>, and by the end of that period, the team delivers a functional version of the product or a significant part of it. <\/p>\n\n

Scrum’s main goal is to promote adaptability and transparency<\/strong>, helping teams adjust their work as project requirements and conditions change<\/strong>.<\/p>\n\n

The term “Scrum” comes from rugby, where a scrum is a formation that brings the team together to push the ball forward. <\/strong><\/p>\n\n

Similarly, the Scrum team works in short, coordinated cycles, making steady progress <\/strong> toward the final goal.<\/p>\n\n

Roles within Scrum<\/h2>\n\n

To better understand how Scrum works, you need to know the key roles:<\/p>\n\n

Product owner <\/h3>\n\n

This person manages and prioritizes the product backlog\u2014<\/strong>the list of tasks or requirements needed to complete the project. <\/p>\n\n

Their job is to keep the team focused on the tasks that deliver the most value to the client or company.<\/p>\n\n

Scrum Master <\/h3>\n\n

This role is vital to ensuring the team follows Scrum principles and practices. <\/p>\n\n

The Scrum Master serves as a facilitator<\/strong>, assisting the team in removing obstacles that could impede progress. <\/p>\n\n

They also encourage open communication and help create a collaborative work environment.<\/p>\n\n

Development Team <\/h3>\n\n

It\u2019s made up of cross-functional professionals who collaborate to deliver the product at the end of each sprint. <\/strong> <\/p>\n\n

This team is autonomous and manages its own workflow to achieve the goals of each sprint. <\/strong><\/p>\n\n

Scrum Artifacts<\/h2>\n\n

Scrum artifacts provide transparency and help track the project’s progress. <\/strong> <\/p>\n\n

The main artifacts are:<\/p>\n\n

Product Backlog<\/h3>\n\n

It\u2019s a prioritized list <\/strong> of all the tasks, features, and improvements required for the project. <\/p>\n\n

The Product Owner maintains and prioritizes the backlog based on the value each task brings to the client.<\/p>\n\n

Sprint Backlog <\/h3>\n\n

This list contains the tasks chosen from the product backlog to be completed during a specific sprint. <\/p>\n\n

The development team decides how many tasks it can complete <\/strong> during the sprint, making sure the goal is achievable.<\/p>\n\n

Increment <\/h3>\n\n

It is the tangible result of each sprint. <\/strong><\/p>\n\n

At the end of each sprint, the team should deliver a usable product increment, even if it\u2019s not the final version.<\/p>\n\n

How does Scrum work?<\/h2>\n\n

Scrum is structured in a series of events that are repeated throughout the project lifecycle. <\/p>\n\n

The most important ones are:<\/p>\n\n

Sprint planning <\/h3>\n\n

Before a sprint begins, the team holds a meeting to plan which tasks from the backlog will be prioritized in that sprint. <\/p>\n\n

The goal is to ensure team alignment and establish a clear scope.<\/p>\n\n

Daily Scrum <\/h3>\n\n

Also known as the daily stand-up<\/strong>, this is a brief 15-minute meeting held each day where every team member answers three key questions: <\/p>\n\n