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.

The 3-day Agile/ScrumMaster/Crystal course from Dr. Alistair Cockburn

is designed as a series of group activities, introspections, lecture, and techniques. Part of the fun of the course (really!) is taking the ScrumAlliance CSM exam during the class, so that students have their CSM certificate before they leave. In addition, the course includes the book Crystal Clear, which shows typical techniques and work products used on agile projects.

 

Day 1 focuses on : Customer-focused, timeboxed development, Ground rules of Scrum, and Incremental development with status tracking.

In Customer-focused, timeboxed development, teams are given a time-boxed assignment to carry out, consisting of a "customer" and a development team. At the end of the time-box, all the teams discuss what they learned and what they might do differently. Later in the day, they are given a chance to do better with a similar assignment.

In Ground rules of Scrum, the class spends several hours reading and discussing the rules and roles of Scrum, in groups and in full-class discussion.

In Incremental development with status tracking, teams are given a project management assignment, present their results to the larger class, and learn some less-obvious aspects of both incremental development and status reporting.

 

Day 2 focuses on Theory of software development, the CSM exam, and Communication-intensive development with reflective improvement.

Theory of software development. A class can give only the basic elements of agile. Back at the office, the team has to know how to modify the base concepts into locally efficient strategies. This section goes to understanding the theory of team design and software development, so the attendees can see /why/ agile development works as it does, and how to tune team strategies on the fly.

The CSM exam.

The rules of the ScrumAlliance changed in Oct'09, so that people must take a timed exam online to become a CSM. I have found that taking the exam during the class helps anchor the material, and in addition, helps motivate attendees because they leave the class with the CSM certificate, instead of just a permission to take the exam later. During this section of the class, the entire class takes the exam online in a timed exercise. Laptops or computers with web access are needed for this.

Communication-intensive development with reflective improvement.

Teams are given several tries at a time-boxed assignment. After each round, they learn how to reflect and improve their performance. This active module anchors several lessons important to agile development, and teaches them a quick and effective way to capture lessons after each sprint.

 

Day 3 focuses on Nano-incremental development, Project planning jam session, and Story-mapping

 Nano-incremental development. The best programmers work in 15- to 45-minute increments, but few of the rest of the world know how to do that. The best Product Owners or Business Analysts know how to slice their requests into small enough pieces to give to programmers who don't know how to do that. This activity needs about 1/3 of the class to program during the class, with 2 non-programmers per team helping in other ways. At the end of the exercise, both Product Owners and programmers alike see how to slice problems thinner, and how to sequence those slices for maximum value.

Project Planning Jam Session (Blitz planning).

Far from "not planning", the practiced agile team plans and checks it's plan often. To do this, a fast planning technique is needed. This module introduces an index-card based project-planning technique. The technique is used to surface dependencies and unknowns that often disrupt even a well-run agile project. Being quick and effective, it can be done at the end of every iteration or after each delivery, to set up for the next delivery.

Story mapping.

This activity introduces Jeff Patton's "Story Mapping" technique, which is used to aggregate user stories into a 2D map of users x activities in order to get a better picture of the product being built. The story map is then sliced for use as a product backlog.

Dates:	22-24 Feb 2010
Location:	Paris, France
Venue:	Paris La Défense Cœur Défense - Tour A 110, esplanade du Général de Gaulle Paris, France http://www.valtech-training.fr/fr/index/training/formations/methodes_pratiques_agiles/CSM-AGILE.html Get Directions
Price:	1 800,00 € per person

The 3-day Agile/ScrumMaster/Crystal course from Dr. Alistair Cockburn

　

The course is designed as a series of group activities, introspections, lecture, and techniques. Part of the course is taking the ScrumAlliance CSM exam during the class, so that students have their CSM certificate before they leave. In addition, the course includes the book Crystal Clear, which shows typical techniques and work products used on agile projects.

　

 

 

Day 1:

 

 

Customer-focused, timeboxed development

Teams are given a time-boxed assignment to carry out, consisting of a "customer" and a development team. At the end of the time-box, all the teams discuss what they learned and what they might do differently. Later in the day, they are given a chance to do better with a similar assignment.

Ground rules of Scrum

The class spends several hours reading and discussing the rules and roles of Scrum, in groups and in full-class discussion.

Incremental development with status tracking

Teams are given a project management assignment, present their results to the larger class, and learn some less-obvious aspects of both incremental development and status reporting.

 

　

 

Theory of software development

A class can give only the basic elements of agile. Back at the office, the team has to know how to modify the base concepts into locally efficient strategies. This section goes to understanding the theory of team design and software development, so the attendees can see /why/ agile development works as it does, and how to tune team strategies on the fly.

The CSM exam

The rules of the ScrumAlliance changed in Oct'09, so that people must take a timed exam online to become a CSM. I have found that taking the exam during the class helps anchor the material, and in addition, helps motivate attendees because they leave the class with the CSM certificate, instead of just a permission to take the exam later. During this section of the class, the entire class takes the exam online in a timed exercise. Laptops or computers with web access are needed for this.

Communication-intensive development with reflective improvement

Teams are given several tries at a time-boxed assignment. After each round, they learn how to reflect and improve their performance. This active module anchors several lessons important to agile development, and teaches them a quick and effective way to capture lessons after each sprint.

 

　

 

Nano-incremental development

The best programmers work in 15- to 45-minute increments, but few of the rest of the world know how to do that. The best Product Owners or Business Analysts know how to slice their requests into small enough pieces to give to programmers who don't know how to do that. This activity needs about 1/3 of the class to program during the class, with 2 non-programmers per team helping in other ways. At the end of the exercise, both Product Owners and programmers alike see how to slice problems thinner, and how to sequence those slices for maximum value.

Project Planning Jam Session (Blitz planning)

Far from "not planning", the practiced agile team plans and checks it's plan often. To do this, a fast planning technique is needed. This module introduces an index-card based project-planning technique. The technique is used to surface dependencies and unknowns that often disrupt even a well-run agile project. Being quick and effective, it can be done at the end of every iteration or after each delivery, to set up for the next delivery.

Story mapping

This activity introduces Jeff Patton's "Story Mapping" technique, which is used to aggregate user stories into a 2D map of users x activities in order to get a better picture of the product being built. The story map is then sliced for use as a product backlog.