Project Management

The Principles Behind Disciplined Agile

From the Disciplined Agile Applied Blog
This blog explores pragmatic agile and lean strategies for enterprise-class contexts.

About this Blog


Recent Posts

What Project Types Exist?

Disciplined Agile and PMI-ACP?

Getting Started With Disciplined Agile (DA)

How to Improve When You Can't Adopt New Technologies Easily

The Art of Guesstimation: Truisms for Better Estimates

What does it mean to be disciplined? To be disciplined is to do the things that you know are good for you, things that usually require hard work and perseverance. It requires discipline to regularly delight your customers. It takes discipline for teams to become awesome. It requires discipline for leaders to ensure that their people have a safe environment to work in. It takes discipline to recognize that you need to tailor your approach for the context that you face, and to evolve your approach as the situation evolves. It takes discipline to recognize that you are part of a larger organization, that you should do what’s best for the enterprise and not just what’s convenient for you. It requires discipline to evolve and optimize your overall workflow, and it requires discipline to realize that you have many choices regarding how you work and organize yourselves, so you should choose accordingly.

The seven primary principles behind the Disciplined Agile (DA) toolkit are:

  1. Delight Customers. We delight our customers when our products and services not only fulfill their needs and expectations but surpass them.
  2. Be Awesome. Awesome teams are built around motivated individuals who are given the environment and support required to fulfill their objectives.
  3. Pragmatism. Let’s be as effective as we can be, and that may mean we go beyond being just agile.
  4. Context Counts. Every person, every team, and every organization is unique.  Let’s find and evolve an effective strategy given the situation we actually face.
  5. Choice is Good. Different contexts require different strategies. Teams need to be able to own their own process and to experiment to discover what works in practice for them given the situation that they face. Having process options to choose from, and understanding the trade-offs of those options, enables you to home in on better options sooner.
  6. Optimize Flow. Your organization is a complex adaptive system (CAS) of interacting teams and groups that individually evolve continuously and affect each other as they do. To succeed you must ensure that these teams are well aligned, remained well aligned, and better yet improve their alignment over time.
  7. Enterprise Awareness. When people are enterprise aware they are motivated to consider the overall needs of their organization, to ensure that what they’re doing contributes positively to the goals of the organization and not just to the sub-optimal goals of their team.

These principles are complementary to the values and principles captured by the Disciplined Agile Manifesto, an update to the Agile Manifesto for Software Development that extended it to reflect the realities faced by modern enterprises.  The seven principles above have evolved out of the DA Manifesto and have been influenced by both Joshua Kerievsky’s Modern Agile principles and Alistair Cockburn’s Heart of Agile.  

In future blog postings I will explore each value in greater detail.  Stay tuned!

Posted on: September 30, 2019 06:22 AM | Permalink

Comments (4)

Please login or join to subscribe to this item
Thank you for sharing this Scott, very informative.

Interesting perspective and approach on the topic
Thanks for sharing.
Are there any of these principles that may conflict with the Minimum Viable Product (MVP)?

No. You may find this interesting:

I find that about 90% of people, maybe more, use the term MVP improperly.

Please Login/Register to leave a comment.


"Golf is a good walk spoiled."

- Mark Twain