Often a mediocre decision made by the team is better than a perfect decision made by a single leader.

Software delivery is a lot like traveling. Less luggage makes for a better experience.

Next time you're facing an unclear feature or epic, ask: Why this? Why now? Why me?

Today I go on record admitting I don't always use TBD, I do sometimes use long-lived branches, and I sometimes even share a branch with another dev.

Two fundamental questions I'd ask any Agile Coach job candidates, if I were hiring.

A group of people with a lot broader experience than I have, come up with a pretty good definition of "Minimum Viable Continuous Delivery".

Everyone and their mother is talking about Kubernetes, but is it right for you?

Continuous Delivery reliably predicts less time spent fixing bugs. How close are you?

The "observation" that fixing a bug in production costs 1000x more than fixing it during design assumes a waterfall approach.

In 2022, I can't think of any legitimate reason that a place of business should need to close for a software upgrade.

Many projects do operate in a non-agile way. What happens to them? Most fail.