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.

Examining the Declaration of Interdependence

Posted by Deborah Hartmann Preuss on Jun 27, 2006

Sections
Process & Practices,
Architecture & Design
Topics
Agile ,
Leadership ,
Methodologies ,
Teamwork
Tags
Management
At the 2004 Agile Development Conference, a number of project, product, and management experts started working together to answer the question "How would you extend the Manifesto for Agile Software Development to non-software products, project management, and management in general?"  Their answer is a document called "The Declaration of Interdependence", often shortened to DOI on the mailing lists.

Declaration of Interdependence
        Agile and adaptive approaches for linking people, projects and value

We are a community of project leaders that are highly successful at delivering results. To achieve these results:
  • We increase return on investment by making continuous flow of value our focus.

  • We deliver reliable results by engaging customers in frequent interactions and shared ownership.

  • We expect uncertainty and manage for it through iterations, anticipation, and adaptation.

  • We unleash creativity and innovation by recognizing that individuals are the ultimate source of value, and creating an environment where they can make a difference.

  • We boost performance through group accountability for results and shared responsibility for team effectiveness.

  • We improve effectiveness and reliability through situationally specific strategies, processes and practices.
©2005 David Anderson, Sanjiv Augustine, Christopher Avery, Alistair Cockburn, Mike Cohn, Doug DeCarlo, Donna Fitzgerald, Jim Highsmith, Ole Jepsen, Lowell Lindstrom, Todd Little, Kent McDonald, Pollyanna Pixton, Preston Smith and Robert Wysocki.

The group creating the document included two of the original Agile Manifesto authors (Jim Highsmith and Alistair Cockburn); noted authors in product management (Preston Smith), project management (Robert Wysocki), and teamwork (Chris Avery); plus others in industry and consulting from both Europe and the US (David Anderson, Sanjiv Augustine, Mike Cohn, Doug DeCarlo, Donna Fitzgerald, Ole Jepsen, Lowell Lindstrom, Todd Little, Kent McDonald, and Pollyanna Pixton).  It's appearance seemed to coincide with the creation of the Agile Project Leadership Network (APLN), whose board boasts many of these same luminaries, and which provides discussion boards for this and other subjects.

June's edition of Better Software Magazine , put out by the StickyMinds people, declares "Declaration of Interdependence" in bold letters. The related article by Alistair Cockburn relates the history of the DOI and examines its six principles, focusing on ways in which its wording may surprise readers. He also looks at the benefits the DOI can bring to the organization that applies it.

Alistair Cockburn, PhD, is internationally known for his work on use cases, project management, and agile methodologies. He has written four books and dozens of articles based on more than thirty years of experience an continues to provide leadership within the Agile Software Development community.
  • This article is part of a featured topic series on Agile

No comments

Watch Thread Reply

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.