[snarfy]

> But in terms of the only measurement that really matters—satisfying requirements on time and within budget—I haven’t seen any methodology deliver consistent results.

Good, Fast, Cheap. Pick two.

That's what you are doing when you are pitting requirements, a time frame, and a budget against each other.

The first problem is this is a company wide process, not just software development. The only thing development tells you is how long it will take given the budget. Development doesn't define the requirements or the budget.

The third statement in the Agile Manifesto, which tends to get overlooked:

"Customer collaboration over contract negotiation"

That is entirely a business process and ultimately determines both the requirements and the budget. It is something that is sorely lacking at most companies, regardless of how hard their engineering department tries to follow agile. It doesn't work without the full company buy-in.

[emodendroket]

In many software projects none of those are satisfied.