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 events, such that every event has a maximum duration. Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened. The remaining events may end whenever the purpose of the event is achieved, ensuring an appropriate amount of time is spent without allowing waste in the process. Other than the Sprint itself, which is a container for all other events, each event in Scrum is a formal opportunity to inspect and adapt something. These events are specifically designed to enable critical transparency and inspection. Failure to include any of these events results in reduced transparency and is a lost opportunity to inspect and adapt.
Levels of Planning
- Scrum teams plan at multiple levels (strategic, release, sprint daily etc) creating appropriate detail using rolling wave planning and progressive elaboration to support the necessary level of understanding.
- In a Scrum, the team and customer engagement together in planning activities to create practical plans that balance priorities and team capabilities in order to gain increased levels of commitment.
- Planning in Scrum happens at different levels represented by Planning Onion.
The planning could be at different levels
- Daily (every day)
- Sprint (Weekly)
- Release (Month)
- Roadmap (2 years)
- Vision (Long Term)
The Team is involved at Daily, Sprint and Release Level. The daily planning happens through the daily standup meeting. Sprint plans consider the tasks that are needed to transform a feature request into working, tested software. Sprint plan happens at the beginning of every Sprint. Release planning is driven by the need to convey a plan to the customer of the product about what they can expect over the next few months. More long term panning is driven by the Product Owner to look beyond the immediate release. This is to come up with a product roadmap typically extending up-to 2 years. Beyond the roadmap, there is planning at the portfolio or strategic levels wherein the organization determines where the product is placed within the portfolio or organization and what strategic needs it addresses within the portfolio. Typically Product Vision is defined at this level.
Velocity is a useful planning metric for estimating how fast work can be completed and how long it will take to complete a project. The metric is calculated by reviewing work the team successfully completed during the previous sprint.
Release Planning Sessions are conducted to develop a Release Plan. The plan defines when various sets of usable functionality or products will be delivered to the customer.
Sprint planning meeting
At the beginning of the sprint cycle (every 7–30 days), a “Sprint planning meeting” is held.
- Select what work is to be done
- Prepare the Sprint Backlog that details the time it will take to do that work, with the entire team
- Identify and communicate how much of the work is likely to be done during the current sprint
Each day during the sprint, a project team communication meeting occurs.
This is called a Daily Scrum (meeting) and has specific guidelines:
- All members of the development team come prepared with the updates for the meeting.
- The meeting starts precisely on time even if some development team members are missing.
- The meeting should happen at the same location and same time every day.
- The meeting length is set Time-boxed to 15 minutes.
- All are welcome, but normally only the core roles speak.
At the end of a sprint cycle, two meetings are held: the “Sprint Review Meeting” and the “Sprint Retrospective”.
- The objective of this meeting is
- To review the work that was completed
- The planned work that was not completed
- If the team is on track
- Get Feedback
A Retrospective is a special meeting that takes place after each sprint, in which the team members gather to inspect and improve their methods and teamwork.