Professional Scrum Master

Taught by Ken Schwaber
May 25-26, 2010 in Columbus, OH, United States

Scrum.org offers a free assessment of your knowledge of Scrum at http://www.scrum.org/scrumopen/

The average score for someone without any training, but who has pursued the Scrum Guide, is 72.
The average score for someone who has take a Certified ScrumMaster course from the Scrum Alliance is 76.
The average score for someone who has take this Scrum in Depth course is 92%

Scrum in Depth – also known as Certified Scrum Master II – is the first significant update of the Certified Scrum Master program since Ken Schwaber first introduced it in 2002. Building on Ken’s experience (also from his numerous coaching engagements in those 8 years) and feedback from Scrum Masters world-wide this unique training experience is fine tuned to give participants a solid grounding in Scrum and its core principles, from which they can make opportunistic decisions about how to use it best. Students learn why certain decisions are better than others, and why some support Agility while others ultimately lead back to waterfall. They will also learn how to use Scrum productivity metrics to monitor the results of their decisions and how to optimize those results.

Registration for this class has closed.

Description

Purpose
The purpose of the Scrum in Depth course is give students the grounding in Scrum and its first principles from which they can make opportunistic decisions about how to use it best. Using Scrum to optimize the results requires a solid knowledge of how it works and why. In the SID course, numerous team exercises give students a chance to try their hand at using Scrum while guided by fellow classmates and Ken. This gives students the opportunity to think of using Scrum in various situations as well as the changes that are required to do so.

Several advanced topics that build on Scrum’s underlying metrics are included in the course, such as managing risk and optimizing total cost of ownership.

Structure

Scrum basics – what is Scrum and its history?
Scrum theory: why does Scrum work and what are the first principles? How are these different from more traditional approaches and what is the impact?
Scrum framework, roles, rules, and flow: how the theory is implemented in the Scrum using the Scrum time-boxes, roles, rules, and artifacts. How can these be used most effectively and how can they fall apart?
Increments: A Scrum increment has to be transparent and ready for inspection. What does this mean, what is a “done” increment, and what happens to “undone” work.
Emergent Architecture: Scrum is empirical. What is the impact of empiricism and emergence on complex architectures and infrastructure development?
Scrum Planning –and Reporting Plan a project and estimate its cost and completion date.
Scrum and Change: Scrum is different. What does this mean to my project and my organization? How do I best adopt Scrum given the change that is expected?
Scrum and Total Cost of Ownership – A system isn’t just developed. It is also sustained, maintained and enhanced. How is the overall cost of this Total Cost of Ownership measured and optimized?
Scaling Scrum – Scrum works great with one team. It also works better than anything else for projects or product releases that involve hundreds and thousands of people dispersed over the globe. How is this best done and managed?