How is the team's work organized?

[sadiksojib35]

Backlog creation. The product owner creates the most complete list of requirements for the product functionality. The team evaluates the complexity of each task on a relative scale (for example, assigning a number of points from the Fibonacci sequence to the task: 1, 2, 3, 5, 8, 13, …). It is important to note that the complexity of tasks cannot be estimated by the number of hours planned to be spent on its implementation. Firstly, people are poor at this, and secondly, scrum teams increase their productivity very quickly, and by the third or fourth sprint they are already working several times more efficiently than at the beginning of the work.

The product owner then organizes the list by determining which tasks

are of the greatest importance for the progress of the project;
most important for the customer or future consumer;
will bring maximum income;
the easiest to do.
In this way, a project backlog is formed – a list of argentina phone number lead requirements for the functionality of the product, ordered by the degree of importance of the tasks to be implemented.

Sprint planning. This is a meeting where the team looks at the top of the backlog and estimates the number of tasks that can be completed in the sprint. Once the team has agreed on the goal of the upcoming sprint and a specific number of tasks to complete in the sprint, no more tasks can be added. Sprint planning is another opportunity for the team to make sure everyone understands how each task contributes to the end goal of the project.

Scrum board and task burndown chart. Transparency of all actions and processes contributes to well-coordinated teamwork. To do this, the team creates a scrum board with columns: “Need to do”, “In progress”, “Done”. All tasks that the team has chosen to implement in this sprint are written on stickers and glued to the “Need to do” column. As the tasks are completed, the team moves the stickers from one column to another. Another way to make the work visible is to create a task burndown chart. Every day, the scrum master calculates the number of points for completed tasks and displays the remaining amount on the graph. Ideally, by the end of the sprint, the curve should reach zero.