Is DDD a throwback to BDUF?

I'm new to DDD (Domain-Driven Design), and I like many of it's ideas. But with DDD I need to spend pretty much time analyzing domain, defining entities and value objects, choosing aggregates and defining their boundaries etc. So I wonder - isn't it th开发者_如何学JAVArowback to the BDUF (Big Design Up Front)? Is there some good experience of putting DDD and Agile together?

Um... no.

DDD says what to do your in design - put your domain model at its core and derive the rest from there (that doesn't mean it needs to be complete).

Agile says when to do design - evolve it constantly rather than trying to get it perfectly right before you start coding.

That is no contradiction at all. For example, using DDD with Scrum, you'd choose the most important functionality that can be implemented in 30 days, identify the domain model required for that functionality and implement it based on that model within 30 days. Then you'd choose which functionality now has the highest priority and can be completed in 30 days, extend the domain model to support that functionality, and implement it.