Suggest an editImprove this articleRefine the answer for “What events does Scrum include?”. Your changes go to moderation before they’re published.Approval requiredContentWhat you’re changing🇺🇸EN🇺🇦UAPreviewTitle (EN)Short answer (EN)**Scrum** includes five key events (ceremonies) that structure the team's work and set the rhythm of development. **Key point:** each event has a clear purpose, participants, and an expected outcome, and together they help the team plan, synchronize, get feedback, and continuously improve the process.Shown above the full answer for quick recall.Answer (EN)ImageScrum includes **five key events (ceremonies)** that structure the team's work and set the rhythm of development. They help the team plan, synchronize, get feedback, and continuously improve the process. Each event has a clear purpose, participants, and an expected outcome. ### 1. Sprint This is the **main cycle in Scrum**, in which a working product increment is created. It usually lasts **1-4 weeks**, and at the end of the sprint the team must show a result ready for use. **Goal:** deliver value to the user within a short period of time. **Fixed:** the sprint goal, the duration, and the set of tasks. During the sprint, changes to the goal are not allowed - the team stays focused on achieving the result. **Result:** a finished, tested part of the product. ### 2. Sprint Planning Held at the start of each sprint. The team, together with the Product Owner, determines **what** will be done and **how** it will be implemented. **Main planning questions:** - What from the backlog can we deliver in this sprint? - What is the Sprint Goal? - How exactly will we carry out the tasks? **Result:** - a formed **sprint backlog** (list of tasks for the sprint); - a clearly defined goal the team is aiming for. ### 3. Daily Scrum A short meeting (up to 15 minutes), held every day at the same time. Needed to synchronize the team and surface obstacles. Each participant answers three questions: 1. What did I do yesterday? 2. What am I going to do today? 3. What is blocking further progress? **Result:** the team understands the current status of the work and can adjust the plan to reach the sprint goal. ### 4. Sprint Review Held at the end of the sprint. The team demonstrates the **finished increment** of the product to the client and stakeholders. **Goal:** get feedback and discuss what worked and what is worth improving. The Product Owner updates the **Product Backlog**, taking into account new ideas, priorities, and feedback. **Result:** confirmation of the value of the work done and understanding of where to go next. ### 5. Sprint Retrospective The final event of the sprint, held after the review. The team discusses **how the sprint went** and **what can be improved** in the next one. **Typical questions:** - What worked well? - What got in the way? - What needs to change to become more effective? **Result:** a concrete plan of improvements for the next cycle. ### Summary | Event | Goal | Result | |---|---|---| | **Sprint** | Create an increment | A finished part of the product | | **Sprint Planning** | Define the sprint goal and tasks | Sprint backlog and sprint goal | | **Daily Scrum** | Synchronize the team | An up-to-date plan for the day | | **Sprint Review** | Demonstrate the result and gather feedback | Updated backlog | | **Sprint Retrospective** | Improve the process | A plan of changes to the work | **Scrum events** create a steady rhythm: the team plans, does, shows, analyzes, and improves. This is a closed loop of continuous growth, where every sprint is a step toward a better product and a more mature process.For the reviewerNote to the moderator (optional)Visible only to the moderator. Helps review go faster.