The Scrum Framework :
- The Scrum Framework consists of Scrum Teams and their associated events, artifacts, and roles as defined in the Scrum Guide.
- According to the Scrum Guide, mandatory rules and principles of Scrum are Scrum Roles, Scrum Events, Sprint Goal, Product Backlog, Sprint Backlog, Increment, Definition of Done, and Monitoring progress in Sprint and Project levels. Other things are practices that can be employed in the Scrum framework and are up to the team and project and are not mandatory.
The Scrum roles :
- Product Owner
- Development Team (Developers)
- Scrum Master
The Scrum artifacts :
- Artifacts represent work or value to provide transparency and opportunities for inspection and adaption.
- Artifacts are defined by Scrum and designed to maximize transparency of key information so that everybody has the same understanding.
- Product Backlog
- Sprint backlog
The Scrum events :
- Sprint Planning
- Daily Scrum
- Sprint Review
- Sprint Retrospective
- The Sprint is the container for all events
- According to the Scrum Guide, mandatory rules and principles of Scrum are Scrum Roles, Scrum Events, Sprint Goal, Product Backlog, Sprint Backlog, Increment, Definition of Done, and Monitoring progress in Sprint and Project levels. Other things are practices that could employ in the Scrum framework and are up to the team and project and are not mandatory.
- Events present an opportunity in the Sprint for something to be inspected or adopted.
- Events are designed to enable transparency and inspection
- There are totally 5 events in the Scrum framework as Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.
- Four Events of Inspection & Adaption
1. Sprint Planning
2. Daily Scrum
3. Sprint Review
4. Sprint Retrospective
- The Sprint is a container for other events.
- All four Scrum events are a type of feedback loop or inspect and adapt opportunities include Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. Although Sprint is an event its role is being a container for other events. Product Backlog refinement is a continuous activity and is not a feedback loop.
- Sprint is a time-boxed event of a month or less during which a “done,”usable, and potentially releasable Product Increment is created.
Sprint purpose :
- Although Sprint is an event its role is being a container for other events. Sprint is a time-boxed event of 30 days or less that serves as a container for the other Scrum events and activities.
- The purpose of each Sprint is to deliver increments of potentially releasable functionality that adheres to the Scrum Team’s current Definition of “done.”
Sprint participants :
- All members of the Scrum Team share in the accountability for creating value every Sprint.
Sprint practice :
- Sprints contain and consist of five parts, the other mandatory events :
1. Sprint Planning
2. Daily Scrum
3. Development Work
4. Sprint Review
5. Sprint Retrospective
- There is just regular Sprint in Scrum within which the Development Team tries to create releasable Increment. Therefore, there are no such things as Sprint Zero, Hardening Sprint, Stabilization Sprint, Integration Sprint, etc.
- Scrum does not acknowledge:
1) Hardening Phases.
2) Sprint 0.
There is no such thing as Sprint 0
3)Technical Sprints that consists only of tasks which help reduce the technical debt and do not add any functionality to the Product.
- A Sprint begins right after the previous Sprint ends & ends depending upon the length of the Sprint. The duration of a Sprint is fixed and cannot be shortened or lengthened. A new Sprint starts immediately after the conclusion of the previous Sprint. There is no gap or work done between Sprints.
Sprint lenght :
- Sprint is a time boxed event of 30 days or less.
- Sprint is the sole event that can not be finished or over earlier or later than its predefined time-box duration. Other events are time-box but can be finished earlier if the team achieves each event’s goal. On the other hand, it is possible the Team finishes all selected Sprint Backlog Items and tasks before the Sprint time-box, but the Team should continue the Sprint until the end of the related time-box through accepting new Items from the Product Backlog by negotiating with the Product Owner.
- Sprints are limited to one calendar month or shorter. The length of a Sprint thus could be weekly, biweekly or monthly. Sprint should be short enough to keep the risk acceptable to the Product Owner.
Sprint Impediments :
- What happens if the Development Team cannot complete its work by the end of the Sprint ? The Sprint ends on time and the team learns what is possible to accomplish in that sprint length.
- What happens if part of the work in a cancelled Sprint is potentially releasable ? The Product Owner typically accepts it.
- What happens when a Sprint is cancelled by the Product Owner ? Completed/”Done” PBIs are reviewed, incomplete PBIs are re-estimated and put back on the Product Backlog.
More informations for the Scrum PSD certification here.