I agree with jonathan. Nice specs are wonderful, but with the house
approach, does someone have a nicely framed copy of the blueprints in
their bedroom?
In the end, all that matters is an effective product. Sometimes we
forget that.
On Oct 16, 2009, at 2:04 PM, jonathan berger wrote:
I can’t think of a good reason not to spec. Can you?
Its important to plan ahead, but specs are artifacts which can easily
diverge from reality as code gets written. Agile processes eschew
specs, instead favoring the following:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
Agile isn't for everyone, but its treated me well so far.
Patrick
twitter: usabilitycounts | uxlosangeles | cooltechjobs
email: [email protected] | blog: http://www.usabilitycounts.com
cell: (562) 508-1750 | office: (562) 612-3346
The last UX books you'll ever need.
________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... [email protected]
Unsubscribe ................ http://www.ixda.org/unsubscribe
List Guidelines ............ http://www.ixda.org/guidelines
List Help .................. http://www.ixda.org/help
