Course Hive
Search

Welcome

Sign in or create your account

Continue with Google
or
Chapter 4: Scrum Events: Purpose and Time-box for Each Event. Understanding the Key Scrum Ceremonies
Play lesson

CSM - Certified Scrum Master Playlist - Chapter 4: Scrum Events: Purpose and Time-box for Each Event. Understanding the Key Scrum Ceremonies

4.0 (3)
20 learners

What you'll learn

This course includes

  • 57 min of video
  • Certificate of completion
  • Access on mobile and TV

Summary

Keywords

Full Transcript

@lightuptechnologies @CambridgeUPELT @PW-Foundation @KhanSirPatnaKhanGs @Pearson @Oxfordonlineenglish1 @ALLENCareerInstituteofficial @NIIT_Limited @byjusclasses @SimplilearnOfficial @greatlearning @MyLearningMyExperience @questpondvideos @Scrumdiddlyumptious @dr.preetityagilectures874 @pmi Welcome to our deep dive into Scrum Events! In this video, we’ll explore the key events (also known as ceremonies) that structure the Scrum framework and help teams deliver valuable increments in a time-boxed manner. These events are designed to promote transparency, inspection, and adaptation, which are crucial for successful Agile projects. Whether you're preparing for your Certified Scrum Master (CSM) exam, managing a team, or just getting started with Scrum, this guide will help you understand the purpose and time-box for each Scrum event. In this video, you will learn about: The Sprint: The Heart of Scrum Sprint Planning: Why, What, and How Daily Scrum: The 15-Minute Sync Sprint Review: Inspecting the Increment Sprint Retrospective: Planning for Improvement By the end of this video, you’ll have a clear understanding of how each event contributes to Scrum's overall effectiveness and how to use them to improve team collaboration, focus, and delivery. This short iteration cycle helps teams stay focused, maintain high quality, and deliver results quickly. Goal-Oriented: At the start of each Sprint, the team defines a Sprint Goal, which provides a focus for the work that will be completed during the Sprint. The goal should be clear, concise, and achievable. Cross-Functional Collaboration: During the Sprint, the Product Owner, Scrum Master, and Developers collaborate closely to work on items from the Product Backlog, ensuring the highest-priority work is done. Incremental Delivery: By the end of each Sprint, the team should have a potentially shippable product increment that is reviewed, tested, and potentially deployed. The Sprint provides a structure for regular, predictable delivery, helping teams maintain consistent momentum and achieve progress toward the larger product vision. Sprint Planning: Why, What, and How Sprint Planning is the first event in the Sprint and plays a critical role in setting the direction and focus for the entire iteration. It’s where the Scrum Team aligns on the work to be done and defines a clear path forward. Why Sprint Planning Is Important: Sprint Planning ensures that the Scrum Team is aligned on the Sprint Goal and the work to be done. This event is crucial for: Establishing clarity on the Product Backlog items selected for the Sprint. Ensuring that the team understands the scope and objectives of the Sprint. Aligning the team’s efforts toward a shared Sprint Goal. Without a structured Sprint Planning session, the team may lack focus, which can lead to misalignment and missed opportunities for value delivery. The Three Key Questions in Sprint Planning: Why is this Sprint valuable? The team establishes the Sprint Goal to clarify why this Sprint is important and what the outcome will be. This helps the team stay focused on delivering business value and ensures that the Product Owner’s vision is understood. What can be Done this Sprint? The Scrum Team reviews the Product Backlog and selects the highest-priority items that will be worked on during the Sprint. These items become the Sprint Backlog, and the team estimates the effort needed to complete them. How will the work be done? The team discusses the approach for completing the selected work and may break tasks into smaller, more manageable units. The Development Team collaborates to decide on the best way to accomplish the work, including creating a detailed plan for execution. Time-box for Sprint Planning: The time-box for Sprint Planning is 8 hours for a one-month Sprint. For shorter Sprints, the time-box is typically shorter (e.g., 4 hours for a two-week Sprint). The event should be structured and focused to ensure the team walks away with clear commitments for the Sprint. Daily Scrum: The 15-Minute Sync The Daily Scrum is a quick, 15-minute meeting held at the same time and place every day during the Sprint. This meeting provides an opportunity for the Development Team to synchronize, discuss progress, and address any impediments they may be facing. Purpose of the Daily Scrum: Progress Check: The Daily Scrum allows the team to inspect its progress toward the Sprint Goal and adjust the plan as needed. Identify Issues: It provides a space to identify any blockers or obstacles that might prevent the team from completing the work. Coordination: Team members can share important updates and align on what needs to be done next. #scrum #agile #csm #psm #scrummaster #certifiedscrummaster #sprintreview #sprintplanning #scrumteam #productowner #productmanagement #productmanager #productbacklog #sprintreview #scrumexamprep #job #ceremony #scrumtraining #pearson #pmi #safe #prince2 #tcs #ibm

Course Hive

Continue this lesson in the app

Install CourseHive on Android or iOS to keep learning while you move.

Related Courses

FAQs

Course Hive
Download CourseHive
Keep learning anywhere