Quite simply this comes down to business users not wanting to know how the sausage is made after all. They want their food cooked fast, but don't really care ho

Quite simply this comes down to business users not wanting to know how the sausage is made after all. They want their food cooked fast, but don't really care how. We manage 2 different conversations at all times (agile and waterfall): Internally, the Chefs in the kitchen agree on Mise en Place practices, prep time, and have strong confidence then can run 100% regression tests and deploy at anytime. The overhead of TDD, technical debt (sharpening the knives), and retrospectives are kept internal. Externally, the customers don't care about the ingredients or process. We encourage business users to take the waterfall view, think through their requirements, discuss menu options, set delivery dates and formal acceptance testing criteria. It's not that development teams aren't doing agile. But the Agile Manifesto's ideal that Developers and Product Owners would all sit down and speak the same language turned out to be less than practical.