hi in this video we will have a deep dive into the scrum events as explained in a previous video scrim is a set of ceremonies roles and artifacts the main event in scrum is the sprints sprint is at the heart of scram it's a time-boxed iteration and its duration vary from one to four weeks maximum within a sprint the team sets their target with the product owner as a sprint goal and plan their work in the sprint backlog as soon as the sprint starts the team work together to complete the planned work effectively and make
it ready for review by the end of that period the duration of a sprint is defined by the scrum team once the team reaches an agreement for how many days a sprint should last all future sprints should be the same a sprint can be cancelled before the sprint time box is over only the product owner has the authority to cancel this print and of course the product owner can decide to cancel the sprint based on recommendation from stakeholders development team or the scrum master a sprint would be cancelled if the sprint gold becomes obsolete this
might happen if the company changes direction or if market or technology conditions change in general a sprint should be cancelled if it no longer makes sense given the circumstances but due to the short duration of a sprint cancellation rarely makes sense sprints consist of different other events the sprint planning daily scrums the sprint review and the sprinter perspective sprint planning is the first event instagram that kicks off the sprints the purpose of this ceremony is to define what can be delivered in the sprint and how the work needed to realize the sprint goal will be
done a great starting point for the sprint planning is the product backlog as it provides a list of ready user stories that could potentially be part of the sprint the team should also look at the previous work done in the increment to have a view on their capacity the sprint planning is split in two parts the first part is related to the what based on the product's backlog the product owner describes the goal of the sprint what backlog items contribute to that goal and clarifies any final details and based on the capacity the development team
decides what can be done in the coming sprint and pick use of stories from the product backlog in the second part the development team decides how the work will be done what they will do during the sprint to deliver the sprint goal break up the work in smaller pieces and perform some high level design you cannot do the sprint planning without the product owner or the development team the product owner defines the goal based on the business value he wants to achieve the development team needs to understand how they can or they cannot deliver on
that goal if item is missing from this event it makes planning dispense almost impossible the scrum master can help in the facilitation of the sprint planning the most important outcome for the sprint planning meeting is that the team can describe the goal of the sprints and how they will start working toward that goal this is made visible in the sprint backlog the duration of a sprint planning should be no more than two hours for each week of the sprints so for example the sprint planning meeting for a two week sprint would be no longer than
four hours once the scrum team has defined their sprint goal and their sprint backlog the sprint can start the team will meet every day in the daily scrum the purpose of the daily scram is for the development team to synchronize its activities inspect progress towards the sprint goal and create a plan for the next 24 hours the daily scrum is a 15 minutes time box event held every day of the sprint at the same time and same place in the daily scrum only the development team is mandatory the product owner is welcome to join as
an observer and the scrum master as a facilitator to ensure that the development team has the meeting but the development team is responsible for conducting the daily scrum and it is mainly for them to answer these three questions what did i do yesterday that helped the development team miss the sprint goal what will i do today to help the development team meet the sprint goal do i see any impediments that prevents me or the development team from meeting the sprint goal if some of the team member needs to have extended discussion then they can meet
immediately after the daily scrum [Music] the daily scrum help to improve the communication and eliminate other meetings it's the best opportunity for team to share their impediments to highlight and promote quick decision making this is a key inspect and adapt meeting this print review is held at the end of the sprint it is designed to gather actionable feedback on what the team has completed the scrum team would invite the stakeholders to the sprint with you the increment is assessed against the sprint goal designed by the scrum team the team will showcase their work in product
to the stakeholders and then ask them for feedback on how to make the product better the product owner incorporates the lessons learned during the conversation into the product backlog this meeting is time boxed to no more than an hour per week of sprint so a two week sprint would have a two hours print review and the one week sprint a one hour's print review the sprint retrospective is the final event of the sprints this event is time boxed to three hours maximum for a four week sprint which means 45 minutes per sprint week the sprint
retrospective is an opportunity for the scrum team to inspect and adapt the process and identify opportunities for improvement the purpose of the sprinter retrospective is to inspect what went well in the last sprint with regards to people relationships process and tools identify what didn't go so well in the sprint and then create a plan for improvements to the way the scrum team does its work usually most of its perspectives follow these five steps one set the stage by defining a common goal for the retrospective and have everyone in the right mood two gather data as
everyone sees the word differently we need to create a shared pool of information three generate insights discuss why did things happen the way they did and identify patterns four decide what to do by choosing a few issues to work on and create concrete action plans five close the retrospective by clarifying how to follow up on these actions the last meeting we would like to discuss in this video is the backlog refinement the backlog refinement is not an official ceremony and scrum but rather an ongoing activity that the scrum team can hold during the sprints in
which the product owner and the development team collaborate on the details of products backlog items product backlog refinement is the act of clarifying items adding details splitting bigger items into smaller ones adding and discussing new items estimating or re-estimating items and ordering these items in the product backlog the scrum team decides how and when refinement is done refinement usually consumes no more than 10 of the capacity of the development team however product backlog items can be updated at any time by the product owner or by the team after discussing it with the product owner [Music]
the backlog refinement help to ensure that the product's backlog remains populated with items that are relevant detailed estimated and prioritized this is the main activity in the scrum cycle law of time will be saved in sprint planning meetings if the backlog is well maintained thank you for following this video i hope it gave you a good understanding of the scrum events please leave us a comment if there is any topic you would like us to discuss and subscribe to our channel for more content [Music] you
