On Tech

Tag: Antipattern (Page 1 of 2)

End-To-End Testing considered harmful

End-To-End Testing is used by many organisations, but relying on extensive end-to-end tests is fundamentally incompatible with Continuous Delivery. Why is End-To-End Testing so commonplace, and yet so ineffective? How is Continuous Testing a lower cost, higher value testing strategy?

Pipeline antipattern: Artifact Promotion

Promoting artifacts between repositories is a poor man’s metadata Note: this antipattern used to be known as Mutable Binary Location A Continuous Delivery pipeline is an automated representation of the value stream of an organisation, and rules are often codified in a pipeline to reflect the real-world journey of a product increment. This means artifact status as well as artifact content must be tracked as […]

Organisation antipattern: Dual Value Streams

Dual Value Streams conceal transaction and opportunity costs The goal of Continuous Delivery is to optimise cycle time in order to increase product revenues, and cycle time is measured as the average lead time of the value stream from code checkin to production release. This was memorably summarised by Mary and Tom Poppendieck as the Poppendieck Question: “How long would it take your organization to […]

Organisation antipattern: Release Testing

Release Testing is high cost, low value risk management theatre Described by Elisabeth Hendrickson as originating with the misguided belief that “testers test, programmers code, and the separation of the two disciplines is important“, the traditional segregation of development and testing into separate phases has disastrous consequences for product quality and validates Jez Humble’s adage […]

Application antipattern: Serialisation

Serialisation increases batch size and cycle time When designing applications for Continuous Delivery, our goal is to grow an architecture that minimises batch size and facilitates a low cycle time. However, architectural decisions are often local optimisations that value efficiency over effectiveness and compromise our ability to rapidly release software, and a good example is the […]

Pipeline Antipattern: Deployment Build

Continuous Integration “Has A” Continuous Delivery is the wrong way around Eric Minick has written a thought-provoking assessment of Continuous Delivery and Continuous Integration tooling, which includes a variant of The Golden Hammer: “When all you have is a Continuous Integration system, everything looks like a build” This leads to an antipattern Eric and I refer to as […]

« Older posts

© 2021 Steve Smith

Theme by Anders NorénUp ↑