Definition of done from which source? From scrum.org, it's just the stuff that needs to be done: [https://www.scrum.org/resources/what-definition-done] sometimes it'll be heavy and ISO-9000-ish and sometimes not. It's whatever the team(s) using scrum want it to be. If the DoD is "has tests that validate X", and the tests don't exist or show that X isn't the case, it ain't done.
> But in reality, the Definition of Done doesn’t fix the broken kitchen—it just adds pressure. Scrum’s relentless sprints, rushed planning, and chaotic workflows create an environment where perfection is impossible. The DoD isn’t solving these problems; it’s just pretending they don’t exist.
So rather than worry about the DoD, worry about the burning kitchen. I don't see why this is a problem with DoD. It's a management problem to not allow time in the schedule for work other than coding.
Scrum takes its name from rugby. It is orchestrated chaos. If it's the wrong methology for the org, pick another methodology.
> But in reality, the Definition of Done doesn’t fix the broken kitchen—it just adds pressure. Scrum’s relentless sprints, rushed planning, and chaotic workflows create an environment where perfection is impossible. The DoD isn’t solving these problems; it’s just pretending they don’t exist.
So rather than worry about the DoD, worry about the burning kitchen. I don't see why this is a problem with DoD. It's a management problem to not allow time in the schedule for work other than coding.
Scrum takes its name from rugby. It is orchestrated chaos. If it's the wrong methology for the org, pick another methodology.