Blog

Thoughts on AI-native Software Engineering, productivity, and building great products.

AI ate Agile for Breakfast

A decade after stepping back from the Lean Agile Scrum (LAS) community, I wanted to speak up again with a bold thesis: AI eats Agile for Breakfast. The conference was cancelled. Three weeks later I'm giving the opening keynote somewhere else – plus a workshop. Even the cancellation proved the thesis.

The right entry into AI-native Software Engineering

Whether the transition to AI-native Software Engineering is successful depends on how developers and management deal with the change and what conclusions they draw for roles, structures, and processes. A small, real-world AI beacon provides the necessary foundation.

Why introducing AI fails

The problem is the entry point: paper over product, rigid processes over responsibility. And the misconception of trying to take everyone along.

AI makes coding easier. Software engineering gets harder.

AI writes code. Engineers build systems. Software engineering gets harder; the engineer’s role shifts.

Stagnation doesn’t come from doubt, but from responsibility

AI has arrived in software engineering. And yet, surprisingly little is happening in many organizations. Many leaders hesitate, not out of skepticism, but out of responsibility.