Category Archives: Continuous Delivery

Continuous Compliance

I work as an independent consultant advising organizations on how to improve their software development practice. This is a very broad theme. It touches on every aspect of software development from design, coding and testing, to organizational structure, leadership and … Continue reading

Posted in Agile Development, Continuous Delivery, DevOps, Effective Practices, Engineering Discipline, Pair Programming | Tagged , , , , | 8 Comments

Perceived Barriers to Trunk Based Development

A friend of mine has recently started work at a new company. She asked me if I’d answer a few questions from their dev team, so here is the second… Q: “Currently at MarketInvoice we use short-lived feature branches that … Continue reading

Posted in Agile Development, Continuous Delivery, Culture, Effective Practices, Feature Branching, Pair Programming, TDD | 3 Comments

CI and the Change Log

I get in to debates about the relative merits of “Continuous Integration (and Delivery)” vs those of “Feature Branching”┬á on a fairly regular basis. A common push-back against CI, from the feature-branchers, is “you can’t maintain a clean change-log”. I … Continue reading

Posted in Agile Development, Continuous Delivery, Continuous Integration, Effective Practices, Feature Branching | 3 Comments

Continuous Integration and Feature Branching

Recently I spoke at the Pipeline Conference in London. I gave a talk on “Optimising Continuous Delivery” to a bunch of people who were self-selected as interested in Continuous Delivery, most of them would already consider themselves CD practitioners, Pipeline … Continue reading

Posted in Agile Development, Continuous Delivery, Continuous Integration, Effective Practices, Feature Branching | 68 Comments

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

Posted in Acceptance Testing, Agile Development, Continuous Delivery, TDD | 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

Posted in Agile Development, Continuous Delivery, Effective Practices, Software Design, TDD | 1 Comment

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

Posted in Agile Development, Continuous Delivery, Culture, Effective Practices | 2 Comments

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

Posted in Agile Development, Continuous Delivery, Effective Practices, External Post | Leave a comment

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

Posted in Agile Development, Continuous Delivery, Culture | Tagged | 1 Comment

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