3. Scrum Events for “Heart of Harmony” (with Exact Timeboxes from the Guide)
All Scrum Events are timeboxed (having a maximum duration) and serve as formal opportunities to inspect and adapt Scrum artifacts. Failure to operate any events as prescribed results in lost opportunities.
The Sprint:
- Timebox: One month or less. For the “Heart of Harmony” digital platform, we will use a one-month Sprint length.
- Key Aspect: It is a fixed-length event that serves as a container for all other Scrum events. A new Sprint starts immediately after the conclusion of the previous Sprint.
- During the Sprint:
- No changes are made that would endanger the Sprint Goal.
- Quality does not decrease.
- The Product Backlog is refined as needed.
- Scope may be clarified and renegotiated with the Product Owner as more is learned.
- Cancellation: A Sprint can only be cancelled if the Sprint Goal becomes obsolete. Only the Product Owner has the authority to cancel the Sprint.
Example: Every one month, the “Heart of Harmony” digital team delivers a new, usable piece of the community portal. If, during the Sprint, a major shift in community needs makes the current Sprint Goal irrelevant, the Product Owner might cancel the Sprint.
Sprint Planning:
- Timebox: A maximum of eight hours for a one-month Sprint.
- Purpose: To lay out the work to be performed for the Sprint. This plan is created by the collaborative work of the entire Scrum Team.
- Topics Addressed:
- Why is this Sprint valuable? (Define Sprint Goal collaboratively).
- What can be Done this Sprint? (Developers select Product Backlog items).
- How will the chosen work get done? (Developers plan the work; their sole discretion).
- Output: The Sprint Backlog (comprising the Sprint Goal, selected Product Backlog items, and the plan for delivering them).
Example: The “Heart of Harmony” Scrum Team collaborates for up to eight hours to define the Sprint Goal (e.g., “Enable basic event sign-ups for the community portal”). The Developers then select items and plan the detailed tasks for achieving this goal.
Daily Scrum:
- Timebox: A 15-minute event. Its duration is fixed and does not scale with Sprint length.
- Purpose: To inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary.
- Attendees: For the Developers of the Scrum Team. (Product Owner or Scrum Master participate as Developers if actively working on Sprint Backlog items).
Example: The Developers meet for exactly 15 minutes every working day to synchronize, discuss progress towards “basic event sign-ups,” and adjust their plan for the next 24 hours. The Scrum Master ensures the event takes place and is productive.
Sprint Review:
- Timebox: A maximum of four hours for a one-month Sprint.
- Purpose: To inspect the outcome of the Sprint and determine future adaptations.
- Attendees: The Scrum Team and key stakeholders.
- Format: A working session where the Scrum Team presents the results, and attendees collaborate on what to do next. The Product Backlog may be adjusted.
Example: The “Heart of Harmony” Scrum Team presents the working “event sign-up” feature to community members and stakeholders for up to four hours. They gather feedback, discuss changing community needs, and collaboratively refine the Product Backlog.
Sprint Retrospective:
- Timebox: A maximum of three hours for a one-month Sprint.
- Purpose: To plan ways to increase quality and effectiveness.
- Attendees: The Scrum Team inspects how the last Sprint went regarding individuals, interactions, processes, tools, and their Definition of Done.
- Output: Identifies the most helpful changes to improve effectiveness, which may be added to the Sprint Backlog for the next Sprint.
Example: The “Heart of Harmony” Scrum Team spends up to three hours inspecting their collaboration, identifying impediments (e.g., slow feedback loop), and deciding on improvements (e.g., “Implement a new feedback tool”) for the next Sprint.
