Hello Welcome back. We will discuss different prescribed events and activities in Scrum that processes these requirements. Product Backlog refinement is the act of adding detail estimates and order to items in the product backlog. It is an ongoing activity for its owner owns this meeting. Scrum Master helps him in organizing it. No time box is specified for this activity, but it should not block sprint activities.
Teams can spend a maximum of 10% of their time in backlog grooming activities. This activity can be used all the right user stories Find out more details etc. Break down user stories that's a too big improve user stories that's a poorly written estimate backlog items. Add acceptance criteria, if not already done, look deeper into the backlog to do longer range technical planning. Typical product backlog grooming or backlog refinement activity can have two parts. The first part we will concentrate on requirements clarification and adding more details to the product backlog.
In the second part development team will do an estimation for the user stories. During the sprint, the selected requirements that is backlog items will be converted to a working product information. Throughout this process, the product owner will be available for answering the questions and clarifying the requirements. Development team may renegotiate the requirements with the product owner to enhance the possibility of achieving the sprint goal. We can consider the sprint itself as the longest event in Scrum sprints contain and consists of sprint planning daily scrums, the development work, the sprint review and the Sprint Retrospective. Sprint is timebox to one month or less.
During the sprint development team creates a done usable and potentially releasable product increment. There is no gap between sprints. A new sprint starts immediately after the conclusion of the previous sprint. Sprint goal is finalized during sprint planning During the sprint, no changes are allowed that would endanger the sprint goal. Scope may be clarified and renegotiated between the product owner and development team as more as learned. A sprint can be cancelled before the sprint time box is over.
It is a decision from the product owner. Only the product owner has the authority to cancel the sprint. A sprint would be canceled or the sprint goal becomes obsolete. This will be a rare case as a sprint duration is shorter. Sprint Planning is a formal entry point for the record. The work to be performed in sprint is planned at the sprint planning.
This plan is created by the collaborative work of the entire scrum team. The Scrum Master ensures that the event takes place and the attendants understand its purpose. Sprint Planning is timebox to a maximum of eight hours or a one month sprint for shorter Sprint's the event is usually shorter. Sprint Planning is the first activity of the sprint. The inputs to sprint planning are the product backlog where we have the ordered estimated list of requirements, the latest product increment, we should be knowing what we have done so far. projected capacity for the development team during the sprint.
This assesses the availability of the team. We will consider leave plans holidays etc past performance of the development team the current speed, performance or in other words the velocity of the team. Sprint Planning answers the following questions What can be delivered in the increment resulting from an upcoming sprint? How will the work needed to deliver the increment be achieved? In simple words, Sprint Planning decides what can be delivered and how it can be delivered the what and how aspects of the sprint. In the first part of sprint planning the scrum team decide what can be done this sprint.
The usual process includes the product owner explains the objective that the sprint should achieve and discusses the product backlog items that they've completed in the sprint will achieve this objective. The development team decides and the number of items that can be selected from the project backlog for the sprint. Then the scrum team Crofts sprint bowl that gives guidance for the team during this sprint. It is an objective that will be met within the sprint through the implementation of the product backlog. In the second part of sprint planning, the development team decides how will the chosen work get done. Development team decides how it will build this functionality into a done product increment during this sprint.
The development team usually starts by designing the work needed to convert the product backlog into a working product increment. Work Plan for the first days of the sprint by the development team is decomposed by the end of this meeting, often two units of one day or less. The product owner can help this process by clarifying the selected product backlog. Items make trade offs if required development team can renegotiate the selected product backlog items with the product owner. As we have seen in the previous slides the sprint goal is an objective set for the sprint that can be met through the implementation of selected product backlog items. It provides guidance to the development team on why it is building the increment.
The Scrum guide stays. By the end of the sprint planning the development team should be able to explain the product owner and Scrum Master how it intends to work as a self organizing team to accomplish the sprint goal and create the anticipated increment. The Product Backlog items selected for this sprint plus the plan for delivering them is called the sprint backlog development team is responsible for creating and maintaining the sprint backlog. Plan usually takes form of engineering tasks and other work items for meeting the definition of done for the selected user story. These tasks are usually estimated in hours or days. development teams start to have known tasks at the time of sprint planning.
As development progresses, tasks may get added sprint backlog can grow in size. It is a live document development team keeps updating it throughout the sprint duration. As a good practice team makes sure that sprint backlog is updated before or during daily Scrum. At any point of time. The total estimated effort for unfinished tasks in sprint backlog gives the amount of identify work remains in the sprint As sprint progresses, new tasks may get added resulting in a temporary increase in remaining effort. During the daily Scrum, the development team inspects the progress of converting the selected requirements into tested shippable increments and make necessary adjustments.
The Daily Scrum is a 15 minutes time boxed event for the development team to synchronize activities and create a plan for the next 24 hours. Daily Scrum is conducted by development team and Scrum Master makes sure this event happens effectively. Usually it takes the format of three questions. Every team member answers three questions. What did I do yesterday that helps the development team meet the sprint go. What will I do today to help the development team meet this sprint go.
Do I see any impediment that prevents me or the development team from meeting the sprint goal? Remember, the development team can decide the format of this meeting. The intention, the expected value of the meeting is important. The three questions format is not mandatory, but it is successfully followed by many teams. There are many benefits of daily Scrum, including but not limited to. Improved communications, reduces the need for other meetings, identifies impediments to development for removal, highlight challenges and promote quick decision making improves the development teams level of knowledge.
And moreover, it is an inspect and adapt meeting during this session, Review the product increment is. a sprint review is held at the end of the sprint to inspect the increment and adapt the product backlog if needed. This meeting concentrates on the outcome from the sprint. They discuss what was done in the sprint and what are the next things that can be done to optimize value. This is an informal meeting. This is not a status meeting, the development team will present the increment to the participants.
The increment is presented to elicit feedback and foster collaboration. Attendees include the scrum team and key stakeholders invited by the product owner. This is For our time books and meeting for one month sprints for shorter Sprint's it will be shorter. In other words, it is time boxed to four hours. The product owner explains what product backlog items have been done and what has not been done. The development team demonstrates the work that has been done and answers questions about the increment.
The product owner discusses the product backlog as it stands and projects the likely completion dates. The entire group collaborates on what to do next. The results of the sprint review is a revised product backlog that defines the probable product backlog items for the next sprint. The Product Backlog may also be adjusted to meet new opportunities Sprint Retrospective An inspect and adapt event for the scrum team. Why is it relevant and requirements management items like definition of done and definition of ready are inspected and improved. As part of this event.
There will be concerns or areas of improvement to the requirement management process coming out of this meeting. Let's discuss this event. The Sprint Retrospective is an opportunity for the scrum team to inspect itself and create a plan for improvements to be enacted during the next sprint. The Sprint Retrospective occurs after the sprint review and prior to the next sprint planning. This is a three hour time boxed meeting for one month Sprint's this meeting inspects how the last sprint with regards to people relationships, process and tools and identify and order the major items that went well and potential improvements. Sprint Retrospective provides a formal opportunity to focus on inspection and adaptation.
There are different techniques used for conducting sprint retrospectives. A widely used method uses three categories to give a structure for the discussions. what went well, what didn't go well? What are the points to improve? Team discusses around these points and comes up with an action plan. instead of attacking all items, it recommends to concentrate on a few top items which can be tracked and achieved income in Sprint's