> 1. If the people on the team can't change the process, it ain't agile Absolutely. > 2. Sprints aren't a failure of agile, they're a failure of devops. I do

> 1. If the people on the team can't change the process, it ain't agile Absolutely. > 2. Sprints aren't a failure of agile, they're a failure of devops. I don't think so, here's the timeline: Scrum (90s), Agile (2001), DevOps (2009). So sprints have been around a long time before DevOps, the way I interpret it. > 3. Estimates aren't literally the devil, execs need to have a rough idea how big it is, just don't get more granular than months How? Your event horizon spans only the next couple of iterations, everything beyond that is pure speculation.