All of this content used to be spread over three different blogs at three different domains and it's now been merged into one. Why was it ever three? Because at the time it seemed reasonable that each of them was for a different audiences, and yet over time I've found that the lines between topic areas got blurrier and tended to overlap. So now they're all together in one place.

If you encounter things that seem broken, please let me know and I'll get them fixed.

Browse by topic area:


There's a lot here and if you're not sure where to start, here are some popular starting points. From these, you'll find crosslinks to even more topics. Enjoy!

When we do everything right and it still doesn’t solve the right problem

The Choluteca Bridge, in Honduras, was built in an area known for hurricanes and other strong weather. It was designed to withstand the destructive force of a hurricane so when hurricane Mitch came through later that same year, it was no surprise that the bridge sustained only minor damage. Clearly, it had been designed and implemented well.

Horizontal scaling

When we think of scaling the work, we’re typically thinking of stories that are grouped within features or epics, which might be grouped inside even larger items. This is vertical scaling and is fairly common. There is another type of scaling, which we need to also consider, and that is horizontal.

Book recommendations

I’m often asked for book recommendations on various agile topics. There is no single best book to start with so I’m giving you a bunch of categories to pick from.

Tuckman model of team development

I was once called in to help a team, six months into a three month project. Yes, you read that correctly. It was supposed to be a three month project and after six months they had lots of code but nothing that actually worked, and no end in sight.

Too many branches

Most companies have too many active branches in their code repositories. “Active” meaning we’re doing actual development on them.

Monte Carlo under the covers

Monte Carlo forecasting is the most common form of probabilistic forecasting that we see. It’s compelling because it can provide a highly accurate forecast of when work will be done, with relatively little effort.

Playful learning with LEGO

Last week at Agile Open Canada, I brought out the LEGO again, to illustrate technical practices. While there is so much we can do effectively remotely, there are some things that really do benefit from being together in the same room, and this is one of them.

What is Probabilistic Forecasting?

Do your customers ever ask “When will it be done?” When dealing with the future, there’s almost never an accurate deterministic answer (Tuesday, exactly at 3:45pm) to that question but there is an accurate probabilistic answer (85% chance of completion on or before October 1) and in most cases, it’s a lot easier to calculate than you’d expect.

Test driving prime factors in Go / Testify

This article will show how to “test drive” the prime factors kata in Go with Testify. Testing in Go is built right in, which is great. It’s a very bare-bones implementation though so adding Testify to the mix makes it a lot easier to write your tests.