Project Management

Disciplined Agile

by , , , , , , , , ,
This blog contains details about various aspects of PMI's Disciplined Agile (DA) tool kit, including new and upcoming topics.

About this Blog


View Posts By:

Scott Ambler
Glen Little
Mark Lines
Valentin Mocanu
Daniel Gagnon
Michael Richardson
Joshua Barnes
Kashmir Birk
Klaus Boedker
Mike Griffiths

Recent Posts

Disciplined Agile: An Executive's Starting Point

Using Lean Agile Procurement (LAP) in complex procurement situations

Vendor Management in the Disciplined Agile Enterprise

Asset Management: What Types of Assets Might You Manage?

PMI and Disciplined Agile at Agile20Reflect

Updating the Disciplined Agile Manifesto

Categories: Manifesto


We have recently posted an update to The Disciplined Agile Manifesto.  In particular, we simplified the wording of the three principles (reduce technical debt, visualize workflow, multi-modal organizations) that we added to extend the original Manifesto for Agile Software Development.  We describe the updates to each of the three principles, and our thinking behind them, below.


Reduce Technical Debt

Original: #13. Leverage and evolve the assets within your organizational ecosystem, and collaborate with the people responsible for those assets to do so.

Update: #13. Leverage and evolve the assets within your enterprise, collaborating with the people responsible for those assets to do so.

The primary change here is the use of the term enterprise instead of organizational ecosystem. Over the years we had several people point out that they weren’t comfortable with that term or that they found it overly complex.


Visualize Workflow

Original: #14. Visualize workflow to help achieve a smooth flow of delivery while keeping work in progress to a minimum.

Update: #14. Visualize work to produce a smooth delivery flow and keep work-in-progress (WIP) to a minimum.

This principle was reworded to make it more action oriented and to clearly point out the term WIP.


Multi-Modal Organizations

Original: #15. The organizational ecosystem must evolve to reflect and enhance the efforts of agile teams, yet be sufficiently flexible to still support non-agile or hybrid teams.

Update: #15. Evolve the enterprise to support agile, non-agile, and hybrid teams.

As you can see we simplified this principle greatly, using enterprise instead of organizational ecosystem as above and going straight to the point of supporting multiple ways of working.

Posted by Scott Ambler on: October 01, 2016 07:24 AM | Permalink | Comments (0)

Extending the Agile Manifesto

Categories: Manifesto, mindset

We have just published a Disciplined Agile Manifesto, an extension to the original Agile Manifesto.

Why have we done this? Since 2001 we’ve applied the ideas captured in the Agile Manifesto and have learned from our experiences doing so.  What we’ve learned has motivated us to suggest changes to the manifesto to reflect the enterprise situations in which we have applied agile and lean strategies.  Because the original authors of the Agile Manifesto have made it clear that they intend to keep their Manifesto static we have decided to move forward on our own with this extension.

We believe that the changes we’re suggesting are straightforward:

  1. Where the original manifesto focused on software development, a term which too many people have understood to mean only software development, the DA toolkit suggests that we should focus on solution delivery.  In short, we prefer solutions over software.
  2. Where the original focused on customers, a word that for too many people appears to imply only end users, the DA toolkit suggests that it focus on the full range of stakeholders instead.  We prefer stakeholders over customers.
  3. Where the original manifesto talked about projects, we believe it is more accurate to talk about teams.  As a result we replaced the word project with team throughout the principles.
  4. Where the original manifesto focused on development teams, the DA toolkit suggests that the overall IT ecosystem and its improvement be explicitly taken into consideration.
  5. The original manifesto focused on the understanding of, and observations about, software development at the time.  Since then there has been some very interesting work done within the lean community since then (and to be fair there was very interesting work done within that community long before the Agile Manifesto was written).  This manifesto incorporates lean principles, in particular considering the whole, visualizing workflow, and minimizing work in progress (WIP).

For earlier versions of the Disciplined Agile Manifesto, see Reworking the Agile Manifesto on IBM Developerworks and the book Choose Your WoW!


Posted by Scott Ambler on: April 10, 2014 08:39 AM | Permalink | Comments (0)

There are two ways of spreading light: to be the candle or the mirror that reflects it.

- Edith Wharton