2 Structured Conversation
This chapter covers
- Example Mapping
- Developing unambiguous terminology
- Using Deliberate Discovery to gain a shared understanding of a user story
- Using structured conversations in a requirements workshop
In this chapter, we are going to peer into the daily work of a software product team to learn more about how they use structured conversations to help them discover what the expected behavior of the next feature should be. We’ll start by describing one of their requirement workshops. This will introduce concepts that you’re not familiar with, but don’t worry, all your questions will be answered later in the chapter.
2.1 Where is my pizza?
The team we will be visiting is developing a pizza delivery management application for a large pizza company. The application will allow clients to track the real-time location of their orders, so they have come up with a fun name for the application: “Where is my pizza?” Some joker on the team noticed that this abbreviates to WIMP – “a weak, cowardly, or ineffectual person” (Merriam-Webster). The rest of the team still know that the product will be awesome.
There are lots of other exciting features too, but for the rest of this book we’ll be considering a client’s ability to modify the delivery address of an order after the order has been submitted.