"Baseball is a slow-paced, ceremonious game with an inch-thick rule book and a deep layer of historical cruft, does that sound like agile to you?" Sounds like

"Baseball is a slow-paced, ceremonious game with an inch-thick rule book and a deep layer of historical cruft, does that sound like agile to you?" Sounds like agile methodologies; doesn't sound like agile manifesto. Which is kinda the point. The manifesto is a few salient points and heuristics that devs at the time found effective for delivering working software (and which, I would contend, still hold). The methodologies that have arisen are overly prescriptive, adopted without any eye to the culture, and frequently lead to outcomes no better than what they're intended to replace.