[quectophoton]

The closest I've found to agile is when a team says they use "extreme programming", but I still find it funny that even EP goes against the "Individuals and interactions over processes and tools", or at least walks a tightrope on whether it's a process or not.

[The_Colonel]

I see people kind of assuming that this agile principle implies there should be no process at all. Do you make that assumption or where does the perceived contradiction come from?

[SideburnsOfDoom]

There is a human tendency for absolutes, black and white, binary, either-or thinking, and it seems to manifest no matter what.

If this is happening here, this is a good example, as the front page of the Agile manifesto is laconically short, 10 lines of text ( https://agilemanifesto.org/ )

And includes the repeated formulation "x over y" - NB this is not "x, instead of y", not "x, not y" And then clarifies with "That is, while there is value in the items on the right, we value the items on the left more."

If people can read an absolute from that, then they can read it anywhere.

[quectophoton]

Yeah, I only remembered the four main lines and was, uh, "pattern matching" with other language stuff.

More or less same mistake as (unfortunately) conflating "I don't like X" with "I dislike X", which also falls into into the black-and-white tendency you mentioned.

[quectophoton]

Now that you point this out, I was actually making that assumption yes. My bad.

In my defense, I forgot about the fine print on the agile manifesto website.