Integrity Score 95
No Records Found
No Records Found
No Records Found
Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.
Prescribed events are used in Scrum to create regularity and to minimize the need for meetings not defined in Scrum. All events are time-boxed. Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened.
- Sprint: All the work necessary to achieve the Product Goal, including Sprint Planning, Daily Scrums, Sprint Review and Sprint Retrospective happen within Sprints.
- Sprint Planning: As described in the Scrum Guide, 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 Sprint Planning to provide advice.
- Daily Scrum: The Daily Scrum is a 15-minute event for the developers of the Scrum Team. To reduce complexity, it is held at the same time and place every working day of the Sprint. If the product owner or Scrum Master are actively working on items in the Sprint Backlog, they participate as Developers.
- Sprint Review: During the event, the Scrum Team and stakeholders review what was accomplished in the Sprint and what has changed in their environment. Based on this information, attendees collaborate on what to do next. The Product Backlog may also be adjusted to meet new opportunities. The Sprint Review is a working session and the Scrum Team should avoid limiting it to a presentation.
- Sprint Retrospective: The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. Inspected elements often vary with the domain of work. Assumptions that led them astray are identified and their origins explored. The Scrum Team discusses what went well during the Sprint, what problems it encountered, and how those problems were (or were not) solved.