FAQ

Narrative-Driven Development (NDD) emphasizes the use of storytelling to model business processes and requirements over time, which helps in gaining a deep understanding of what stakeholders truly need from a software system. Once these narrative-based requirements are established, Domain-Driven Design (DDD) can be effectively applied to design and develop solutions.

DDD’s focus on a detailed domain model ensures that the software created directly corresponds to these business requirements. Although DDD is not primarily a requirements gathering approach, its strategic patterns significantly aid in aligning software designs with business expectations.

No. NDD can be added to any existing process. It’s less about the daily cadence or team organization, and more about changing the way in which requirements are captured. The only change needed is to write narratives prior to breaking down work and include everyone involved.