Students will be introduced to the foundational aspects of agility, including an overview of Scrum. This module helps to form the basis for the rest of this course by focusing on the Agile Mindset, Values, Principles, and Practices. It is crucial that anyone using Scrum has a shared understanding of these topics in their organization, as a starting point for more strategic conversations.
Successful implementations of Scrum must have a clear understanding of the three Scrum Roles. This module begins with introducing the concept of the Scrum Team and its attributes. Students will then explore the activities and responsibilities of the Scrum Master, Product Owner, and Developer to understand the differences and relationships between these three roles. They then put all the pieces back together into a cohesive picture of roles and responsibilities.
This module focuses on the artifacts used in the Scrum framework that represent work or value. Students will be introduced to the concepts of the Product Backlog, Product Goal, and Product Backlog Items to form this foundation. We will explore popular techniques to represent Product Backlog Items including Personas, User Stories, and Acceptance Criteria, tying these concepts together in the definition of the Increment and the Definition of “Done”.
Sprint Events – Part 1
We start exploring the events within Scrum by defining the concepts of a Sprint, a fixed time that provides the Scrum Team an opportunity to deliver value. Then, looking at each event individually, we define what topics make up the Sprint Planning event, including the Sprint Backlog and Sprint Goal. Students then are introduced to the conversation called the Daily Scrum. For each event, we will discuss common pitfalls and behaviors to avoid, known as anti-patterns, along with their potential negative impacts.
Sprint Events – Part 2
This module continues through the cycle of the Sprint, focusing on the Sprint Execution, Sprint Review, and Sprint Retrospective activities and anti-patterns. Students will explore techniques to capture feedback and ways to improve their own interactions and streamline their delivery.
Once the roles, artifacts, and events are defined, we spend several modules analyzing the relationships and connections of these concepts, looking at Scrum as a System. Students explore this “big picture” of the framework and the connections between the different aspects of the framework. Some highlights of these modules include exploring the impacts of adjusting the framework, scheduling activities within a Sprint, and breaking down the day-to-day activities of a Scrum Master. These modules culminate in a set of challenging activities that test the knowledge of students in understanding a more holistic picture of Scrum.