> measure your results ... The heart of the agile manifesto I suppose That's an interesting one. I don't know if Scrum teams I've been part of are doing this w

> measure your results ... The heart of the agile manifesto I suppose That's an interesting one. I don't know if Scrum teams I've been part of are doing this wrong, but I have seen a shocking lack of measurement going on. Much less than with even waterfall. Whereas with a waterfall approach from decades past one might have a deadline and know if one has hit it or not, or a budget and know if one has overrun or not, the product managers at most Scrum teams I've worked with recently wouldn't be able to tell you what % of time is spent in Scrum ritual meetings, whether the project is overrun or not (as we only plan one sprint ahead, and the project is going to take more than one sprint), what % of time was actually spent on what project in the last sprint (or over the last quarter), what % of time was split between requirements, dev, ops, or any other task, etc. Has your experience with agile been different? Or am I misunderstanding what you mean by measurement?