Re: How to convince my team to do DDD?

Does your current development process include domain experts?

If so, you can explain to stakeholders that their business experience is
the most valuable asset in the
project<http://epic.tesio.it/doc/manual/nothing_but_business.html>and
thus encapsulating such experience in a specific, well crafted, piece
of code is a proper approach.
If you do not need domain experts, you probably do not need DDD.

A concrete way to spread the verb of DDD, is to start with a small project
(that is still complex enough to require at least a domain expert) with an
experienced modeler.
Do not improvisate, however, or you will obtain the worse result, with
everybody stating that "DDD does not works!".


My 2 cents.


Giacomo


On Wed, Mar 20, 2013 at 2:07 PM, atle03 <[email protected]> wrote:

> **
>
>
> 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
>
>  
>