Scrum is one of the agile methods and is a very efficient way to deal with complex projects with multiple needs. The main focus of this method is on the cooperation and interaction of team members and their communication with each other. This interaction is easily achieved with the help of different roles in the team and multiple meetings in this method. In the following, we discuss the roles, terms and processes of the Scrum method. Look at this picture:
Figure 1-The overall Scrum system
Terms of scrum method:
User Story: Clear definitions and descriptions of expected customer features written by the customer and project managers.
Product backlog: We can think of it as a storehouse of stories and pending tasks that we refer to to make our daily to-do list and select essential items. We call this function "pull" and if nothing is done, it returns to stock (or "push").
Sprint: The individual time periods that are considered for the development of small and broken parts are called sprints. A sprint in the Scrum method depends on factors and lasts between 2 weeks and 4 weeks. In this period, each team member is responsible for the assigned tasks.
Sprint Backlog: A list of tasks to be completed during a sprint. This list is extracted from the product backlog list.
Figure 2-Product backlog
Task: Each item in the sprint backlog that must be done by the team is called a task.
Board: We must have a physical or digital board in all stages of work so that team members are aware of their duties and other team members and can follow the work process and the status of their activities visually. The entries in this board are the backlog of the sprint and are updated every day after the start of the sprint. These tables contain various columns that may be changing. In each method or team, they even have different names. But in the simplest case, at least the following three columns are included:
- pending doing or doing
Figure 3-Board TODO
An example of a board. The tasks in the board have different colors depending on the priority, column or topic to be better categorized. They may also have a series of points according to their degree of difficulty. If we want to explain the above picture:
- The list of completed tasks is injected from the backlog to the board.
- Each person enters his task from the to do column into the ongoing or developing column and starts working.
- After finishing the work, you can enter the code in the column called review, at this stage another person will be responsible for checking these codes.
- The next column is the test column, in this part the tester starts to test the done work. Finally, if everything was correct, the desired task is merged and added to the done column.
Planning meetings: meetings that are held before the start of each sprint and all team members, according to their priorities and available time and ability, with the help of the Scrum Master, start pulling the list from the backlog to the sprint. For this, they add it to the sprint.
Standing meetings: Every day, usually before starting work, meetings are held between team members for 15 minutes, in which they discuss the previous day's work, the problems encountered and the current work plan (these meetings are usually held standing be).
Retrospective Meeting: After the completion of each sprint, a meeting is held where all team members discuss the experiences, learnings, problems, and deficiencies that have been completed in the sprint.
Trial meeting: Depending on the proposal of the project beneficiary or beneficiaries or the client's request, this meeting is held once in every one or more sprints to see a demo or a preview of the results of the completed sprints.
Product owner: As the beneficiary of the project and the representative of the employer, he is responsible for collecting and prioritizing the arrears and determining the road map. It is also in constant contact with the customer and receives and sends feedback.
Scrum Master: A person responsible for sprint planning and work list injection, monitoring progress and timely completion of work, informing members' work and focusing them.
Development Team: A team of people with different expertise who are responsible for the realization of sprint goals. The number of these members varies, but usually they are not more than 10 people. None of these members has superiority or rank over the other and they are always in constructive interaction with each other.
Scrum methodology review: If you are familiar with these terms, how to do this work process:
- The first thing to do is a planning session to determine the speed lag.
- After that, the board is prepared and the work begins, and this work continues until the end of the sprint.
-Every morning in daily or outpatient meetings, we talk about the previous day's work and the current day's plan.
- and after the sprint ends, talks about the experiences of the finished sprint.
- If necessary, a demo meeting will be held with the presence of managers or customers and the results of the work will be displayed. After all this work, this loop is repeated from the beginning and this loop is executed again