It’s time to treat software engineering seriously.

For years, Agile has relied on playful metaphors — tribes, squads, trains, sprints, even pigs and chickens.
These made the frameworks easier to sell, but they also made our profession look less like engineering and more like a playground.

Today our systems run hospitals, railways, satellites, and financial infrastructure.

The language, mindset, and expectations must match that responsibility.

In this second issue of the Agile Software Engineering newsletter, I argue for a shift toward clarity, engineering discipline, and frameworks rooted in Lean, DevOps, and architecture — without losing creativity or innovation.

If you would like to read the full article it is here.