InterClypse

I recently came across a project that stated they were following an agile methodology, specifically Scrum; however they had not delivered any usable software since the projects inception (over 18 months). In addition, they required a detailed specification prior to the start of development. The specification took over 6 months to produce by a separate team and required several review approval meetings before approval was given to begin development. Are they really following an Scrum? ABSOLUTELY NOT!

What is Scrum?

Scrum is the most popular agile methodology in use today. It was first introduced by Dr. Jeff Sutherland and Ken Schwaber in 1995 at OOPSLA. According to the Agile Alliance, Scrum is an agile, lightweight process that can be used to manage and control software and product development using iterative, incremental practices. Scrum, when used properly, significantly increases productivity and reduces time to market while facilitating adaptive, empirical systems development.

Scrum adheres to the values as defined in the Agile Manifesto: “Through this work we have come to value:

• Individuals and interactions over processes and tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan

Twelve principles underlie the Agile Manifesto, including:

• Customer satisfaction by rapid delivery of useful software
• Working software is delivered frequently (weeks rather than months)
• Working software is the principal measure of progress
• Even late changes in requirements are welcome
• Close, daily cooperation between businesspeople and developers
• Face-to-face conversation is the best form of communication (co-location)
• Projects are built around motivated individuals, who should be trusted
• Continuous attention to technical excellence and good design
• Simplicity
• Self-organizing teams
• Regular adaptation to changing circumstances

Scrum 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
• Retrospectives

Simple questions to determine if you are following Scrum; if you answer no to any of the below then you are not adhering to Scrum.

• Do you have fixed/time boxed iterative development; typically 2-4 week sprints?
• Do you have working software at the end of each iteration or sprint?
• Do you have testing as part of the iteration or sprint?
• Do you have an integrated team that consists of the people formulating the product, the people building the product, the people testing the product, and the people that will use the product?
• Do you require a complete specification before you start development? If you do you are not following Scrum.
• Do you have daily meetings?
• Do you have product backlog?
• Do you have a product owner?