Principle: Never Compromise Quality
No one wants to compromise quality, but it happens too frequently! There are two opposing forces in play, which are the reasons for having such a principle in DSDM:
Adaptive projects, because of their exploratory nature, have a risk of becoming chaotic, with poor architecture and low quality. Therefore, practitioners should pay attention to quality and make sure it’s not compromised. The Test‑Driven Development and Refactoring practices in XP are effective mechanisms to overcome this risk and ensure high quality.
DSDM is based on a philosophy that implies a certain approach to project variables where time, cost, and quality are fixed, and scope is dynamic. Having a dynamic scope can reduce pressure: You’re not obligated to deliver everything by the end of the timebox; rather, you just focus on the most important things and deliver only as much as you can with the defined level of quality. This approach makes it easier not to compromise quality.
Written by Nader K. Rad
This is (and will be) a work in progress: More details will be added in the future, depending on the feedback.
This wiki is developed and managed by an accredited trainer, independent of Agile Business Consortium and APMG. While aligned with their guidelines, it’s not an official resource.