My Book
-
Recent Posts
Blogroll
Recent Comments
- davef on MSEC – The Modern Software Engineer’s Companion
- vince on MSEC – The Modern Software Engineer’s Companion
- Michael on Continuous Integration and Feature Branching
- davef on Test *Driven* Development
- Trunk Primarily basically based Model – TOP Show HN on Perceived Barriers to Trunk Based Development
Archives
- December 2022
- November 2022
- July 2022
- January 2022
- March 2021
- January 2021
- December 2020
- November 2020
- August 2020
- July 2020
- April 2020
- November 2019
- September 2019
- August 2019
- March 2019
- February 2019
- November 2018
- September 2018
- June 2018
- April 2018
- March 2018
- October 2017
- January 2017
- October 2016
- June 2016
- May 2016
- April 2016
- October 2015
- August 2015
- June 2015
- April 2015
- March 2015
- December 2014
- November 2014
- October 2014
- September 2014
- August 2014
- February 2012
- January 2012
- December 2011
- July 2011
- June 2011
- January 2011
- November 2010
Categories
- Acceptance Testing
- Agile Development
- Blog Housekeeping
- Continuous Delivery
- Continuous Integration
- Culture
- DevOps
- Effective Practices
- Engineering Discipline
- External Post
- Feature Branching
- High Performance Computing
- LMAX
- Microservices
- Pair Programming
- Personal News
- Reactive Systems
- Software Architecture
- Software Design
- Software Engineering
- TDD
- Uncategorized
Meta
Category Archives: Agile Development
Answers to GOTO Cph 2017 Questions
I gave a presentation on my recommended approach to Acceptance Testing today, here at GOTO Copenhagen. You can see an earlier version of this talk, from another conference here. GOTO will be publishing their version soon 😉 I ran out … Continue reading
Mob Rule?
I was at a conference last year where I saw Woody Zuill talking about “Mob Programming”. You can see that talk here A very simple description of Mob programming, for those of you who don’t have time to watch Woody’s … Continue reading
Posted in Agile Development, Culture, Effective Practices
Leave a comment
Test *Driven* Development
Before Test Driven Development (TDD) the only thing that applied a pressure for high-quality in software development was the knowledge, experience and commitment of an individual software developer. After TDD there was something else. High quality in software is widely … Continue reading
Cycle-Time
Motivation is a slippery thing. My favourite example is described by the writer Dan Pink. He tells the true story of a Nursery who, like many Nurseries, had a problem with parents turning up late to collect their children. This … Continue reading
RedGate Webinar Q&A
I recently took part in a Webinar for Database tools vendor Redgate. At the end of the Webinar we ran out of time for some of the questions that people had submitted, so this blog post provides my answers to those … Continue reading
Pair Programming – The Most Extreme XP Practice?
I was an early adopter of Extreme Programming (XP). I read Kent’s book when it was first released in 1999 and, though skeptical of some of the ideas, others resonated very strongly with me. I had been using something like … Continue reading
The Anatomy of an Experimental Organisation
I am a software developer. I see the world from that perspective. In reality though that is only one viewpoint. While it is important that we are effective at delivering software, what really matters is that we are effective at … Continue reading
Test Maintainability
At LMAX, where I worked for a while, they have extensive, world-class, automated acceptance testing. LMAX tests every aspect of their system and this is baked in to their development process. No story is deemed complete unless all acceptance criteria … Continue reading
Posted in Acceptance Testing, Agile Development, Continuous Delivery, LMAX, TDD
Leave a comment
How many test failures are acceptable?
Continuous Delivery is getting a lot of mileage at the moment. It seems to be an idea whose time has come. There was a survey last year that claimed that 66% of companies had a “Strategy for Continuous Delivery”. Not … Continue reading
Incremental Design – Part II
In my earlier blog post on incremental design I suggested that we need to allow for failure. So how do we limit the impact of failure, how do we tell when our design choices don’t work and how do we … Continue reading