Scrum Log Jeff Sutherland

Scrum is an Agile development framework that Jeff Sutherland invented at Easel Corporation in 1993. Jeff worked with Ken Schwaber to formalize Scrum at OOPSLA'95. Together, they extended and enhanced Scrum at many software companies and helped write the Agile Manifesto.

Saturday, May 30, 2009

Ken Schwaber on "Flaccid Scrum - A New Pandemic?"

Agile Bazaar June Meeting

Date: Thursday June 18
Time: 6:00 - 9:00pm
Place: To be announced (A Burlington location was planned but we are looking for a larger space and will announce it soon)
RSVP: Go to  to register. We expect to fill all the seats, so sign up early!

Food: Will be provided
Cost: Voluntary contribution to offset food expenses is welcome

Scrum has been a very widely adopted Agile process, used for managing such complex work as systems development and development of product releases. When waterfall is no longer in place, however, a lot of long standing habits and dysfunctions have come to light. This is particularly true with Scrum, because transparency is emphasized in Scrum projects.

Some of the dysfunctions include poor quality product and completely inadequate development practices and infrastructure. These arose because the effects of them couldnít be seen very clearly in a waterfall project. In a Scrum project, the impact of poor quality caused by inadequate practices and tooling are seen in every Sprint.

The primary habits that hinder us are flaccid developers and flaccid customers who believe in magic, as in:

Unskilled developers - most developers working in a team are unable to build an increment of product within an iteration. They are unfamiliar with modern engineering and quality practices, and they donít have an infrastructure supportive of these practices.

Ignorant customer - most customers are still used to throwing a book of requirements over the wall to development and wait for the slips to start occurring, all the time adding the inevitable and unavoidable changes.

Belief in magic - most customers and managers still believe that if they want something badly enough and pressure developers enough to do it, that it will happen. They donít understand that the pressure valve is quality and long term product sustainability and viability.

Have you seen these problems? Is your company "tailoring" Scrum to death? Let Ken respond to your issues and questions!

Ken will describe how Scrum addresses these problems and will give us a preview of plans for the future of the Scrum certification efforts.


Blogger Richard said...

Perfect description of an all too common problem!

12:20 PM  

Post a Comment

<< Home