Software Development Process Does Not Matter

Process interests me. Refining and improving a process to make work more joyful and productive matters to me. But, what has become clear over the past thirty years is that in software development, process just doesn’t matter. Seriously. It doesn’t. It might just be because I’m becoming a software punk revolutionary, but I suspect not.Continue reading “Software Development Process Does Not Matter”

The Universal Truth of Collections

The BBC has been running a series called Secrets of the Museum, which features a behind the scenes look at the Victoria and Albert Museum in London. The longer I watched this fascinating show, the more it revealed one of the universal truths of humanity; it’s propensity to collect things and it’s inability to limitContinue reading “The Universal Truth of Collections”

Manager vs Individual Contributor vs Lubricator

You can’t have been following leadership literature for very long if you haven’t heard of manager time vs individual contributor time. The general concept is that individual contributors need some big chunks of time to get stuff done, and managers (partly to protect these big chunks for their team) work in small fragments of time.Continue reading “Manager vs Individual Contributor vs Lubricator”

Budgets Not Estimates

This is an early view over a process we are experimenting with in my organisation; budgets not estimates. It represents a re-ordering of components in the planning process that generates more options and reduces single-option big bets. There are lots of different terms for how people plan software, but very often it involves someone turningContinue reading “Budgets Not Estimates”

Why Devs (Should) Understand Estimates

Yes, this is a sub-post! A reaction to a post titled “Why Devs (Should) Like Estimates”. I try not to get involved in industry conversations about estimation (or, indeed, #NoEstimates) as it can get very dicey at a general level in ways that simply don’t occur for a specific team or organisation. I’ll briefly qualifyContinue reading “Why Devs (Should) Understand Estimates”

The DITE Cycle: Data Insight Theory Experiment

This is not my idea, though I’ve named it the DITE cycle in opposition to other available alternatives. There are lots of organisations and individuals doing something along these lines and they all give it different names. There are echoes of The Lean Startup, flashes of Spotify’s DIBBs, the velvety touch of Impact Mapping, andContinue reading “The DITE Cycle: Data Insight Theory Experiment”

The Disheartening Early Phase of Cycle Times

Whenever I implement cycle-time as a metric, I have to explain that there is a slightly disheartening early phase to the collection of this information. Over the first couple of days, your cycle time will look awesome, but then it gets progressively worse. This can sometimes shock a team, because staring at a graph sometimesContinue reading “The Disheartening Early Phase of Cycle Times”