Why Should There Be A Scrum event?
The Scrum events or ceremonies are activities or meetings carried out during a sprint which ranges from sprint, sprint planning, daily standup, sprint review and retrospective
The Sprint
Sprints are referred to as the heartbeat of Scrum. It is usually a one month or less fixed event of one to create consistency. Immediately a sprint ends, another Sprint starts.
Sprints enable predictability by ensuring inspection and adaptation of progress toward a Product Goal at least every month due to its iteration.When a Sprint’s horizon is too long the Sprint Goal may become invalid, complexity may rise, and risk may increase. Shorter Sprints can be employed.
Sprint could be canceled if the Sprint Goal becomes obsolete.it is important to note that a sprint can only be canceled by the Product Owner.
Sprint Planning
Sprint Planning initiates the Sprint by laying out the work to be performed for the Sprint. This resulting plan is created by the collaborative work of the entire Scrum Team.
The Product Owner ensures that attendees are prepared to discuss the most important Product Backlog items and how they map to the Product Goal. The Scrum Team may also invite other people to attend stakeholders)
During the sprint the following are flows of discussion
I. The essence of the sprint and its value
Ii The whole Scrum Team then collaborates to define a Sprint Goal that communicates why the Sprint is
valuable to stakeholders.
iii The Sprint Goal must be finalized prior to the end of Sprint Planning.
Iv Also what can be achieved or done during the course of the sprint is also discussed at the sprint planning. Through discussion with the Product Owner, the Developers select items from the Product Backlog to include in the current Sprint.(Sprint Backlog) . Selecting how much can be completed within a Sprint may be challenging. However, the more the Developers know about their past performance, their upcoming capacity, and their Definition of Done,the more confident they will be in their Sprint forecasts.
v How the work will be done is also a discussion during the sprint planning. It is important to note that no one can choose how the task will be turned into deliverables for the developers. The developers decide how they want to carry out the task and turn it into deliverable value
The sprint backlog is usually drawn at the sprint planning meeting. Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.
Daily Scrum
Daily standup is usually a 15 minute time boxed meeting for team to coordinate and create a plan for the next day
Three Main Questions?
a. What did I accomplish yesterday?
b. What am I going to accomplish today?
c. What is blocking me?
The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal. To reduce complexity, it is
held at the same time and place every working day of the Sprint.
Daily Scrums improve communications, identify impediments, promote quick decision-making, and
consequently eliminate the need for other meetings.
The Daily Scrum is not the only time Developers are allowed to adjust their plan. They often meet throughout the day for more detailed discussions about adapting or re-planning the rest of the Sprint’s Work.
Sprint Review
A. The Sprint Review is the second to last event of the Sprint and is timeboxed to a maximum of four hours for a one-month Sprint.
B. The essence of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations. The Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed.
During the event, the Scrum Team and stakeholders review what was accomplished in the Sprint. The Sprint Review is a working session and the Scrum Team should avoid limiting it to a presentation.
Sprint Retrospective
A The Sprint Retrospective concludes the Sprint. It is timeboxed to a maximum of three hours for a one month Sprint. The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness.
B. The Scrum Team discuss how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. Assumptions that led them astray are identified and their origins explored.
C. The Scrum Team discusses what went well during the Sprint, what problems it encountered, and how those problems were (or were not) solved.
D. The Scrum Team identifies the most helpful changes to improve its effectiveness. The most impactful improvements are addressed as soon as possible. They may even be added to the Sprint Backlog for the next Sprint.
For shorter Sprints, the event is usually shorter.
When you take all these into considerations,Your work flow will be considered Smooth and Easy.
