How to convince my team to do DDD?
"atle03" <[email protected]>
| Newsgroups | gmane.comp.programming.domain-driven-design |
|---|---|
| Message-ID | <[email protected]> |
Hi all,
I have a clear impression that my team/product could benefit greatly from using DDD, but at the same time I really don't see how I can convince them about this. I am not only thinking of using DDD as a set of patterns for organizing code ("DDD light"), but see DDD more as a behaviour-changing think for the team. For me this means establishing the ubiquitous language, defining bounded contexts, doing collaborative design sessions around the domain model, working with business concepts in code, etc. The dream would be some kind of "awakening" in the team where people see the light and start changing their behaviour.....
Does anyone out there have ideas on how to approach this? Any sources of inspiration I can point team members to? Although the books (Evans, Vernon, Nilsson, ...) are very good, they require some effort to get through, and I find them less suited for convincing "newcomers", especially non-programmers. Other than that, there are few presentations, booklets, videos, articles, etc around.
Regards,
Atle
------------------------------------