Business people and technical experts often develop their own jargons on a project, leading to a constant requirement for one jargon to be translated into another. This inhibits effective communication and leads to a loss of information with every translation.
Instead of letting different jargons emerge, develop a common language as a basis for a shared understanding of the domain. Use the same names for the same concepts in specifications, code, tests and documentation. Evolve and maintain this language throughout the project to prevent the need for translations.
