Scrum is an extremely popular IT project management methodology based on agile methodologies, taking an iterative, incremental approach to teamwork. It relies on the organization of work into small cycles or sprints, which allow the implementation of the various stages of the project, in an efficient and rapid manner by a motivated team. Its great advantage is the great transparency of the project and the ability to see every single task assigned to a specific team by each employee. What's more, this work methodology assumes that each sprint provides a set of working parts of the project or its functionalities, which can be improved and tested in subsequent sprints.
Scrum assumes the presence of a Scrum Owner, who plans the various stages of the project step by step, a Scrum Master is responsible for following the rules of working in this methodology and motivating the team, as well as the team divided into sub-teams made up of specialists from different fields.
Scrum - the philosophy of a working sprint
Scrum methodology is extremely fast and efficient due to the precise planning of each stage of work on the project. Thanks to it, each team member knows exactly what to do, what phase the project is in, and all work strives to have a working product at all times.
Product Backlog - a record of the product
This is a project broken down into stages, from the most important to the least important, assuming that each of them is possible and the team has the competence to implement it. Its creation is handled by the Product Owner, who then consults with the team.
Each stage of work on a project begins with the entire team discussing a list of assumptions and tasks called Sprint Backlog, assigning responsibilities to each member, and outlining the timeframe needed to make a specific part of the product work properly.
This is the time needed to complete one phase of work on a project. It depends largely on the complexity of the project.
Daily Scrum Meeting
These are daily meetings for discussing all the important issues concerning a single sprint. It is at this meeting that the Scrum Master motivates the team in order to prevent a drop in work efficiency.
Sprint Review Meeting - completion of a sprint
Refers to the review of the completed sprint, through which each member of the team, as well as the customer, can give feedback on whether the project needs improvement and whether the overall work on the product is progressing in the right direction.
Refers to checking and evaluating the sprint increment.
This is the phase in which all the work on a sprint is most often analyzed in order to learn lessons for the future so as to improve and enhance the work on future sprints.