Get Scrum - The Scrum Process Explained

Key Takeaways

in this session we will consider the 11 elements that make up the process of scrum as described in the scrum framework first let's identify the roles in a scrum team the scrum master the scrum master is the coach for the team and the organization in implementing scrum so that all the benefits of scrum may be gained through the effective implementation the scrum master is a management role that manages the effective implementation understanding of the scrum framework within the organization they also need to be considered a senior enough organizational role so they are confident to discuss impediments at any level within the organization the product owner the product owner should own the product in an entrepreneurial manner providing the vision to the scrum team of the value that the product should deliver through this vision the product owner maximizes the value of the work delivered by the development team through actively owning the product backlog as a living artifact and maximize the amount of work not done therefore you can consider the product owner as the value optimizer the development team at this point the development team is the accurate name for those who deliver the value of the product however at this moment Ken and Jeff are both reviewing and updating the scrum guide and unfortunately the development team appears if it will not be renamed as theirs may change in the future we will update this video but at the moment the development team is an accurate term for those who carry out the work in a scrum team now let's consider the three artifacts in scrum the product backlog the product backlog is a living artifact describing the vision of the product through the product owner adding items to the backlog that will deliver the value expected from the product and the development team refining the backlog item said it can be technically delivered in a sprint where items can be removed as no longer needed not likely to deliver the expected value or that this value can be delivered in the other manner then the product owner should do so in order to maximize the value of the work not done the Sprint backlog the Sprint backlog forms the plan of items that development team expects to deliver throughout the Sprint this may be broken down and described as tasks the intent complete in order to deliver each product backlog item or as tests that described the work that must be completed so each backlog item can be considered done the done increment the done increment is the accumulated increments of all the Sprint's completed so far in order to deliver the product if you're at the end of sprint 1 then the done increment will be the output from only that sprint however if you're at spend 11 then the done increment is the accumulated work for all preceding sprints as well as the output from their nearly completed spread 11 which comprises the potentially shippable product every time the product owner releases the done increment to their customers this provides a feedback loop to the vision and they refer to the product backlog based on the customers reactions to the release know let's identify the events in scrum that connect the rolls to the artifacts and build the feedback books spent planning the first event that occurs within the Sprint is sprint planning this allows their team to plan the work that were taken from the product backlog and deliver the value that will be considered output at the end of the Sprint first in sprint planning they identified a sprint goal in business terms this sets the value heading for the outcome that the Sprint will actually deliver then the development team will select the product backlog items that they believe will allow them to deliver that sprinkle after that they will break those items down into either the task or test that will allow them to deliver that sprint backlog the daily scrum the event of which the development team participates to synchronize the work of the last 24 hours and the next 24 hours is called the daily scrum this gives the development team an opportunity to inspect the work of the last 24 hours and adapt their plan for the next upcoming 24 hours the sprint review the sprint review is the event of a spread where the scrum team and its stakeholders can participate in the inspection of the work that's been produced to meet the goal of this brand and how this progresses development of the overall solution the outcome from Sprint review provides a feedback loop to both the product backlog and the choices made during sprint planning one thing you could be assured to have as an outcome is an updated product backlog even it is agreed that the current order is correct the retrospective the retrospective is the opportunity at the end of the sprint in which the scrum team can inspect its implementation of scrum as a process framework the interactions of the people within the team as well as any required skills in order to deliver the solution while reviewing these to consider opportunities for continuous improvement this provides a continuous improvement feedback loop for this Grum team which you take at least one continuous improvement goal into each sprint as a target to achieve the Sprint the last event that we would consider is a special event called the container event this is the actual sprint itself is termed as being a container event because all the activities of scrum occur within a sprint in this Grum framework there are no activities events or other actions that are carried on outside of the actual sprint therefore the length of the sprint should be such that allows you to carat all the work to deliver done and a complete increment of the product within this time box you