Chapter 11
Working with Requirements
In the preceding chapters, we discussed how to understand a domain and its language. We showed you how to find team and context boundaries. Sometimes, this is all that development teams need to jump directly into code. However, usually jumping from scenarios to code is a bit too challenging, and you need to bridge the gap between domain knowledge and requirements. We will show you how to derive requirements from domain stories so that you can discuss priorities and viable products.
This chapter is for you in the following cases:
You consider yourself one of the following:
Product owner
Product manager ...
Get Domain Storytelling: A Collaborative, Visual, and Agile Way to Build Domain-Driven Software now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
