Deaf phone - which gives an intriguing and fun to think of childhood, where even a simple "information" may be distorted after passing through a chain of "relays".
cult image of the swing (which we all know) illustrates what happens to the information a bit more sophisticated (eg on requirements) firmware in the production process.
How to prevent this? A reasonable solution is
Ubiquitous Language - the key to the Domain Driven Design involving the manipulation of the common vocabulary cybersquatters at each level of abstraction, ranging from business experts to source code (sic) in the layer of application logic and the logic of domain. The logic of domain, of course, a strict "label" - the use of well-defined Building Blocks.
This leads to the bottom of the post.
encourage you to familiarize yourself with the presentation of my guru - Eric Evans: " Sustainable Design for Agile Teams " during which We study a sample session between the programmer and the expert cybersquatters. Pay attention to well-defined, common language spoken by both parties and how to "discover" new beings.
course, this process is not cheap and requires precious resource: Domain expert: /
//============================= ==============
presentation also addresses another aspect arcyważny Misunderstanding the design domain in the naive approach to Agile. When we focus on a single requirement or a single iteration, then usually there is a special case business process in any domain. We lose "biger pikczer" and eventually all boils down to the happy (unhappy later) "hack" code that describes some special cases - the legacy. And there is nothing to be honest - no one is eager to refactor model of cybersquatting, which is already filled with data in the database:)
