Sunday, September 24, 2006
The JAOO Conference is coming up next week in Denmark. This is one of the leading annual software developer conferences and highly recommended. Last year, I presented at the JAOO conference on the Roots of Scrum. It was a great conference with about 900 Java and .NET developers in attendance.
InfoQ has just put up a video of the entire Roots of Scrum presentation along with slides that synchronize with the video. Very cool!
The Roots of Scrum marketing pitch on InfoQ concerning Kent Beck, Scrum, and XP is somewhat exaggerated. In the presentation, I discuss the email Kent sent me in 1995 when he requested materials on Scrum. He was certainly aware of Scrum and particularly the Takeuchi and Nonaka 1996 Harvard Business Review paper mentioned in the Roots of Scrum video. XP, however, focuses on engineering practices which are quite useful to Scrum teams. While the first Scrum team used all of what became XP engineering practices in some form, an early decision was made with Ken Schwaber to focus industry-wide rollout of Scrum on team, project management, and scaling issues. As a result, Scrum as a way to manage and scale teams is nicely complementary, yet not overlapping, to XP engineering practices. The highest performing development teams tend to use both Scrum and XP at once as you will notice in my recent paper on the SirsiDynix project.
Next Wednesday at JAOO, I will talk about Scrum Tuning. How do you make your Scrum implementation better and what are best practices observed when watching hyperproductive Scrum teams in action? This will be followed by a two day Scrum certification course at the conference. This CSM course has been sold out for months so those of you who would like to become a Certified ScrumMaster in Denmark should take a look at the October 25-26 CSM Course in Aarhus which will follow the JAOO conference. Contact Anne Sophie Bille at EOS: email@example.com.
Friday, September 22, 2006
21-22 September 2006
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.
The course was given at Jeff's company, PatientKeeper, which is well known as a laboratory for Scrum research. He will be assisted by the PatientKeeper Product Owner who will go through Product Backlog management for a complex product portfolio and will describe how to automate and manage Sprint Backlogs for multiple teams developing a wide variety of integrated and interoperable products.
Jeff is an expert on distributed/outsourced Scrum (see his paper on the SirsiDynix project) and on implementing Scrum in a CMMI Level 5 company (see recent submission to CMMI conference). He has also done research and development on Scrum using his last five companies as laboratories. His entire current company at PatientKeeper is run by a MetaScrum, and is one of the most advance implementions of Scrum worldwide. Mary Poppendieck, in her latest book on Lean Software Development 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."
CSM Training is held in the PatientKeeper boardroom giving participants the unique opportunity to work for two days within a Scrum company. There is a large open space Atrium which is ideal for group exercises. 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.
In this course, 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 a non-technical group exercises.
This course is equally suited for managers, programmers, testers, analysts, product managers, and others who are interested in working on or with a Scrum team. You will leave with solid knowledge of how and why Scrum works. Through practical, hands-on exercises and small-group discussion you will be prepared to plan your first sprint immediately after this class.
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 ScrumMaster-only material and information are available.
About The Instructor:
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. As VP of Engineering and CTO of nine companies, he developed Scrum in four of them and implemented Scrum company-wide in five of them. In recent years, Jeff developed a center of excellence for Scrum training at his current company, PatientKeeper, working with Ken Schwaber, the Co-Creator of Scrum, Rally Development Corporation, a leading tools vendor, and other well-known Scrum consultants and trainers. Many software developers from all over the world have been trained at PatientKeeper where they learn directly from the originators of Scrum as well as from Scrum leaders managing PatientKeeper teams.
Overview of Scrum
Why Scrum works
What Scrum is
Architecture on a Scrum project
Sequential vs. overlapping work
ScrumMaster as team member
The 59-minute Scrum project
The product owner
Sharing the vision
Size of the items
User stories on the product backlog
INVEST in your backlog
The daily scrum
Sprint planning meeting
Sprint backlog items
Estimating the product backlog
Release planning meeting
XP game Sprint execution exercise
Sprint burndown charts
Release burndown charts
Teams are cross-functional
The scrum of scrums
Focus of initial sprints
Shared vs. specific product backlogs
Distributed, outsourced, and CMMI Scrum
Who Should Attend
Whether you're a manager, programmer, tester, analyst, product manager, or someone interested in working on or with a Scrum team, this course is suited for you. You will leave with solid knowledge of how and why Scrum works. Through practical, hands-on exercises and small-group discussion you will be prepared to plan your first sprint immediately after this class.
PMPs: You can receive 16 Professional Development Units (PDUs) for this course.
Participants receive course materials for review upon registration. The CSM course was formulated to train and certify ScrumMasters and is used worldwide for ScrumMaster training. The book, Agile Project Management with Scrum, by Ken Schwaber is required reading for the course and the course is based on the primary Scrum book, Agile Development with Scrum.
Boston CSM Trainings are held in the PatientKeeper Board Room on the second floor of 275 Washington Street in Newton, MA. This is directly off the Mass. Pike and across the street from the Sheraton Hotel, only about a 10-15 minute drive from Logan Airport or from Harvard Square.
275 Washington Street - Second Floor
Newton, MA 02458
The Sheraton Hotel across the street from PatientKeeper is the most convenient. However there are many good hotels in the Harvard area. Check www.hotels.com or your favorite travel site for hotels in Cambridge, MA, and pick one that fits your price.
The fee for Certified ScrumMaster Training is $1200. You can register in three ways:
1. Fax a Purchase Order to PatientKeeper at 617-812-8527
2. Send a check to Jeff Sutherland, PatientKeeper, Inc., 20 Guest Street, Suite 500, Brighton, MA 02135
3. Use the ScrumMaster Training button on the upper left side of this page. This will allow you to use Paypal, or click if you do not have a Paypal account and it will provide you with a credit card screen that will accept any credit card.
Refund policy: 90% of the course fee will be refunded for cancellations more that 7 days in advance of the course. No refunds will be provided for cancellations within a week of the course.
Friday, September 08, 2006
In response to questions about hyperproductive Scrum teams, please take a look at the SirsiDynix project, the most productive large Java project ever documented. A 56 member distributed/outsourced team was split between Provo, Utah; Denver, Colorado; Waterloo, Canada; and St. Petersburg, Russia. They achieved almost the same productivity as a single, colocated Scrum team documented by Mike Cohn in his User Stories book.
For the Complex Systems conference paper below, I also reviewed the first Scrum and how it achieved hyperproductivity using a variant of Toyota's set based engineering. Viewing the phenomenon as a biological model, it systematically induced "punctuated equilibrium" seen in species evolution.
Sutherland, J, Viktorov, A., and Blount, J. (2006) Adaptive Engineering of Large Software Projects with Distributed/Outsourced Teams. In Proceedings of the International Conference on Complex Systems, Boston, MA, 25-30 June.