InfoQ

News

Presentation: "We Suck Less!" Is Not Enough

Posted by Abel Avram on Aug 15, 2008 08:05 AM

Community
Agile
Topics
Adopting Agile
Tags
Failure ,
agile2008

In this presentation filmed during Agile 2008, David Douglas and Robin Dymond discuss about companies which try to adopt Agile, but don't go all the way, resulting in failure and rejection of it, and predictably having a negative impact on Agile's future.

Watch: "We Suck Less!" Is Not Enough (1h 25 min)

According to a study made by Forrester in 2007, cited by David, “Many of these shops (companies adopting Agile) aren’t completely clear about what Agile adoption really entails.” Many adopting Agile companies are happy if they are doing "OK", which means a 50% productivity improvement. They are not aware they can have a 500% increase in productivity. David says the bar is set very low if our Agile adoption motto is "We suck less".

David says the current perception of Agile in the market today is:

  • Superior to current practice
  • Set of tools (major financial services firm)
  • Cheap, easy, and runs on its own (medical manufacturing company)
  • Project solution

Agile should be perceived as:

  • An entire work system
  • Designed for 5x+ productivity gains
  • Requires organizational redesign
  • Requires significant change management

Robin continues by giving several examples of large corporations which started doing Scrum at some point, but returned to the old waterfall approach. According to Robin, an important factor in Agile adoption failure is organizational structure which is not matching the development process.

David predicts Agile adoption failure cases will grow in the future and will have a negative impact on Agile. He recommends the following actions to be takes:

  • Recognize we have a problem and begin collaborating on a solution
  • Be transparent about levels of Agility
  • Create a clear position on what is Agile
  • Measure and quantify productivity and speed
  • Put organizational design on the Agenda

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.
Thats true with everything in this field by Francois Ward Posted Aug 15, 2008 8:15 AM
Re: Thats true with everything in this field by Mike Funk Posted Aug 19, 2008 7:40 AM
Only large projects? by Rukshan Jayaratna Posted Aug 20, 2008 4:06 AM
Insights from presentation by Robin Dymond Posted Sep 3, 2008 11:11 PM
  1. Back to top

    Thats true with everything in this field

    Aug 15, 2008 8:15 AM by Francois Ward

    The whole "take what we think is important, but don't go all the way" paradigm is omnipresent in the field, and is one of the major cause of project failures.

    Often, when new methodologies or technologies are introduced, there has been great in depth analysis of the potential pitfalls, and documentation on how to avoid them (often as part of the core methodology or tool or whatever). These are often ignored by teams as "not for us", "doesn't fit in our company", "people would never accept it", etc etc.

    So then all of the severe flaws of the methodology, tool, technology, API, whatever which were thought about in the planning stage, are left wide open, and the people blame the methodology. Its -always- like that.

  2. Back to top

    Re: Thats true with everything in this field

    Aug 19, 2008 7:40 AM by Mike Funk

    Francois's experience mirrors my own. In the past 4 years, I've only seen Scrum implemented correctly twice. I suspect 90% of those companies using Scrum do so in name only.

  3. Back to top

    Only large projects?

    Aug 20, 2008 4:06 AM by Rukshan Jayaratna

    I've been scanning around agile material. Most are very large projects. My company have turned out projects with 3-4 team members max, working for some times less than 2 months. Recently I've tested out a team where the team PM, was more "Agile Coach" role and the team consisted of a BA plus two developers. The result turned out good. No way of comparison, since from the start of the company we were into Agile.

  4. Back to top

    Insights from presentation

    Sep 3, 2008 11:11 PM by Robin Dymond

    The challenge presented to executives and leaders in organizations is to recognize the fundamental organizational design issues that sustained Agile adoption requires. At the end of the presentation we work with the audience on an exercise to define what is "done" for an enterprise Agile adoption. Insightful discussion and ideas are presented, including from Steve Greene and members of the Salesforce R&D team.

    Innovel is a leading Scrum, Agile, and Lean training and consulting firm. Industry and academic contribution are core parts of our business. In addition to this presentation, Robin Dymond presented a new training simulation that has been made available at no charge to companies and consultants training businesses to use Agile methods.

    Regards, Robin Dymond, CST
    Managing Partner, Innovel
    Assistant Producer Learning and Education Stage Agile 2008

Educational Content

Bindings, Platforms, and Innovation

This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.

Orchestrating Long Running Activities with JBoss / JBPM

This article explores the use of JBoss and jBPM to implement design solutions that effectively address the issue of orchestrating long running activities.

Neo4j - The Benefits of Graph Databases

This presentation covers the use of graph databases as an optimal solution for data that is difficult to fit in static tables, rapidly evolving data or data that has a lot of optional attributes.

Realistic about Risk: Software development with Real Options

This session introduces Real Options and shows how it can help in running your project. Real Options is a decision-making process that can be used to manage risk.

Communication Flexibility Using Bindings

This article discusses the use of bindings on services and references (including the instance of non-configured bindings) as the means to implement SCA communications in a Web and SOA environment.

Writing DSLs in Groovy

After a short introduction to DSLs, Scott Davis plays with the keyboard showing how to approach the creation of a DSL by typing working snippets of Groovy code that get executed.

Scaling Agile with C/ALM (Collaborative Application Lifecycle Management)

IBM Rational and InfoQ present, Scaling Agile with C/ALM, an eBook showing organizations how to become “finely tuned software delivery machines” by enabling team integration and scaling.

Concurrent Programming with Microsoft F#

Amanda Laucher presents a real life enterprise application written in F#. She shows actual code snippets, explaining design decisions and suggesting how to use some of the F# constructs.