Project Management

The Principles Behind Disciplined Agile

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

About this Blog

RSS

Recent Posts

Data Technical Debt: 2022 Data Quality Survey Results

Is Technical Debt A Management Problem? Survey Says...

You Think Your Staff Wants to Go Back to the Office? Think Again.

Contracts, Procurement, Vendors, and Agile

Disciplined Agile 5.4 Released

Categories

#AgileBeyondIT, #ChoiceIsGood, ACP, agile, Agile Alliance, agile-manifesto, book, Business Agility, Certification, Choose your WoW, Conference, Context, Continuous Improvement, contracts, COVID-19, Data Management, database, DDJ, Disciplined Agile, Enterprise Agile, estimation, Fundamentals, Governance, GQM, guesstimation, http://disciplinedagiledelivery.com/principles/be-awesome/, India, information technology, Introduction, Kanban, lean, MANAGEIndia, math, MENA, Metrics, mindset, News, OKRs, Organization, People Management, Planning, PMO, Portfolio Management, Principle, Project Management, Quality, Ranged Estimates, Remote Work, Scrum, Security, skill, software, Surveys, Technical Debt, Technical debt, Terminology, Transformation, value stream, vendor management, VMO

Date



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 (7)

Please login or join to subscribe to this item
avatar
Rami Kaibni
Community Champion
Senior Projects Manager | Field & Marten Associates New Westminster, British Columbia, Canada
Thank you for sharing this Scott, very informative.

avatar
Eduin Fernando Valdes Alvarado Project Manager| F y F Fabricamos Futuro Villavicencio, Meta, Colombia
Thanks for sharing

avatar
Luis Branco CEO| Business Insight, Consultores de Gestão, Ldª Carcavelos, Lisboa, Portugal
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)?

avatar
Scott Ambler Consulting Methodologist| Ambysoft Inc. Toronto, Ontario, Canada
No. You may find this interesting: http://disciplinedagiledelivery.com/defining-mvp/

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

avatar
Ramkrishna Kashyap Project manager PMP,PMI-ACP,PMI-PBA,PMI-RMP,IFMA-CFM, LEED AP BD+C| Prime project international Dubai Thane., Maharashtra., United Arab Emirates
Eight pricipales

avatar
Ramkrishna Kashyap Project manager PMP,PMI-ACP,PMI-PBA,PMI-RMP,IFMA-CFM, LEED AP BD+C| Prime project international Dubai Thane., Maharashtra., United Arab Emirates
why use 7 principlles

avatar
Jon Jorgensen Trainer, Coach, Consultant| Brett Palmer & Associates Mission Viejo, Ca, USA
Why was "Principle: Organize Around Products/Services" from page 24 and pages 31-32 from the Choose Your WoW! book removed from the DA Principles?

Please Login/Register to leave a comment.

ADVERTISEMENTS

"Experience is a comb which nature gives to men when they are bald."

- Chinese Proverb

ADVERTISEMENT

Sponsors