I was browsing the web, searching for new ideas to help out fellow manager with some improvements he was willing to do. I went through TTD, pair programming, continuous integration, collective ownership and others. Basically, through the XP practices I knew or used. ( I have to say that every time I do study like this, I learn that I still have to learn. This was the case again.) I found out, that for a long time I was over-looking something called „metaphors“. I am quite familiar with this term and i can relate to it in many ways, but to be honest, in the agile development, I can not. So what is it?
Here are two definitions I found:
(www.extremeprogramming.org) “System Metaphor is itself a metaphor for a simple design with certain qualities. The most important quality is being able to explain the system design to new people without resorting to dumping huge documents on them. A design should have a structure that helps new people begin contributing quickly. The second quality is a design that makes naming classes and methods consistent. What you name your objects is very important for understanding the overall design of the system and code reuse as well. Being able to guess at what something might be named if it already existed and being right much of the time is a real time saver. Choose a system of names for your objects that everyone can relate to without specific, hard to earn knowledge about the system. „
(Kent Beck, Extreme Programming Explained, p. 179.) “The system metaphor is a story that everyone – customers, programmers, and managers – can tell about how the system works.” or “to give everyone a coherent story within which to work, a story that can easily be shared by the business and technical folks.”
Even though I find it interesting, I am not really sure how can this work in real life and what’s the benefit. Do you have any practical experience with it? Any examples or good advise? Do comment, please! :)