Scrum

Scrum only contains a small number of rules. These rules define the five activities, three artefacts and three roles, that form the core of scrum. The rules are defined in the Agile Atlas or in the Scrum Guides. The Scrum framework must be represented by the techniques to implement activities, artefacts, and roles in order to allow Scrum to actually be implemented. The core of Scrum is decoupled from the implementation method in order to define the main elements and working mechanisms and also provide greater freedom to individual projects. The Scrum approach is empirical, gradual, and iterative. It is based on the experience that many development projects are too complex to be included in the master plan. The solution that many requirements seem to be is not initially clear. This ambiguity can be resolved by generating an interim result. Using this interim result, you can find missing requirements and solution techniques that are more efficient than abstract clarification steps. Alongside products, plans are also developed iteratively in phases in Scrum. The long-term planning (product backlog) is continuously improved and perfected. The blueprint (sprint backlog) is only created for the next cycle (sprint). This means that the project planning is oriented towards the substance. Empirical improvement is based on three pillars: Transparency: Project progress and failure are regularly recorded and made visible to everyone. Evaluation: Product properties are regularly provided and products and processes evaluated. Adapt: Product, plan and process requirements are not only specified once, but continuously refined. Scrum does not reduce the complexity of the task, but improves the structure in smaller and less complex components. The aim is to quickly and economically develop high-quality products according to the established vision. Implementing a vision in a finished product does not mean creating detailed specifications. In Scrum, requirements are formulated as properties from the user perspective. This requirements list is the product backlog. These requirements are gradually set over a period of 2
weeks, known as a sprint. The end of a Scrum sprint is the delivery of the finished work (incremental product). The incremental product needs to be in a state as delivered by the customer (deliverable product). Following the cycle, the products, requirements, and processes are further tested and developed in the next sprint. Scrum is designed for teams of 3 to 9 people. Major development projects or large development departments require a greater framework to organize the coordination of several teams. If these synergies follow the same principles as Scrum, this is referred to as a major agile framework.