[wpietri]

> The alternative is to just do what makes sense, without calling it anything.

You argue in favor of not calling things things, and then go on to call a lot of things things. You demonstrate why we need to name things: to talk about them more effectively.

What makes sense to one person may not make sense to another. I agree that each team should decide based what's right for them based on the people and the problems. But to do that beyond the trivial, we need to name things.

[righttoolforjob]

Sure you can name things, but there is no agreed upon definition of what scrum or agile means, so don't talk about them. They are useless, unscientific terms.