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 Planning :
- Sprint Planning is a time-boxed event of 8 hours or less to start a Sprint.
- Sprint Planning is a mandatory event of Scrum and is a feedback loop that team members can inspect the Product Backlog and select enough work to develop during the Sprint. It should be conducted at the beginning of each Sprint.
- The Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint. For shorter sprints, it is usually shorter.
Sprint Planning purpose :
- Sprint Planning serves to inspect the work from the Product Backlog that is most valuable to be done next, and to design this work into the Sprint Backlog.
- Outputs of Sprint Planning are the Sprint Goal and Sprint Backlog which itself contains selected Product Backlog Items and their related tasks.
Sprint Planning participants :
- The Scrum Team.
- The Sprint Goal is created through all Scrum Team members’ collaboration.
Sprint Planning practice :
- In the Sprint Planning, usually, enough tasks are defined for the early days of the Sprint, and other tasks emerge during the Sprint when the Development Team learns more about the work, new tasks are added during the Daily Scrum.
- Creating the Sprint Backlog is a collaborative work that is done by the Development Team members during the Sprint Planning not before or after it.
- During Sprint Planning, the Sprint Backlog should be groomed / defined enough so the development Team can create its best forecast of what it can do and start the first several days of the Sprint.
- Sprint Planning answers what two questions?
1. What can be delivered in the Increment for this Sprint?
2. How will required work be achieved?
- The three Sprint Planning meeting inputs are :
1. Product Backlog
2. Projected Development Capacity
3. Past Development Performance
More informations for the Scrum PSD certification here.