Why our rush to build software faster sacrifices quality and treats software like fast food
In August 2007, I was lucky enough to be able to edit an issue of Better Software Magazine. I was able to choose my authors: Alistair Cockburn, Jim Highsmith, and Jim Shore. I did this because I was lazy – I wanted great articles without a lot of effort. Choosing these authors
In this paper, Heather Williams and Andrew Furguson describe performing lightweight usability testing electronically with customers over a long distance. It’s a minor point of a strong paper that gives great tactical advice for UCD practitioners working on Agile projects. Read the UCD perspective
Why user experience people need to roll up their sleeves and get their hands dirty in development to get the best results.
Why requirements in software development harm collaboration, stunt innovation, and threaten the quality of our products.
“Software development has been steered wrong by the word ‘requirement,’ defined in the dictionary as something mandatory or obligatory. The word carries a connotation of absolutism and permanence – inhibitors to embracing change. And, the word ‘requirement’ is just plain wrong.” I wish I