Date: 6-7 March, 2008
Location: Boston, MA, United States
Regular Price: $1800
Jeff started the first Scrum at Easel Corporation in 1993 and worked with Scrum Co-Creator Ken Schwaber, to formalize the Scrum development process at OOPSLA’95. In the same year, Sutherland provided Kent Beck all background information on the creation of Scrum. XP engineering practices then evolved along with SCRUM and the two leading Agile development processes work well together. Scrum and XP are the most widely used Agile processes worldwide and their creators are authors of the Agile Manifesto.
This course will be led by Jeff and you will learn about Scrum in the PatientKeeper Boardroom. PatientKeeper started Scrum seven years ago and has evolved a Scrum implementation that includes the whole company. Jeff's experiences consulting with leading companies like Google, Microsoft, Yahoo, Oracle, Palm, Adobe, Siemens and many others will provide valuable input for new Certified ScrumMasters on how to startup and optimize Scrum teams. For 14 years, Dr. Sutherland has been developing software with Scrum and this experience is useful and fun for participants to hear about.
The PatientKeeper Chief Product Owner will assist Jeff by reviewing the actual PatientKeeper Product Backlog with the class and explaining how he leads a MetaScrum of stakeholders every week and ships dozens of production releases of software every year. You may get to partipate in the PatientKeeper Scrum of Scrums which usually occurs every morning led by the PatientKeeper VP of Engineering.
Jeff has worked with many distributed/outsourced Scrum teams (see his paper on the SirsiDynix project) and has helped implement Scrum in a CMMI Level 5 company (see recent submission to CMMI conference) and several CMMI Level 3 companies. He has used his last five companies as laboratories for inspected and adapting to improve Scrum implementations. Mary Poppendieck reports on Jeff's latest Scrum implementation in her book on Lean Software Development:
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 how to stop thrashing and start executing along with 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 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 "XPGame” which simulate Scrum projects through non-technical group exercises.
The course will run from 9am-5pm each day. A continental breakfast and lunch will be provided.
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.
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.