Use scrum events to deliver work in time-boxed increments

By the end of this lesson, you’ll be able to: - Define a sprint as a fixed time-box delivering one or more “measurable” product increments - Explain that the scrum team defines the definition of done if no organizational standard exists - Explain that no changes during the sprint should risk the sprint goal - State that only the product owner can cancel a sprint - Identify that the scrum team refines the product backlog as needed

By the end of this lesson, you’ll be able to: - Define the sprint backlog as the set of selected product backlog items and a plan for delivering them to achieve the sprint goal - Recognize that sprint planning is time-boxed to a maximum of eight hours for a one-month sprint - Explain that sprint planning covers three topics: sprint value, work selection, and execution plan - Identify the sprint backlog as one of the three scrum artifacts - Emphasize that the sprint backlog should prioritize opportunities for continuous improvement

By the end of this lesson, you’ll be able to: - Define the daily scrum as a meeting for developers to inspect progress, address impediments, and adjust plans - Explain that the daily scrum enhances focus, communication, and quick decision-making - Emphasize that the outcome should improve workflow and process efficiency - Recognize that the daily scrum is time-boxed to 15 minutes per day

By the end of this lesson, you’ll be able to: - Define the sprint review as an opportunity to inspect the sprint outcome and plan future adaptations - Emphasize that the sprint review is a working session, not just a presentation - Recognize that the sprint review is time-boxed to a maximum of four hours (or less) for a one-month sprint (usually shorter in shorter sprints) - State that the goal is to showcase a working increment, gather feedback, and update the product backlog - Explain that only work meeting the definition of done is included in the session

By the end of this lesson, you’ll be able to: - Recognize that the sprint retrospective is time-boxed and typically relative to sprint length - Emphasize the importance of identifying and agreeing on a measurable process improvement (kaizen) for a future sprint - Describe how the scrum team reflects on successes, challenges, and problem-solving during the retrospective to ensure continuous improvement