Scrum Events


A Sprint is exactly what all is conceived for. It is during the sprint that the finished product is created. Or the product that the customer wants to see, because the development cycle can be endless. We can say that the word sprint in Scrum-campaign describes, in fact, the workflow itself. Once all the planning steps have been taken, and the teams have sorted out their tasks, it's time for the sprint.

Typically, a sprint is planned for a month, but most companies using the Scrum methodology agree that the organization of such a long process is costly and tedious, so the sprint often lasts about two weeks. Sometimes two sprints break down the process of improving or updating the same software product.


A mandatory element of the sprint in Scrum is the meetings of the team and the customer. In itself, these meetings can be divided into two types: planning activities and closing events. The planning meeting in the life cycle of one sprint usually occurs twice.

The first Meeting

The first of them gather all who are somehow interested in the product. These are developers, customers, managers, and stakeholders. Under the guidance of a Scrum Master, we discuss what product should be the result, what can be implemented within a single sprint, and what can not be done. As a result of these discussions, Sprint Backlog is compiled - a kind of To-Do-List for the current workflow. It includes all the tasks that need to be performed to achieve the ultimate goal of the sprint.

The second meeting

The second meeting is internal. Under the leadership of the Scrum Master, the development team discusses the intricacies of development and splits tasks into groups, and sets priorities that will be followed throughout the sprint. It may turn out that not all the tasks are on time, then you need another meeting of customers to reallocate priorities. But all decisions on the direct development are made only by the team itself-the essence of Scrum is that no one has the right to influence this process unless any other choices have been made on this issue.

Final and bonus

After the sprint, the final meeting is held - the so-called sprint review, which demonstrates the success of the team.

Throughout the sprint, there are daily meetings that allow development teams to stay connected to each other and stay in the overall workflow, which is very important. In Scrum-campaign, tasks are very often distributed like puzzle pieces, and you won’t be able to join them in the final if the internal connections are broken.