> "Agile is great for innovation where there is no deadline and no limited budgets" that rings very true with me. I'm nearing the end of a 3 year project where

> "Agile is great for innovation where there is no deadline and no limited budgets" that rings very true with me. I'm nearing the end of a 3 year project where scrum was prescribed and followed, but the truth is we've basically shoehorned agile practices into a waterfall model because of business needs. My experience with agile projects is probably far removed from how it should be implemented, but it still feels like it's fundamentally flawed to address business needs which rely on fixed scope and accurate estimates from the start of the project succeed (e.g. critical 3rd party tools being end-of-lifed, product mandates beyond company control, renewing client licenses based on feature completion). I guess until something better comes along, I'm stuck with being told to do some strange type of scrumfall/water-gile.