InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Presentation: "We Suck Less!" Is Not Enough

Posted by Abel Avram on Aug 15, 2008

Sections
Process & Practices
Topics
Adopting Agile ,
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
  • This article is part of a featured topic series on Agile

Related Sponsor

In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!

Thats true with everything in this field by Francois Ward Posted
Re: Thats true with everything in this field by Mike Funk Posted
Only large projects? by Rukshan Jayaratna Posted
Insights from presentation by Robin Dymond Posted
  1. Back to top

    Thats true with everything in this field

    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

    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?

    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

    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

Jesper Boeg on Priming Kanban

In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches.

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.