Knowledge work is the combination of work execution and workflow. Execution usually gets the attention in IT.

Frequently, when I hear someone defending "waterfall", and dig deeper they're actually talking about small-a agile.

So some of the bad KPIs, like lines of code, are easy to detect. But how do we choose a good KPI?

Based on my customer service experience, Transistor.fm is truly agile. Not necissarily "Agile", but agile.

A task I expected would take an hour has taken 10, with no end in sight.

Demos are far from the only way to receive timely feedback.

Ensemble writing would never work... except when it does. All the time!

Many epics are waterfall projects in disguise.

These phrases are designed to end conversations.

If you work in small enough batches, you'll never care if your story is "worth" 8, 3, or 233 points.

It's important to learn to be selective.