Certified ScrumMaster Course Agenda

These are the topics cover in class. As with life in general, there is more to do than time to do it, so we have to prioritize to suit the participants’ interest. We also cover many other topics as they come up, some in real time and some in the parking lot section at the end. For any special-interest topics we do not get to, we follow up the class with our list of Agile/Scrum articles.

Agile Principles

  • Agile software development implements Lean principles and dynamics.
  • Scrum is one form of Agile, designed initially for software development but applicable to other kinds of work.

Empirical Process

  • Agile success relies on “Empirical Process”
  • Improvement comes from a continuous learning cycle we call “Inspect and Adapt”.

Scrum Framework

  • Scrum has 4 meetings and 3 artifacts
  • Scrum has 3 roles that share the responsibility of creating value in small increments
  • The roles complement each other to create a balanced team

Scrum Execution

  • Scrum organizes work into 1-4 week time boxes called Sprints
  • Each Sprint has 4 primary meetings
  • The bulk of the time is spent creating value in the form of a product


  • Scrum works best when the Team achieves a smooth flow of work
  • Scrum dynamics are based on the mathematics of queuing theory that we
  • use to manage the Internet

Scrum Planning

  • Scrum planning is continuous
  • Scrum planning happens at 5 levels, each with a different time horizon
  • The Product Backlog is the primary source of work to be completed and value to be delivered

User Stories

  • User Stories are simple descriptions of desired functionality
  • User Stories have two attributes that are helpful for planning: size and priority
  • Stories are elaborated just-in-time for implementation


  • Priorities help the Scrum Team decide what to do next
  • Priorities help with long term planning
  • Prioritization can be done in many ways, based on many criteria


  • Agile estimation is done at both the high level and the low level
  • Estimates are used for planning and for tracking progress
  • Estimates are done quickly, by the Delivery Team
  • Estimates are not commitments

Scrum Enhancers

  • A 1-sprint look-ahead on stories will help the flow
  • Defining Ready and Done will dramatically reduce time waste

Long Term Planning

  • Scrum-built products may have Roadmaps and Release Plans
  • Team velocity is a measure used in long term planning

 Scaling Scrum Up and Out

  • Scrum can scale to many Teams
  • Distributed Scrum is constrained by the laws of physics but there are patterns that can help

Class Project

  • Scrum Simulation

Team Growth

  • Scrum motivates more effectively that traditional financial motivators
  • Teams go through stages
  • Agile technical practices enhance Team success

ScrumMaster Duties

  • The ScrumMaster is responsible for the health and growth of the Scrum Team
  • The ScrumMaster is a facilitator, mentor, negotiator, protector, coach and servant leader

ScrumMaster Skills

  • Listening skills are key to success
  • Knowing how to ask powerful questions will help you coach the Team
  • Modeling desired behavior and use of language can have a strong influence on your Team

Technical Practices

  • Agile technical practices enhance Team success
  • Agile Testing Basics

Scrum Adoption

  • Scrum is simple but not easy
  • Organizations are resistant to change
  • Choosing the easy parts may fail to give the desired results

Parking Lot 

  • Your Topics


  • Personal Actions
  • Class Evaluation
  • Class Picture
  • Graduation Ceremony