Re: How to convince my team to do DDD?

From my experience it is hard to enforce the approach from the inside
unless the developers themselves are motivated about it and convinced it is
the right way to do things for the project - YMMV. Also, because DDD can be
interpreted in many different ways the approach is an easy prey for
opposing developers to start useless debates and nitpick arguments during
SCRUM. My experience is that you'll get the better developers interested
quickly, the other might tag along or stick with their ways of doing things.

Jorg

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