Blog

Someone on my team sent me a long note last week. Real gaps. Product issues, process issues, friction with a colleague.

I have held a version of this as a rule for some time. If an operator cannot leave for ninety days, they may have built a demanding job for themselves.

"Busy" might be the most socially acceptable answer we have invented. How are things? Busy. Why didn't this move? Too much going on. Why haven't you started?

Scrum is useful when the work is uncertain and a capable team can turn short cycles into evidence.

From the Patanjali Yoga Sutras, Sutra 2.03 avidyā-asmitā-rāga-dveṣa-abhiniveśāḥ kleśāḥ Five distortions. But not five independent problems.

Health is not the opposite of smart. It is the transmission. From the Architect, 09 August 2026.

My Scrum blog then said, "Scrum exposes problems. It does not solve them." I still think this is one of the most useful things I wrote about the framework.

From the Architect, 8 August 2026 The alarm is faster than the assessment. Not two problems. One sequence, running in the wrong order.

The DLMx Protocol examines how work moves from intent to outcome through doing capacity, leadership clarity, management discipline, and multipliers.

A backlog can make a team look certain long before the team has earned certainty. The list is long. The items are estimated. Priorities are numbered.

Four people can look at the same work and declare it done for four different reasons. The developer says it works. Operations says it has been released.

I no longer see Scrum as the answer to how work should be done.

Scrum was once an important part of my public identity. I read it, practiced it, blogged about it, and eventually wrote a book about it.