If you are a manager, analyst or developer with programming skills on the target platform (Java or C#), and would like to learn how, as a team, you should strike a healthy balance between digging into your subject matter and addressing technological issues, this is the course for you!

NOTES:
This course is offered in two forms: one for Java/J2EE; one for C#/.NET. The course will be taught using either Java or .NET tools depending on the preference of the majority of delegates. The purpose of the course is to teach DDD concepts and principles, not tools, so the environment in which the exercises are taught is not critical.



TEAM MENTORING SERVICES:
This Domain Modeling workshop will have a much greater impact on the project if it is followed up with mentoring, to help team members anchor it in their own work, and to help them over the practical obstacles that frustrate, and frequently stop, people doing these things for the first time. Valuable new ideas fail to take hold for lack of some practical detail.

We recommend at least two weeks of hands-on work with the team, starting no more than 2 weeks after the end of the class. A typical ratio is at least one mentor per 10 developers (or one per team, whichever is more).

To get the most out of Eric Evans Domain Driven Design Hands-On Immersion Workshop, you should have basic knowledge of object modeling and design. We encourage non-technical managers and analysts to attend. A mixed class is ideal. To make the code exercises work, we only need half of the attendees to have programming skills on the target platform (Java or C#).

Note: This course is offered in two forms: one for Java/J2EE; one for C#/.Net

You should also have some experience of medium to large-scale software development in a multi-team environment. Familiarity with J2EE, .Net or other framework for large scale application development is also useful.

In this intensive DDD class, each morning is spent in lecture and classroom exercises, and each afternoon in a “lab”, doing hands-on coding projects that reinforce the morning’s lessons. The end of each day is a retrospective discussion bringing out the main points of the day’s experience and relating them to the earlier days and to the participants’ own work.