InfoQ

News

Is Scrum Atomic?

Posted by Amr Elssamadisy on May 01, 2007 07:56 AM

Community
Agile
Topics
Methodologies,
Community
Tags
Process Adoption,
Scrum,
Community

Melanie Silver, in Am I, or Am I Not, Using Scrum? That is the Question, asked what it means to be practicing Scrum and answered that you must be doing all of the Scrum practices for this to be true. Most of the comments left agreed with that sentiment, and a few did not. This question is reminiscent of the early XP debates of whether or not you have to be doing all of the twelve practices to be practicing XP. In the XP community, that has been answered in the negative - you do not have to be doing all of the XP practices to be doing XP. So is Scrum like XP or is it indivisible?

Silver started by defining Scrum as adhering to the values of the Agile Manifesto, and having its own distinct characteristics and practices:

  • Three basic roles: Product Owner, ScrumMaster, and Project Team Product Backlog
  • Sprint Backlog
  • Sprint Planning Meeting
  • Daily Scrum Meeting
  • Thirty-day iterations, delivering increments of potentially shippable functionality at the end of each iteration
  • Sprint Reviews Retrospectives
She then went on to ask what isn't Scrum and gave three different scenarios where some of the practices of Scrum were used and some were not. In concluding she cited two main reasons why a team should be doing all of the Scrum practices to be doing Scrum:

Abandoning some of the practices that make Scrum successful gives the naysayer more opportunities to claim Scrum doesn’t work. One would have been much better off espousing the individual techniques that were used than claiming that the Scrum methodology was applied.

Using only certain Scrum techniques and adopting only some of the Scrum characteristics may not preclude you from claiming you are agile. However, I would use this analogy to show why you cannot profess to be using true Scrum: Can you say you've made a batch of chocolate chip cookies if you leave out the chocolate chips?

Most of the comments left by readers of the article agreed that it should be an all-or-nothing thing. Jeff Sutherland commented that only a small percentage of companies who claimed to be doing Scrum actually were:

At the QCON conference in London a couple of weeks ago I gave a presentation on Google's Scrum implementation. Out of about 200 people, 30 said they were doing Scrum. When I went over Nokia's requirements for iterative development, only 15 were even doing iterative development. When I asked if they met Nokia's requirement for calling their teams a Scrum implementation, only 3 out of the 200 said they were really doing Scrum." So his due diligence will be finding the three companies out of 30 who say they are doing Scrum!
So, is Scrum different from XP in that it is indivisible? Does it matter to the Scrum community if it is? Does it matter to the Agile community?  An interesting way to think about this problem is to take software out of the picture, Ron Jeffries does so in We Tried Baseball and It Didn't Work.

Related Sponsor

VersionOne is recognized by Agile practitioners as the leader in Agile project management tools. Companies such as Adobe, BBC, CNN, Dow, HP, IBM, Sony and 3M have turned to VersionOne to help deliver greater value to their customers.

4 comments

Reply

Can the bar actually be lowered? by Bruce Rennie Posted May 2, 2007 8:13 AM
Re: Can the bar actually be lowered? by Amr Elssamadisy Posted May 3, 2007 9:46 AM
Re: Can the bar actually be lowered? by Nicholas Cancelliere Posted May 8, 2007 12:00 PM
qwqwq by berkay NiQuiL Posted Jun 30, 2008 2:03 PM
  1. Back to top

    Can the bar actually be lowered?

    May 2, 2007 8:13 AM by Bruce Rennie

    I mean, it's not all that difficult to implement the Scrum practices. I think the length of a sprint can be argued without any damage, but really, what else is there to discuss?

  2. Back to top

    Re: Can the bar actually be lowered?

    May 3, 2007 9:46 AM by Amr Elssamadisy

    I can think of one valid example off-hand: Stand Up Meetings are frequently dropped with very small, collocated teams (usually under 5 members) that have been practicing Agile for a while and grock the culture. Because the entire team is in one room with a common area they are constantly communicating and a Stand Up Meeting becomes redundant. So, since these meetings are for synching up, and that goal can be achieved without them, are we still doing Scrum? Does it matter?

  3. Back to top

    Re: Can the bar actually be lowered?

    May 8, 2007 12:00 PM by Nicholas Cancelliere

    In response to Amr: If you do not have a set time which the stand-up takes place, how do I as a chicken attend? The primary goal of the stand-up is to "plan the day" and let the team self-organize. Having it at the same time every day makes it a commitment by the team to evaluate daily where they are in terms of the burndown, etc., and offers opportunity for non-team members to sit in (which they're allowed to do as chickens). Constant communication doesn't gurantee the right type of information.

  4. Back to top

    qwqwq

    Jun 30, 2008 2:03 PM by berkay NiQuiL

Exclusive Content

Rationalizing the Presentation Tier

Thin client paradigm characterized by web applications is a kludge that needs to be repudiated. Old compromises are no longer needed and it's time to move the presentation tier to where it belongs.

Agile Project Management: Lessons Learned at Google

In this presentation filmed during QCon 2007, Jeff Sutherland, the creator of Scrum, talks about his visit at Google to do an analysis of Google's first implementation of Scrum.

AtomServer – The Power of Publishing for Data Distribution

In this article, Bryon Jacob and Chris Berry introduce AtomServer, their implementation of a full-fledged Atom Store based on Apache Abdera, which is now available as open source.

An Introduction to Virtualization

It is easy to think that virtualization applies only to servers. In reality the recent resurgence of the concept is also being applied to networking, storage, and application infrastructure.

REST Anti-Patterns

In this article, Stefan Tilkov explains some of the most common anti-patterns found in applications that claim to follow a "RESTful" design and suggests ways to avoid them.

Choosing between Routing and Orchestration in an ESB

In this article, Adrien Louis and Marc Dutoo discuss the differences and relative merits of using orchestration vs. routing in a typical ESB setup, and discuss various implementation options.

Enterprise Batch Processing with Spring

Wayne Lund discusses batch processing, Spring Batch objectives and features, scenarios for usage, Spring Batch architecture, scaling, example code, failures and retrying, and the future roadmap.

User Story Estimation Techniques

Developer Jay Fields draws on his experiences as a ThoughtWorks consultant to describe effective user story estimation techniques.