Blog

Designing organisations for responsiveness

Key points:

  1. Set up the organisation to ‘sense’ its environment
  2. Treat internal teams (almost) as external providers
  3. Conway’s Law should shape our organisation design
  4. Promise Theory is a useful approach to organisational agility

IMG_20171002_125459

I have been doing quite a bit of work recently with various organisations to help them develop new capabilities for building and evolving software-rich services. Part of this work involves thinking about the responsibilities of different teams and how these evolve. This blog post captures some thoughts and links on how the more successful organisations arrange themselves for agility and responsiveness.

Continue reading Designing organisations for responsiveness

Continuous Deployment is a niche practice; Continuous Delivery is more fundamental.

Summary: many people confuse continuous deployment (pushing changes to live systems many times per day) with Continuous Delivery (reliable software releases through build, test, and deployment automation). Here is why I think that Continuous Delivery is the more fundamental practice.

(Update 1, 2017-11-02: clarified ‘continuous deployment’ and the on-premises context)

IMG_20170212_124433578

Continue reading Continuous Deployment is a niche practice; Continuous Delivery is more fundamental.

Things I (Don’t) Like About Continuous Delivery – LondonCD meetup June 2017

This is part 4 of a 4-part series of articles based on discussions at the LondonCD meetup group on 12 June 2017. The other posts are linked at the end of this article.

Our 4th Open Space discussion challenged people to identify the things that they don’t like about the Continuous Delivery book: things that don’t work in practice, things that are plain wrong, etc. – a slightly cheeky session!

tl;dr: Jez Humble and Dave Farley – authors of Continuous Delivery – did not get anything wrong in their book but they “did not say enough” about the culture/people aspect of Continuous Delivery. People and culture are tricky – who knew?! 🙂

Continue reading Things I (Don’t) Like About Continuous Delivery – LondonCD meetup June 2017

Continuous Delivery for Legacy/Heritage Systems – LondonCD meetup June 2017

This is part 3 of a 4-part series of articles based on discussions at the LondonCD meetup group on 12 June 2017. The other posts are linked at the end of this article.

Applying the principles and practices of Continuous Delivery for new software is fairly straightforward (at least, until you deal with data and databases). However, existing “legacy” systems that were built without many automated tests and without much concern for repeatable deployments of discrete functionality pose a challenge for moving to Continuous Delivery.

Office Lens 20170612-205923

Continue reading Continuous Delivery for Legacy/Heritage Systems – LondonCD meetup June 2017

Difficulties and Solutions for Continuous Delivery with Databases – LondonCD meetup June 2017

This is part 2 of a 4-part series of articles based on discussions at the LondonCD meetup group on 12 June 2017. The other posts are linked at the end of this article.

Continuous Delivery for web applications is (in 2017) largely a solved problem but where data and databases are concerned, Continuous Delivery becomes more difficult (I have written quite a bit about Continuous Delivery and Databases on the Redgate Simple Talk website – worth a read if you’re interested). In the meetup, we explored some of these challenges and some solutions to Continuous Delivery for databases. (Thanks to Alex Yates of DLM Consultants for his expertise in facilitating the discussion!)

Office Lens 20170612-210029

Continue reading Difficulties and Solutions for Continuous Delivery with Databases – LondonCD meetup June 2017