Events and Artifacts of Scrum

Leadership institute
#1

Events and Artifacts of Scrum

In the following, not only the most important events and artifacts of Scrum are explained, but also how they are connected to each other.


The Product Owner has a certain product vision. Because the product can be very complex, it is broken down by so-called backlog grooming into smaller features (elements) that are listed in a priority list, the product backlog.


  1. A sprint begins with sprint planning, includes development work (sprint execution) during the sprint, and ends with review and retrospective. The number of points in the product backlog is usually higher than a development team could handle in a short sprint phase. Therefore, the development team must initially determine a number of points in the product backlog that it believes it can complete (Sprint Planning). The goal is to have a potentially deliverable product increment at the end of the sprint.
2 Likes
#2

In 2011 a change in The Scrum Guide(Schwaber and Sutherland 2011) has triggered a debate about whether the appropriate term to describe the outcome of Sprint Planning should be forecast .Proponents of the term forecast prefer this term because even the best estimate can change during a sprint due to new information.

There is also the opinion that a commitment on the part of the team leads to the quality of the work suffering because an attempt is made to meet the set goal in any case, or because the team may tend to set goals that are too low for it to achieve in any case.