The Spirit of the Requirement
Comments(7) It's time for software developers to quit doing what we're told and start thinking. We're not robots. We're intelligent individuals who can consider context and produce results beyond the handicapped communication of a formal requirement.
It's the software developer's responsibility to ask questions, listen to the answers, and do whatever it takes to understand the problem and it's symptoms; ultimately capturing the Spirit of the Requirement. The Spirit of the Requirement can be likened to the Spirit of the Law, where the focus is placed on intent; not literal definition.
For example, it's a terrible idea to spend hours styling an Adobe Flex application to match an HTML mock-up. Everyone, including the developer will be disappointed. If the customer wanted HTML, they obviously could have done it themselves. Think. Interpret. Provide value.
This problem is more common than you might think. In fact, if you haven't witnessed similar situations, then chances are that you've unknowingly participated in them. Consider an experience where you had done exactly what was asked of you, yet it wasn't good enough?
It's time we open our eyes, lift our hands from our keyboards, and be more than requirements transcriptionists.