addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgooglegroupshelp-with-circleimageimagesinstagramFill 1linklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

Getting started with DDD - What does DDD look like in an Agile environment?

Getting started with DDD

Are you trying to get started with DDD? Are you wondering how to integrate the concepts into your current process? Do you want to see what the collaboration looks like? Maybe what pitfalls will might run into?

If so, this is the discussion for you. This discussion is a direct result of the questions from the first Lean Coffee DDD we did earlier this year. Many people were struggling with the core concepts and making heads or tails of what is really DDD, and how can DDD be Agile if it focuses on so much design.

This discussion will be based on our team's experience getting started using DDD and incorporating it into our Scrum-based process. I'll be talking about using Specification by Example as the gateway into DDD as a meaningful context-specific starting point. I won't be talking about DDD tactical patterns, and only a little about the strategic patterns.

I will be talking about the essence of DDD and Specification by Example, and how they can work together to make sure you are building the right product as well as building it right.

Join or login to comment.

  • David R.

    hearing about specific examples from josh was helpful

    September 17, 2013

Our Sponsors

Sign up

Meetup members, Log in