Blog

A common complaint on Scrum teams is, “We have too many meetings.” However, I would like to argue that the issue isn’t the number of activities in Scrum; it’s how...

I was just going through my office the other day when I found these wonderful 3.5-inch floppy disks. I know most of you reading this probably have never held one...

Let’s take a look at a couple of different orgs I have had the pleasure to work with and their response to “problems”. I am reminded of my practices in...

A SaaS checkout team and their payments partner invited two long-time customers to be design partners for a new Pay-in-4 API. Week one, they shipped a guarded pilot to a...

This week, we have been exploring real-world scenarios at an organization where I worked; they were a retail provider. While I spent most of my time in the technology operations...

You’ve seen this before, perhaps. On paper, everything looked fine. Our logistics partner was hitting every pickup window; our carriers generally met transit SLAs; the warehouse was definitely locked in...

The Real Problem Isn't Your StandupsAre you working on the organization or in it? This fundamental question drives to the heart of a critical misunderstanding in agile transformation. Hi, my...

Two months before the holiday launch, an electronics company I have worked with held its Thursday portfolio review. Exciting right?Every internal chart looked green; our sprints were on track, test...

In the quarterly review, the dashboard looked triumphant; more features shipped than in any quarter on record. Then I surfaced two quiet charts; customer churn ticked up, support contacts spiked...

Releases kept slipping; the team’s burndowns were fine; the real problem sat in plain sight. Every change waited in a test environment queue that moved slowly, shared across products, with...

Halfway through the quarter, Finance froze hiring to “protect the budget”; the decision hit a critical product just as usage was spiking. Work piled up in analysis; support tickets climbed...

Have you ever had this scenario?Leadership cheered a 25% spike in team velocity, then watched support tickets spike the same week. The team had divided the work into smaller stories...