Agile transformation: The Low

A few months into any company's journey towards agile development I often see a point which I call the Low. This is where you've brought in a few experts, and done a few of the things they've said... but nothing seems to have improved and now people are wandering round »

Bimodal IT isn't anything to aspire to

Bimodal IT is a term created by analysis form Gartner, to describe an increasingly common pattern in enterprise development. It's where you have one part of the organisation working in a very traditional, governance-focused manner using lots of process charts, documents and explicit signoff, and one part working in a »


What's the difference between a merely good Scrum organisation and a great one? The answer is waste. Waste in a Scrum context is loosely defined as any activity which does not result in something the customer uses. At its most obvious we're talking things like TPS reports and bikeshedding, but »

Be careful with "Modern Agile".

I have a problem with a lot of the recent advice suggesting firms looking to adopt agile practices should eschew the stand-ups, estimations and fixed iterations of Scrum. Which is strange as a lot of that advice is coming from respected, experienced Scrum practitioners. However, I think what's happening is »

Updating the Joel Test for the modern world

Hands up who remembers the Joel Test? It might take some remembering, because it's a shade over 15 years old now - pre-dating the Agile Manifesto. For those of you who don't, Joel's writing on software was some of the earliest, "actually, this software development lark doesn't have to be »

Avoiding nightmare releases

Something I've seen a lot of supposedly Agile teams fail with is releases at the end of a project. Everything up to that point ticks along nicely, but the final sprint is a monstrous combination of time extensions, shifting scope, last-minute changes and unexpected problems. I've seen all sorts of »