Perhaps counter intuitively brakes let you drive fast. Without the brakes we would drive really, really slowly. I believe the same is true of automated tests. Something that looks like it should make you go slower actually lets you deliver code faster. As long as you’re doing the right tests.
Continue reading
Author Archives: Steven Thomas
Help! Looking for Topics for “What to do when . . . ?”
I need help. Every month for the last 18 months I’ve been posting something to answer the question What do I do When … ?. People seem to like the format but I’m running out of ideas. I’d appreciate some help finding topics for a new batch of posts in this series. Please drop me a line or add a comment if you’ve got a question you’d like answered or just a suggestion for a topic.
Accuracy vs Precision in Estimation
Which is better: An estimate of “roughly 2 weeks” or an estimate of “4.75 days”? Personally I favour accuracy over precision. “4.75” is attractive because it very precise and a smaller number, but “roughly 2 weeks” might be more accurate. And estimating must be accurate to be any use for planning.
Continue reading
Are you dead? A comfortable Agile Project Manager isn’t doing their job
If no one is pissed off with you then you are dead but just haven’t figured it out yet!
Tom Peters (2004)
Bucking Bronco: Software Projects that Kick
Leading software development often reminds me of what it must be like to ride a bucking bronco … with the added problem you have to go somewhere at the same time.
Continue reading
Declarative vs Imperative Gherkin Scenarios for Cucumber
Everybody I’ve met that is new to Gherkin starts with an Imperative style of scenarios. The Imperative approach is simple and intuitive and reflects what manual testers do. But I hate the Imperative style with a passion. I favour a Declarative style of scenarios not least because a declarative style means I can test business rules. The UI is prone to change but the business rules tend to be more stable.
Continue reading
Developers don’t have time for code reviews and unit tests
The ticket moves to “Dev Done” but there are no unit tests and the code hasn’t been reviewed. When challenged the developer says “That’s because I don’t have time for that stuff”. If I hear that I want to know why they feel they don’t have time, then I give them the time.
Continue reading
Fluid Planning and Execution Creates Agility
Thought leaders in the US military are challenging traditional approaches to command and control. These military innovators are proposing a more fluid approach that allows simultaneous planning and execution. It is good to see they are catching up but as an Agile practitioner I already do fluid planning and execution.
Continue reading
Whose responsibility is testing anyway?
I have a painfully small manual test team, sometimes 1 tester per 15 developers. The answer to the obvious question “who tests?” is “mostly the developers”. Of course this only works if you’re doing extensive automated testing including Specification by Example with a tool such as Cucumber.
Continue reading
Cake Driven Development
I don’t know whether it is me or whether it is just people, but my teams tend to obsess about food. Particularly cake. Food entwines itself in the team culture. And that is why I think it is worth a blog post.
Continue reading