{"id":20889,"date":"2021-06-12T04:26:29","date_gmt":"2021-06-12T04:26:29","guid":{"rendered":"https:\/\/studioventuras.com\/what-you-need-to-know-about-scrum\/"},"modified":"2025-04-01T02:45:21","modified_gmt":"2025-04-01T02:45:21","slug":"what-you-need-to-know-about-scrum","status":"publish","type":"post","link":"https:\/\/studioventuras.com\/en\/what-you-need-to-know-about-scrum\/","title":{"rendered":"What you need to know about Scrum"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Today it’s Scrum’s turn! You’ve already read about agile methodologies<\/a> in general, you’ve delved into the Kanban methodology<\/a>, and now you’re going to get a better understanding of how Scrum, this famous task planning and management framework, works! <\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

What is it and how did it come about? <\/em><\/h2>\n

The history of Scrum began in 1986 with the article “The New Product Development Game”, published in the Harvard Business Review and written by Hirotaka Takeuchi and Ikujiro Nonaka. In it, the authors explain how the process of developing and producing products is carried out by multidisciplinary teams working together from start to finish. <\/p>\n

Inspired by the article, in 1993 Jeff Sutherland and his team at Easel Corporation created the Scrum process, which was presented by Jeff himself and Ken Schwaber in 1995 at the OOPSLA Conference. <\/p>\n

Scrum is a term used in Rugby and refers to the act of restarting the game when there is a foul or when the ball goes out of play. With this, you can already see a little of the logic of this methodology: the importance of closely monitoring each stage of the process and thus, the moment an error is identified, turning your efforts to correcting it. <\/p>\n

In this sense, in Scrum, the project is divided into small cycles (iterations) of activities, called Sprints. Each Sprint corresponds to a predetermined time interval in which the tasks must be carried out by the team. This structure makes it possible to constantly monitor the project, making room for frequent feedback and changes in planning. <\/p>\n

In order for everything to work and for the project to be delivered with the quality and in the short time proposed by Scrum, the team must be aware of all the activities and tasks. In this way, the work must be collaborative and well visualized by everyone. Transparency is a super-important point in this methodology. <\/p>\n

Scrum has many peculiarities, which is why it’s interesting to analyze how it actually works, examining each stage of its cycle and the terms used.<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

How does it work?<\/em><\/h2>\n

To begin with, let’s remember how the team is divided:<\/p>\n

    \n
  1. Product owner<\/strong>: is responsible for creating the product backlog<\/b>, i.e. the set of functionalities of the product being developed. They take care of the technical side, acting as a mediator between the client and the team. <\/li>\n
  2. Scrum master<\/strong>: is responsible for ensuring that Scrum is being applied correctly (reinforcing its values, principles and practices), for removing obstacles during the process and for organizing meetings. He acts as a facilitator. <\/li>\n
  3. Development\/Scrum team<\/strong>: the team, which is multidisciplinary and self-organized, is responsible for developing and testing the product. Everyone works together and the team usually consists of 6 to 10 people. <\/li>\n<\/ol>\n

    Knowing this, we can move on to the process. The first step is analysis and planning by the Product Owner. As we’ve just said, he’s going to make the Product Backlog<\/b>, with what should be prioritized during the project. <\/p>\n

    The project is then divided into Sprints, each of which usually lasts between 2 and 4 weeks. There is a meeting between the team so that everyone can visualize and understand the tasks and how the process will be carried out. Then, with the tasks listed in the Product Backlog, it is decided what will be done in each Sprint, and then these activities are moved from the Product Backlog to the Sprint Back<\/b>log. <\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t
    \n
    \n
    \n
    \n
    \n
    \n
    \n
    \n
    \n
    \n
    \n
    \n

    Four types of meetings are held throughout the process: the Sprint Planning Meeting<\/b>, the Daily Scrum<\/b>, the Sprint Review Meeting<\/b> and the Sprint<\/b> Retrospective<\/b>.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

    \n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"