Certified ScrumMaster Slides Now Available


The following is a little story of how I came up with flow to this deck. And what you won’t find in it.

Examining the CSM learning objectives
Printing out the the content outline and course objectives I cut out each learning objective.

Looking for new sequence
Looking for similar phrases I group them together and came up with the clusters: Values, People, Games (Process), Collaboration, Customer Value, Incremental, Timebox, Empiricism, Inspect, Adapt, Transparent, Commitment, Respect, Courage, Focus, Self-organization, Practice/Experience as new focus areas.

Iterating over concepts
I arrange the focus areas to go through the concepts of Roles, Meetings and Artifacts. I can address a concept more than once, from the lens of these focus areas. Before this, I would go through each of the concepts just once.

In converting the objectives to a deck, I turn each objective into a question. For some of them I provide answers, all of which are part of core Scrum concepts. I can go through all the eighty-plus learning objectives, while also enjoying many activities and addressing questions by participants as they arise.

Activities and information outside Scrum not included
What is not in here, are the activities we do in the class, before going over the official answer. Not all answers are provided, either. The deck does not have any answers that deviate from core Scrum sources. We do some fun things like plan and build a city with or create a game about Scrum and do these things using the Scrum Framework. Here’s some finished examples:



This is the basic deck only
The class is set up in an active-learning environment with many activities and movement. Participants learn from each other. I’ve removed most of that for this deck uploaded.

It is the basic deck I went through in the story: Making changes to Project Management during an Agile transition

Your feedback is always appreciated
I hope you enjoy! What do you think of the sequence of concepts?

This entry was posted in #agile explained and tagged , , . Bookmark the permalink.

Comments are closed.