There are lots of project management methodologies in modern software development industry. Each of them has a number of terms and notions that are used only in it. For a software developer, it is extremely important to understand their meaning. That is why in this article we will tell you about the terms used in Scrum methodology. But before doing that we have to give the general definition of this project management method.
The first thing you should know about Scrum is that it is the most popular Agile methodology. Like most Agile methods, Scrum originated at the beginning of 2000s. The methodology shares all main Agile principles, including strong customer involvement, iterative structure of projects, and strong communication between the team members. Most developers agree that Scrum methodology is the best for short and not complex projects. However, many teams and companies use it to manage long term projects.
Now let’s return to the main topic of this article and describe Scrum notions.
A Scrum team is probably the main distinctive feature of this methodology. It is a typical Agile team. However, it differs significantly even from the teams of other Agile methodologies. That is because of the fact that a typical Scrum team has only three roles: the team itself, the Product Owner, and the ScrumMaster. To understand the methodology better, it is necessary to describe some of these roles in greater detail.
The Product Owner
A Product Owner is a customer or his representative in the team. He is the person responsible for product backlog formulation and prioritization of its items. The Product Owner must participate at all team meetings, and estimate the intermediate product after each iterative cycle.
A ScrumMaster is a non-formal leader of every Scrum team. He is not a project manager, but more of a coach that helps the project stay Scrum. He teaches the team members how to implement the best Scrum practices and deliver the final product within the shortest amount of time.
The sprint is the name of Scrum iterative cycle. A typical sprint lasts about two weeks. A Scrum team should add new functionality to the product during this period. Each sprint has its own plan that cannot be changed after it was accepted by the team. After the sprint is finished, the Scrum team shows the intermediate product to the Product Owner.
The sprint planning meeting
A sprint planning meeting is a compulsory procedure that is conducted before the start of every sprint. Its main goal is to create a good and realistic sprint backlog. The sprint backlogs are formulated from the items of the product backlog. In Scrum, the developers can reprioritize the product backlog items any moment. After the sprint backlog is formulated, the work on a sprint begins.
The daily Scrum
Daily Scrums are meetings conducted by the Scrum teams every day. Usually, they take place in the morning. These meetings are aimed at defining the advantages and disadvantages of the team’s work during the previous working day.