Certified ScrumMaster

All CSM courses are taught by Certified Scrum Trainers. Taking a CSM course, passing the CSM test, and accepting the license agreement designates you as a Certified ScrumMaster, which indicates that you have been introduced to and understand the basic concepts you need to perform as a ScrumMaster or team member on a Scrum team. This course also satisfies two elements of the CSD track: Scrum Introduction and Elective.

Overview

In this two-day course, you will apply the Scrum framework to build a new product. You will learn what it feels like to be on a Scrum team—experiencing many of the challenges you're likely to face—while being coached by someone involved with the application of Scrum at many organizations. This “learning by doing” style of instruction demands your open mind and active participation.

We will apply the experiential activities to discussion of advanced topics such as how to use Scrum in multiple-team organizations, how to measure progress empirically at a macro level, release planning to maximize ROI, and why such a simple framework disrupts organizations to be the best they can be.

Participants who complete the course successfully will be designated “Certified ScrumMaster” (CSM). This certification includes a one-year membership in the Scrum Alliance, where additional Certified ScrumMaster-only material and information are available.

Pre-requisites

Participants are required to read the following books prior to class:

•  "Agile Project Management with Scrum", Ken Schwaber. Microsoft Press. 2004
•  "Agile Estimating and Planning, Mike Cohn". Prentice Hall. 2005
•  "Agile Software Development with Scrum", Ken Schwaber and Mike Beedle. Prentice Hall. 2001

Who Should Attend

This course is suitable for anyone working in software development and IT, including: Project managers, team leads, and IT/development managers, architects, developers and other team members.

Contents

Overview of Scrum 

• Why Scrum?
• What is Scrum?

Meetings 

• The daily scrum 
• Sprint Planning
• Sprint review 
• Sprint retrospective 

The Product Backlog

• What is the Product Backlog
• Size of the items 
• Writing User Stories
• User stories on the product backlog 
• INVEST   

Estimating and Planning

• Planning Poker
• Dog Points

Tracking progress

• Sprint burndown graph 
• Task boards

Definition of "Done"

• Technical debt and architecture in a Scrum environment

The ScrumMaster 

• Description
• Responsibilities 
• A day in the life of a ScrumMaster

The Product Owner 

• Description 
• Responsibilities 

The Team  

• Description
• Roles
• Teams are cross-functional  

Sprints 

• Potentially shippable 
• Sprint length 
• Release sprints 
• Abnormal terminations   
• Velocity  

Release planning

• Release Burndown graph
• The Alternative Product Burndown graph  

Scalability 

• The scrum of scrums 
• A large team (model #1) 
• A large team (model #2)