Class
CSM Certified ScrumMaster
Taught by Jeff Sutherland and Scott Downey
April 29-30, 2010 in Beverley Hills, California, United States
This course will be led by Jeff Sutherland, Co-Creator of Scrum. Scott Downey, Scrum Coach at MySpace, will assist him with this training.
Jeff Sutherland started the first Scrum at Easel Corporation in 1993. He worked with Ken Schwaber to emerge Scrum as a formal process at OOPSLA ’95. Together, they extended and enhanced Scrum at many software companies and IT organizations and helped write the Agile Manifesto. Jeff’s company, Scrum, Inc. is located at OpenView Labs, a venture capital group where he is Agile coach to portfolio companies. The OpenView venture group runs all its operations with Scrum. As Senior Advisor to OpenView he focuses on using Scrum to transform companies as well as empower software developers. Jeff has been CTO/VP of Engineering of 9 software companies and his last one, PatientKeeper, quadrupled revenue in 2007. OpenView Venture Partners wants to create similar high performance in portfolio companies. Jeff will share the secret sauce he developed for the venture group that helps teams radically improve productivity and quality while providing a more rewarding and fun working environment for developers.
Jeff is an expert on distributed/outsourced Scrum and on implementing Scrum in a CMMI Level 5 company. He is also an expert on “Scrum at Church” where has helped his wife, Rev. Arline Sutherland, start up Scrum in four churches and in denominational headquarters. He has has scaled and distributed Scrum using his last five companies as laboratories and specializes in the Type C Scrum he implemented at PatientKeeper where the whole company was involved in Scrum. PatientKeeper developers delivered 10 times faster than waterfall teams they used for outsourcing.
Jeff using Lean concepts in his Scrum implementations and has done joint workshops with Mary Poppendieck. In Lean Software Development Mary comments: Five years ago a killer application emerged in the health care industry: Give doctors access to patient information on a PDA. Today there is no question which company won the race to dominate this exploding market; PatientKeeper has overwhelmed its competition with its capability to bring new products and features to market just about every week. The sixty or so technical people produce more software than many organizations several times larger, and they do not show any sign that the size of their code base is slowing them down.
A key strategy that has kept PatientKeeper at the front of the pack is an emphasis on unprecedented speed in delivering new features. It will not surprise anyone who understands Lean that PatientKeeper has to maintain superb quality in order to support its rapid delivery. CTO Jeff Sutherland explains it this way:
“Rapid cycle time:
* Increases learning tremendously * Eliminates buggy software because you die if you don’t fix this. * Fixes the install process because you die if you have to install 45 releases this year and install is not easy. * Improves the upgrade process because there is a constant flow of upgrades that are mandatory. Makes upgrades easy. * Forces quick standardization of software via new features rather than customization and one off. * Forces implementation of sustainable pace. You die a death of attrition without it. * Allows waiting to build new functionality until there are 4-5 customers who pay for it. This is counterintuitive, and caused by the fact everything is ready within 90 days.”“I find that the vast majority of organizations are still trying to do too much stuff, and thus find themselves thrashing. The only organization I know of which has really solved this is PatientKeeper.” Mary Poppendieck
In this course, participants will learn everything necessary for getting started with Scrum. There are very few rules to Scrum so it is important to learn its fundamental principles by experiencing them directly from those who have implemented the best Scrums in the software industry. Participants gain hands-on practice with the release backlog, sprint backlog, the daily Scrum meeting, tracking progress with a burndown chart, and more. Participants experience the Scrum process through a “59-minute Scrum” and the "XP Game” which simulate Scrum projects through non-technical group exercises.
The course will run from 9am-5pm each day.
Following the course, each participant is enrolled as a Certified ScrumMaster, which includes a one-year membership in the Scrum Alliance, where additional Certified ScrumMaster-only material and information are available.
PMPs: You can receive 16 Professional Development Units (PDUs) for this course.
Course Material:
Participants will receive course materials for review at the start of the course. A course syllabus is available at http://jeffsutherland.com/csmsyllabus.pdf
Registration for this class has closed.
Venue
The Olympic Collection Banquet & Conference Center
11301 Olympic Boulevard #204
Los Angeles, CA 90064
Phone: (310) 575-4585
www.ocbanquet.com
Questions?
Description
Overview of Scrum* Why Scrum works
* What Scrum is
* Origins
Sprints
* Potentially shippable
* Architecture on a Scrum project
* Sequential vs. overlapping work
* Sprint length
* Release sprints
* Abnormal terminations
The ScrumMaster
* Responsibilities
* ScrumMaster mindset
* Situational ScrumMastering
* ScrumMaster as team member
The 59-minute Scrum project
The product owner
* Description
* Responsibilities
* Sharing the vision
Product backlog
* Size of the items
* User stories on the product backlog
* Backlog-writing workshops
* INVEST in your backlog
Meetings
* The daily scrum
* Sprint review
* Sprint retrospective
Sprint planning
* Sprint prioritization
* Sprint goal
* Sprint planning meeting
* Sprint backlog items
Release planning
* Velocity
* Estimating the product backlog
* Release planning meeting
* XP game Sprint execution exercise
Tracking progress
* Sprint burndown charts
* Release burndown charts
* Task boards
The team
* Composition
* Teams are cross-functional
* Organizing
Scalability
* The scrum of scrums
* Focus of initial sprints
* Shared vs. specific product backlogs
* Distributed, outsourced, and CMMI Scrum
* Getting started
