There are times when customers are not prepared to talk about their problems in a theoretical way. They are reluctant to generate ideas during abstract discussions but seem to open up better after seeing something tangible in front of them. In such cases, mockups and prototypes become the main means for requirements elicitation and validation processes.
We will discuss what kind of beast the "mockup-driven development" is and which opportunities this approach provides in a BAs work with both our customers and technical team members.
Moreover, you will learn how to use this approach wisely - we will talk about possible traps to keep an eye on and agreements to be made with the team beforehand to avoid painful issues in future.