Is Sprint a Formal Opportunity to Inspect and Adapt or Not?
The Scrum guide says "Scrum combines four formal events for inspection and adaptation within a containing event, the Sprint"
As per Scrum there are 5 events The Sprint, Sprint Planning, Daily Scrum, Sprint Review and Sprint Retrospective
The Scrum Guide also says "The Sprint is a container for all other events. Each event in Scrum is a formal opportunity to inspect and adapt Scrum artifacts"
So I am confused if Sprint is a formal opportunity to inspect and adapt or not? If not why?
Thanks
Hi Mohanraj, as Ken Schwaber describes it, the Sprint is not a formal event as in a single meeting, it is an event that includes all other events, hence it is not considered formal in that term and therefore not considered one of the 4 formal events.
The Developers do; however, inspect and adapt during the sprint whilst working on PBIs as more is learned about them.
The Scrum guide says "Scrum combines four formal events for inspection and adaptation within a containing event, the Sprint"
As per Scrum there are 5 events The Sprint, Sprint Planning, Daily Scrum, Sprint Review and Sprint Retrospective
The Scrum Guide also says "The Sprint is a container for all other events. Each event in Scrum is a formal opportunity to inspect and adapt Scrum artifacts"
So I am confused if Sprint is a formal opportunity to inspect and adapt or not? If not why?
Perhaps it can be seen as a matter of propagation, in that the inspect-and-adapt formality of the contained events is transmitted to the container. In other words the Sprint is a formal opportunity to inspect and adapt because of what it contains, and not because of what it is.
Arguably, the properties of containment may also include transitivity (a Sprint and its formal events may be contained within other Sprints) and possibly antisymmetricity (none of the 4 formal events may contain the Sprint).
Thanks Eric, Scott & Ian for clarifying.
So the take away is the inspection and adaptation happens within the Sprint but it is not formal as it is just an containing event.
Hello,
Let's first think about what we were doing in a traditional environment. We were making a long-duration plan and making Risk Register, Lesson Learn Documentation etc. throughout the project. So, there was a very long period for feedback or for inspection and adaptation. So, to overcome those problems we are working in an agile environment.
So, In Scrum, Sprint is a short, iterative, timebox cycle in which the team is doing commitment and delivering incremental value at the end of the sprint. and to achieve this we are doing some events like Sprint Planning Daily Scrum, Sprint Retrospective, Sprint Review.
And all those meetings are providing an inspection and adaption opportunity to the team.