The Agile Manifesto and what consultants peddle as "agile" have a surprisingly small overlap.

Did your agile consultant go over outcome over output?

It basically drives home that doing work for the sake of work isn't useful. It's only useful if it's something that produces a desired outcome where that outcome is usually a service or features that customers actually want, but it also bleeds into doing technical things that indirectly let you meet customer requirements faster like having good test coverage, a good release process, etc..

The Agile Manifesto itself is actually a fantastic set of tenets. Unfortunately most people I've talked to who are trying to push 'agile' have neither read it, or have enough experience in software development or projects to understand why it's so insightful.

They do love to straw man waterfall though.

This gave me a good chuckle :)

seconded; thats a summary of everything I strive for

It's from the original Snowbird manifesto: https://agilemanifesto.org/ https://www.theatlantic.com/technology/archive/2017/12/agile...