Correct, in error, appropriate, or inappropriate? How are you going to know?
Today a colleague sent the following email:
I found this cute little diagram of the design process. Any comments?
I limited my reply to:
Assumes that there is a “correct” functionality that can be completely specified in advance, and that any deviation from that complete specification is an “error”
I prefer to release small increments of functionality and get customer feedback; it’s hard to know if functionality is “appropriate” or “inappropriate” until customers are using it
This doesn’t mean you can put broken functionality in front of a customer. But it means that you’re not going to know whether the functionality you build really meets the customer’s need until they start using it.
I have no idea where my colleague got the diagram, so I can’t give appropriate credit. Sorry.
Comments
You can email me at geeks#stephen.viles.geek.nz (change # to @).
Articles
- Producing CSV files from Java for French and German
- New York City travel tips
- Introduction to Java web applications
- Removing line noise with a user style sheet
- A pattern for scripts that update data
- Moving from Blogger to nanoc
- What's the problem we're trying to solve?
- Hibernate trap: Do not directly access fields in another entity instance
- Comparing XML using line-oriented diff tools
- Correct, in error, appropriate, or inappropriate? How are you going to know?
Copyright © Stephen Viles. You can share or adapt this material under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 New Zealand license. This site is built with nanoc and hosted by NearlyFreeSpeech.NET.