2 ms·

Since I started involving myself in more complex application modernization projects, I lean towards Domain-Driven Design. DDD and agile don’t like each other m

Since I started involving myself in more complex application modernization projects, I lean towards Domain-Driven Design. DDD and agile don’t like each other much at all until you’re in the implementation side of software engineering. The discovery and modeling activities are very hard to quantify so reporting tasks and progress is very difficult. So the challenge is to get managers to be flexible in how they manage aspects of application modernization.

dragonwriter 3y ago
> The discovery and modeling activities are very hard to quantify so reporting tasks and progress is very difficult. Agile has nothing to do with things being easy to quantify (except insofar as it is in part a response to the fact that they aren’t, generally, in software development.) Obsession with quantification and detailed estimation is something Agile was a response against (but which has defeated Agile values even in most places that say they are “Agile”.) DDD may be an excuse for (it does not seem to me to actually require) big upfront design, rather than the more fluid minimal units of independent value many approaches in the agile space prefer, but that’s a different issue than quantification.
- ChicagoDave 3y ago
  There’s a practical side that the agile manifesto ignored which has been proven over and over. Management simply refuses any project management that doesn’t have clear goals and reporting mechanisms.