I think scrum and all agile frameworks are trying to solve two problems. 1) Making good software efficiently 2) How can stakeholders get a better sense of how

I think scrum and all agile frameworks are trying to solve two problems. 1) Making good software efficiently 2) How can stakeholders get a better sense of how much work a team can do per unit of time I don't think scrum offers anything in the first department that "Hey, don't do waterfall" doesn't. I don't think this advice needs a capital "Agile" or Scrum though. It's pretty obvious nowadays. As for the second gaol, I don't think it offers much either beyond the advice "Hey, speak up if you encounter a blocker and think it's going to take longer." Again, I don't think that deserves a capital Agile / Scrum. Has anyone actually been on a team where you nailed down your velocity and this truly helped anyone? I think a good process is Design <-> Iterate -> Ship, have a real quick standup to identify problems early and often and then report back to stakeholders. Just pull tickets Kanban style. Have a retrospective once a month or so. Doesn't deserve or need to be a whole religion.