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.

InfoQ Interview: David Hussman on Coaching Agile Adoption

Posted by Deborah Hartmann Preuss on Apr 12, 2007

Sections
Process & Practices,
Architecture & Design
Topics
Customers & Requirements ,
Delivering Value ,
Leadership ,
Agile
Tags
Useability ,
Coaching and Mentoring ,
Introducing Agile
David Hussman "Agile Geek at Large" talked to InfoQ about his approach to coaching teams and organizations adopting Agile, including his ideas about customizing it for different kinds of organizations without sacrificing the common denominators required to make Agile really work. Hussman talked about user stories, "story tests", addressing the fears of management as they see the team shifting into self-managed mode, and building a vibrant development community, in this interview: David Hussman on Helping Organizations Adopt Agile.

Asked "What are some of the culture shock that a manager might go through when the team demands ADO and how can the team ease its fears?" Hussman looked at a bit of history while answering:
... somewhere the message came out:"we don't need managers, we don't need testers". I'm not sure [anyone] even said that, but somehow this myth kind of gathered around that. So for me, a lot of it is going in and doing myth-busting with these mangers, to make sure they don't feel ostracized, to make sure that they're part of a larger community. To engage them and say 'what are the things they have to do?' because they have to report to someone. What are their wants? What metrics are generated by an Agile project, whether it's metrics around risk or quality or progress, that plug right into their world?
Hussman takes a pragmatic and flexible approach to communication: take, for example, his view of Agile planning:
I think it's very much cultural and corporate based, like "what are their needs?" So to the manager question again: If the manager needs something specific we might end up translating it back into their needs.
It would be easy to misconstrue that Hussman is all about management... not so. His background includes not only lots of programming, but also plenty of time in the music industry, years in which he learned the amazing value of great teamwork:
I love to write code, that's where I started, but more importantly, what I like is seeing a group of people succeed. So back to my former life as a producer, an engineer or a musician: there's a great feeling of playing a song... jamming away, or bringing a group of people in the recording studio and making a CD, and they come out and they hold it up and say "listen to this!" They're really excited. I think the same thing happens in software: people live their software experience and they keep referencing it, especially times that are good or bad, like "One time we did this!" What inspires me is seeing the Agile stuff recreate that experience more than once, more than accidentally.
Read the InfoQ Interview: David Hussman on Helping Organizations Adopt Agile
  • 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!

Reference material by Pavol Vaskovic Posted
  1. Back to top

    Reference material

    by Pavol Vaskovic

    David, thanks for this interview. I use it as a reference material to explain, why we are doing this Agile thing.

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.