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 som

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..