SCRUM Methodology

The SCRUM methodology is a flexible project management using certain principles and practices. According to SCRUM, a team of employees working on a project must adhere to the principle of self-organization, gradually develop and improve their project, and analyze successful experience and mistakes for further development.

When using the SCRUM methodology, a team approach is practiced to solve assigned tasks, non-standard distribution of roles and functions of project participants, and not only employees-performers, but also customers of the product are involved in the work process.

The work process according to the SCRUM methodology includes the following stages:

1. The customer develops technical specifications for the team based on customer needs and general demand for the product.
2. Formation of a team of 6-10 specialists of various profiles. The general scheme of the team includes the customer, Scrum master (a person who does not participate in the development of the product, but monitors compliance with the SCRUM principles and solves emerging problems) and developers.
3. Design and plan short cycles or sprints, during which a team works on a specific project task. A sprint is completed when the team has delivered a finished product to the customer within the established time frame.
4. Daily team gatherings for a Scrum meeting or a standup. At each meeting, the team is asked questions about the work done since the last standup, the tasks for today, and the problems that prevent them from being completed. Based on the results obtained after the meeting, the Scrum Master analyzes the workflow and, if necessary, helps solve the problems that have arisen.
5. To ensure visibility of the workflow, the team uses a Scrum board, which is a visual diagram that shows which tasks have been completed, which are in active work, and which are coming in the future.
6. Analysis of the results of each sprint.
7. After finishing the work on the product, the results for the reporting period are summed up. Each developer reports on their results, which are assessed by the rest of the team. Then the customer makes a decision on the implementation of the resulting product.

See also