I often have occasion to describe some very effective ways of doing things. Let me list a few:
Building software incrementally, in two-week cycles, with each increment showing real working features, is a really good way of managing a project.
Creating acceptance tests (or checks), which amount to automated examples of what is wanted, is a really good way of ensuring that requirements are understood,...read more
There’s a lot of interesting talk and thinking, going on under the heading of #NoEstimates. Woody Zuill and Neil Killick are two of the most vocal proponents. The basic idea, as I...read more
In the book “Zen and the Art of Motorcycle Maintenance”, Robert Pirsig’s protagonist, “Phaedrus” is exploring the idea of Quality. At one point he reaches the statement: “Quality...read more
My esteemed colleague and sometime nemesis Michael Bolton has written a screed against the terms “manual testing” and “automated testing”. Check it out, sapiently.
Kate met Dan Devlin at the coffee shop on Main Street where he had originally recruited her. They shared the lovely weather and caught up to date on their lives. But Dan had a question.
A few minutes before 9, the team was in the coffee room.
“What time’s the meeting?” said Gil. “Is she here?”
“Nine sharp,” said Susan. “I...read more
Alan Shalloway blogged on “Big Change Up Front”, suggesting that it’s not always the best thing to do. This made me think …
Alan’s blog makes the point...read more
“Why don’t you believe in testing?” said Lanette Creamer, the Testy Redhead. Ah, but I do. I care about what, when, and at which end of the horse.
It’s really...read more
An odd article by Trent Nix on “LearnTFS” purports to debunk Agile by moving closer to waterfall. Interesting, but not quite right.
Trent Nix, in this article, suggests...read more
I’ve had the privilege of observing He Jinbao, a martial arts master. He doesn’t hurry. Maybe we shouldn’t either.
My T’ai Chi instructor, Richard Miller, studies...read more