exercises and case studies will be scattered throughout the two-day
session. Longer exercises are detailed below. Ample material is
available for this session, and while all essential information will be
covered, time spent on each topic will vary depending on the composition of the
class and the interest in particular areas. A more detailed course
outline is available at our website.
Agile Thinking: In order for us to understand
the benefits of Scrum and the nuances behind its framework, we begin with the
history of agile methods and how relatively new thoughts in software
development have brought us to Scrum. “The Art of the Possible” is
an opportunity to understand how small changes in behavior can have a large
impact on productivity. This also turns our thinking towards new ideas
and a willingness to change for the better.
Here we’ll ensure that we’re all working from the same foundational concepts
that make up the Scrum Framework. We’ll
review the three areas that impact an organization most as we move ahead with
Scrum and explain the different Scrum Roles, Artifacts, and Meetings.
Considerations: Moving beyond Scrum’s foundational concepts, we’ll use this time to dig deeper
into the reasons for pursuing Scrum. We’ll
also begin a discussion of integrity in the marketplace and how this relates to
Exercise: The 59-minute Scrum Simulation. This popular
exposure to Scrum originally developed by Jean Tabaka asks us to work on a short project that lasts for just 59
minutes! We’ll walk through all of the key steps under the Scrum
framework as we work in project teams to deliver a new product.
Scrum Roles: Who are the different players
in the Scrum game? We’ll review checklists of role expectations in
preparation for further detail later in our session.
establishing product expectations.
This is a long-running exercise where we will discuss and practice
various aspects of product and project planning in an agile Scrum environment.
The Product Backlog: This section includes Product Visioning and Progressive Elaboration. The Scrum Team must have an understanding of our Product Vision so they can make good decisions, and the organization must have an understanding of our Vision to provide funding. The Product Backlog is a reflection of that Vision.
Exercise: We'll go through the initial steps of creating a "healthy" Product Backlog as we practice developing its content. Here we will begin using User Stories, guided by Bill Wake's INVEST model. This is the beginning of our project definition that will be used as part of our discussions and exercises that follow.
Velocity and Story Points: Since a Product Owner is responsible for monitoring progress, we'll discuss and practice how to measure a Team's progress in delivering product features. We'll be discussing relative effort, Planning Poke, Story Points, Ideal Team Days, and Team Capacity.
Prioritization Considerations and Methods: Prioritization is the Product Owner's number tool for maximizing return on investment. In this section we'll review different techniques available to establish meaningful priorities, including Weighted Impacts, Theme Screening, and Kano Modeling.
References and Advanced Considerations:
This section of our material acts a reference for more detailed information
regarding Meetings, Artifacts, Advanced Considerations, and additional thoughts on Extracting Value from our endeavors.
Closing Topics: We’ll wrap up with direction
on where to go next with your Scrum experience, some Scrum reference sites, and
our graduation ceremony.