Course Details

Previous Page

Software Practices (SCRUM): SCRUM Meetings

Target Audience
Expected Duration
Lesson Objectives
Course Number

A large part of the Scrum process revolves around the Scrum meetings. SCRUM meetings are highly structured and time efficient, and are part of the fantastic success of SCRUM methodologies. Another large piece of the Scrum process is managing user stories. User stories are short descriptions in non-technical language of how a system is expected to behave, and are one of the key and unique features of SCRUM development. This course covers the Scrum meeting and user stories in depth. It also covers key concepts, such as velocity and technical debt.

Target Audience
Software development managers looking to implement Scrum, or software developers looking to work on a Scrum team


Expected Duration (hours)

Lesson Objectives

Software Practices (SCRUM): SCRUM Meetings

  • start the course
  • describe the four Scrum meetings, when they occur, who attends, and the discussions that take place in each meeting
  • describe how the Sprint Goal and Sprint Backlog are created in the Sprint Planning meeting in Scrum software practices
  • describe how the Daily Standup meetings are structured with the Scrum Master and Scrum Team in Scrum software practices
  • describe how the Sprint Retrospective meeting assists the Scrum Master, Scrum Team, and Product Owner to adapt their practices and behaviors toward continual process improvement
  • describe how the Sprint Retrospective Meeting in Scrum can reveal insights into the last Sprint and identify areas that have room for improvement
  • describe how the Product Backlog Grooming Meeting in Scrum allows the team to review the top level user stories to determine whether they are ready to move into the next Sprint
  • describe how the Sprint Review Meeting allows Scrum members and stakeholders to inspect and adapt the product as it is being developed
  • describe how the Scrum of Scrums Meeting facilitates communication and collaboration between teams working on a large project
  • use the Definition of Done (DoD) checklist in Scrum to ensure that the best practices are followed during the development of high-quality software
  • describe the advantages of using smaller user stories when preparing for a Sprint in Scrum
  • describe how to write consumer user stories
  • size user stories in a product backlog using Scrum principles
  • describe how and why teams split user stories into tasks to track user stories' progress in a Sprint
  • describe how the Scrum Master can encourage self-organization within the Scrum Team
  • describe User Stories
  • split EPICs into a hierarchy of User Stories that can be completed in a single Sprint
  • describe the SCRUM Story Board
  • describe the lifecycle of a User Story
  • break down an EPIC into component User Stories
  • split User Stories into small slices using heuristics
  • split large User Stories into small slices using business data patterns
  • split User Stories by identifying the simple and complex patterns
  • use tasks to measure a team's progress and keep the entire team on track
  • use the SMART tasks to break down tasks into manageable portions of the User Story
  • use INVEST guidelines to develop high-quality User Stories
  • describe some of the ways technical debt accumulates and makes a product unstable
  • describe how to bring technical debt under control
  • describe the advantages associated with deferring detailed specifications in Scrum
  • use the team's velocity to estimate their capacity in the next Sprint
  • describe how to manage the Sprint
  • describe how to limit the work in progress
  • Course Number: