Difference between revisions of "Certified ScrumMaster Course PLUS"

Line 58: Line 58:
 
<br>
 
<br>
 
== Outline: Core CSM ==
 
== Outline: Core CSM ==
* Agile and Scrum Overview
+
* '''Agile Overview''' — Agile product development frameworks aim to increase flexibility or agility in the development organization, and thereby enable business agility. They emphasize increasing transparency, inspection, and adaption, and flexible workers. By far, Scrum is the most popular agile framework, with good reason. We examine some of the big ideas.
* Scrum Background
 
* Scrum Overview
 
* Scrum Roles and Responsibilities
 
* Scrum Artifacts
 
* Scrum Events
 
* Sprint Planning Meeting
 
* Sprint
 
* Daily Scrum
 
* Sprint Review Meeting
 
* Backlogs and Burndown Charts
 
* Release Planning
 
* The Art of the ScrumMaster
 
* Tools for Fostering Self-Organizing Teams
 
* Introducing Scrum into the Organization
 
  
 +
* '''Scrum Background''' — The roots of Scrum start in the 1986 Harvard Business Review paper, ''The New New Product Development Game''. We examine the background behind this research, and the key ideas in the paper, which were the impetus for Scrum.
 +
 +
* '''Scrum Overview''' — In this section, we summarize the key elements of Scrum, including roles, events, artifacts, and values. And especially, the need for transparency, inspection, and adaptation.
 +
 +
* '''Scrum Roles and Responsibilities''' — Team, Product Owner, and ScrumMaster are the three key roles of Scrum. We explore the behaviors and responsibilities of each role, and how that may differ from your current organization.
 +
 +
* '''Scrum Artifacts''' — The Product Backlog of items, and Sprint Backlog of tasks, and the Product Increment are the three key artifacts of Scrum. We examine their contents, and how to create, modify, and use the backlogs.
 +
 +
* '''Sprint''' — The Scrum Sprint is the short iteration within which the Team creates a Potentially Shippable Product Increment (PSPI). We explore the implications of working in Sprints that deliver PSPI.
 +
 +
* '''Sprint Planning Meeting''' — This meeting kicks off the Sprint, in which the Product Owner offers a list of Product Backlog Items to the Team, and the Team creates a Sprint Backlog and forecast. We look at the outcomes and techniques for this meeting.
 +
 +
* '''Daily Scrum''' — This is a daily short meeting in which the self-managing Team members update each other on their progress, to foster coordination and collaboration. We examine the rules and techniques.
 +
 +
* '''Product Backlog Refinement'' —
 +
 +
* '''Sprint Review Meeting''' —
 +
 +
* '''Sprint Retrospective Meeting''' —
 +
 +
* '''Backlogs and Burndown Charts''' —
 +
 +
* '''Release Planning''' —
 +
 +
* '''The Art of the ScrumMaster''' —
 +
 +
* '''Tools for Fostering Self-Organizing Teams''' —
 +
 +
* '''Introducing Scrum into the Organization''' —
  
 
== Outline: PLUS Topics Include... ==
 
== Outline: PLUS Topics Include... ==

Revision as of 13:22, 18 January 2013

Overview

3 days

The standard, basic CSM is two days; this CSM PLUS is a three-day in-depth seminar on the art of serving as an effective ScrumMaster or agile leader, on the Scrum framework, and the organizational changes involved in adopting Scrum. In addition to all standard CSM content, you will learn -- through exercises and discussion – more key concepts and skills in Scrum and agile methods, including Large-Scale Scrum, agile organizational design, enterprise-level adoption and transition, Scrum in the context of offshore and/or multisite development, specification by example and its relationship to Acceptance TDD, how to do agile estimation, splitting large requirements into smaller customer-centric requirements, Product Backlog prioritization, how to facilitate a Scrum Retrospective, how to coach a Sprint Review, and more.

Surveys show that Scrum is by far the most popular agile method worldwide -- and with good reason.

There are three roles in Scrum: Team(s), Product Owner, and ScrumMaster. This latter role is NOT a project manager in any traditional sense. The ScrumMaster is a process coach -- someone who is a master of the Scrum method and helps the teams and product owner apply it and maximize value with it.

Agile management is as radically different from traditional project management as agile processes are different from traditional methodologies. Rather than plan, instruct and direct, the agile coach facilitates, coaches and leads. This person is called a ScrumMaster in the Scrum agile process to denote the difference and remind the person filling this role of the new responsibilities. Accepted participants learn how to be a ScrumMaster and how to make a development team, a product group, or an organization agile. Exercises, case studies, and examples used to bring home the realization of how to be a ScrumMaster instead of a project manager.


Methods of Education

Discussion, presentation, Q&A, workshop exercises


Audience

Anyone interested in adopting Scrum should take CSM PLUS as a foundation -- including potential Product Owners, and the leadership team. And certainly, anyone wishing to serve as a ScrumMaster.


Level

Introductory: This course assumes no prerequisite skills, other than the readings listed in the Prerequisites section. Students will learn and apply skills (both "hard" and "soft") during the session.


Prerequisites: Pre-readings

Participants must read (available online), before the course:


Unless otherwise arranged, every participant is also required to have read the following chapters from Scaling Lean & Agile Development: Thinking and Organizational Tools for Scrum (Larman & Vodde), before the course:

  • Chapter 2: Systems Thinking
  • Chapter 4: Queuing Theory
  • Chapter 8: Teams

NOTE! Your company may have an online Safari account that you can use to read the book chapters online free. Please ask your colleagues if you have a Safari account.

Objectives

Through education and practice, a ScrumMaster should be able to:

  • Remove the barriers between development and the customer so the customer directly drives development;
  • Teach the customer how to maximize ROI and meet their objectives through Scrum;
  • Improve the lives of the development team by facilitating creativity and empowerment;
  • Improve the productivity of the development team in any way possible; and,
  • Improve the engineering practices and tools so each increment of functionality is potentially shippable

In addition to the above, PLUS objectives include ability to coach or advise more in-depth agile and Scrum practices, including retrospectives, agile engineering practices, and estimation sessions.

Outline: Core CSM

  • Agile Overview — Agile product development frameworks aim to increase flexibility or agility in the development organization, and thereby enable business agility. They emphasize increasing transparency, inspection, and adaption, and flexible workers. By far, Scrum is the most popular agile framework, with good reason. We examine some of the big ideas.
  • Scrum Background — The roots of Scrum start in the 1986 Harvard Business Review paper, The New New Product Development Game. We examine the background behind this research, and the key ideas in the paper, which were the impetus for Scrum.
  • Scrum Overview — In this section, we summarize the key elements of Scrum, including roles, events, artifacts, and values. And especially, the need for transparency, inspection, and adaptation.
  • Scrum Roles and Responsibilities — Team, Product Owner, and ScrumMaster are the three key roles of Scrum. We explore the behaviors and responsibilities of each role, and how that may differ from your current organization.
  • Scrum Artifacts — The Product Backlog of items, and Sprint Backlog of tasks, and the Product Increment are the three key artifacts of Scrum. We examine their contents, and how to create, modify, and use the backlogs.
  • Sprint — The Scrum Sprint is the short iteration within which the Team creates a Potentially Shippable Product Increment (PSPI). We explore the implications of working in Sprints that deliver PSPI.
  • Sprint Planning Meeting — This meeting kicks off the Sprint, in which the Product Owner offers a list of Product Backlog Items to the Team, and the Team creates a Sprint Backlog and forecast. We look at the outcomes and techniques for this meeting.
  • Daily Scrum — This is a daily short meeting in which the self-managing Team members update each other on their progress, to foster coordination and collaboration. We examine the rules and techniques.
  • 'Product Backlog Refinement
  • Sprint Review Meeting
  • Sprint Retrospective Meeting
  • Backlogs and Burndown Charts
  • Release Planning
  • The Art of the ScrumMaster
  • Tools for Fostering Self-Organizing Teams
  • Introducing Scrum into the Organization

Outline: PLUS Topics Include...

  • many more exercises
  • agile estimation with relative point estimation, estimation poker, monte carlo simulation, and more
  • retrospectives with system dynamics analysis, root cause analysis, collaboration exercises, and more
  • Large-Scale Scrum for large, multisite, and offshore development
  • visual management tools
  • lean thinking and Scrum
  • splitting large requirements into smaller customer-centric requirements
  • the 3 Cs of user stories: card, conversation, confirmation
  • details of facilitating parts 1 and 2 of a Sprint Planning Meeting
  • agile requirements analysis
  • specification by example, and acceptance test-driven development
  • design workshops & agile architecture




Graduation/Certification/Exam

Not everyone who attends may achieve certification; it depends on demonstration of values and knowledge consistent with Scrum, and at least fulfilling the course prerequisites. Certified ScrumMasters will be recorded at www.scrumalliance.org.

There is an online exam to take, at the ScrumAlliance, to complete the certification process. For more, see here.


Maximum Participants

35


Environment - Room, Tools, Texts

Read this: Course Environment - Workshop Style1


Text and Notes

  • THESE MUST BE SUPPLIED FOR THE ATTENDEES BY THE CLIENT *BEFORE* the course: Scaling Lean & Agile Development: Thinking and Organizational Tools for Scrum (Larman & Vodde), so that the PREREQUISITE READINGS can be completed (unless otherwise agreed). It can be ordered from Amazon here. It is also possible that other colleagues at your company have copies, and people can borrow or share one. Or, perhaps the company has a Safari account with access to the digital version.
  • There is a course PDF for the presentations. We may decide to give the students a file copy to view on a laptop or a paper copy, depending on situation.