4. Events

A Sprint is a set of 4 ordered events, spread out over time and with a fixed duration. As a general rule, a Sprint lasts between 2 and 4 weeks.

When the last event ends, another Sprint starts immediately, creating a continuous development cycle.

Sprint Planning

Sprint Planning is the meeting that kicks off the Sprint. It is the moment when the Scrum team collaborates to define what work will be done during the Sprint and how that work will be carried out. Here the Sprint goals, or the Sprint Goal, are established, and the Sprint Backlog is created, which is a list of tasks selected from the Product Backlog that the team commits to completing during the Sprint.

It should last a maximum of 8 hours for a one-month Sprint. For shorter Sprints, the duration is proportionally shorter.

Anyone interested in the project may take part, but only the Scrum Team (Product Owner, Scrum Master, and Development Team) has a voice and a vote in the decisions.

The Product Owner explains how value can be increased. They then present the items from the Product Backlog they consider a priority, and the Development Team selects those they believe they can complete during the Sprint. Together, they define the Sprint Goal and create the Sprint Backlog. Next, the Development Team plans how it will carry out the selected work, breaking it down into smaller tasks and assigning them among the team members.

Then the following is created:

• The Sprint Goal: a clear and concise objective that guides the team's work during the Sprint.
• The Sprint Backlog: a list of tasks selected from the Product Backlog
• A plan to deliver the product increment and achieve the Sprint Goal.

Daily Scrum

The Daily Scrum is a daily meeting where the Development Team synchronizes its activities and creates a plan for the next 24 hours. Generally, only the Development Team will be present, although the Scrum Master and the Product Owner may attend as listeners if they wish.

Its duration is 15 minutes at most, although it can be shorter, and it takes place at the same time and place every day to minimize complexity.

The goals are to:

• Improve communication among team members.
• Identify and remove obstacles that may be blocking progress.
• Promote quick and effective decisions.

And eliminate the need for other meetings.

Sprint Review

The Sprint Review is a meeting to show the product increment to the Stakeholders. It is considered that the Sprint Goal has been achieved and that it meets the Definition of Done. The objective is to obtain feedback and adapt the Product Backlog if necessary.

The Stakeholders are the people interested in the project, such as clients, end users, managers, or anyone else who has an interest in the product.

It should last a maximum of 4 hours for a one-month Sprint. The Scrum Team and the Stakeholders invited by the Product Owner must be present.

Sprint Retrospective

The Sprint Retrospective is the final meeting of the Sprint, where the Scrum Team reflects on the process and looks for ways to improve in the next Sprint. It is an opportunity for the team to evaluate what worked well, what did not work, and how they can improve their collaboration and efficiency.

• Evaluate the Sprint that has just concluded
• Review how collaboration among team members went
• Identify processes or practices that can be improved
• Discuss tools
• Adjust the Definition of Done if necessary

It lasts a maximum of 3 hours for a one-month Sprint.

And with this we conclude the Sprint and return to Sprint Planning to start a new cycle.

Now that we have seen all the events, let's explore the Scrum artifacts, or the elements we have mentioned throughout the course.