SCRUM - kirillsats/FirstAppBuketov GitHub Wiki

Scrum is a methodology for organizing a collaborative workflow based on step-by-step development and improvement of a product by a small team of specialists of different profiles.

Scrum refers to a family of flexible Agile methods. Often these two concepts are used as synonyms, but this is incorrect. Scrum is a specific example of the Agile approach. It represents a specific production methodology, while Agile is more of a philosophy or a set of values.

Features of Scrum are team approach and non-standard distribution of responsibilities in the team. Both company employees and business customers are involved in the process.

Why Scrum methodology is needed

The approach is flexible and allows for experimentation, so it is effective when you need to develop a new product quickly. Especially if there is no final vision of the result or market conditions change too often. Scrum helps to gradually move towards the goal and to monitor the effectiveness of the work done along the way.

Principles of Scrum team work

While working according to the Scrum methodology, fundamental principles should be followed:

  • Continuous Improvement. The product improves due to self-improvement of the whole team.
  • Autonomy. Each participant is responsible for his/her part of the work and for the overall result.
  • Cross-functionality. The presence of people with different skills in the team makes it self-sufficient.
Advantages Disadvantages
  • The team works in small increments, where goals and ways to achieve them are defined at each stage, which increases the speed of work. | - Scrum is not suitable for very large and complex projects, as coordination issues may arise.
  • The team works on different tasks of the project simultaneously, achieving the desired goal faster. | - A high level of trust within the team is necessary.
  • Large tasks are broken into smaller ones, making it easy to make adjustments during the work process. | - After an extended period of work, productivity dynamics drop, requiring the team to be restructured or dismantled.
  • Rapid response to changes and error elimination minimizes financial risks. | - The client must constantly communicate with the team and provide feedback.
  • Each team member knows their responsibilities. |  
  • Open information exchange makes the work as transparent as possible. |  
  • Daily visibility of achievements maintains a high level of motivation. |  
⚠️ **GitHub.com Fallback** ⚠️