I don't think I've ever been in a company that's used any Agile practice in an iterative fashion, or that's in any way thoughtful about structuring dev work. Ma

I don't think I've ever been in a company that's used any Agile practice in an iterative fashion, or that's in any way thoughtful about structuring dev work. Managers adopt it as an arbitrary template for more compressed work, regardless of how well it fits into 2 weeks or 1-day standup cycles, then usually the same template permeates every other team, making it impossible to design a schedule that's appropriate out-of-sync with any other department or team. So I reduce the scope of my work to what can fit into 2 weeks and that I could have something tangible to speak about every single day, and there's no real feedback cycle engaged without a ton of friction and a raised eyebrow. I have a hard time believing that anything has ever shipped because the team chose Agile; any success determined only by deadlines, budget, and periodic (real) feedback cycles.