The Problem with Agile: Scrum, Jira, and Misinterpretations

The Agile methodology, once a promising approach to software development, has seemingly devolved into something far removed from its original intent. This article delves into the frustrations surrounding the current state of Agile, particularly focusing on the common misapplication of Scrum and the overreliance on tools like Jira.

Agile's Identity Crisis

The speaker laments that the word "Agile" itself has become tainted, almost to the point where even its original proponents avoid it. It's been turned into a "steaming pile of garbage", far from the intended principles. While the speaker continues to use the term for professional reasons (consulting work), what they actually practice bears little resemblance to the common perception of Agile.

The core problem lies in the fact that the essence of Agile – paying attention to each other, working in small iterations – is often lost in the noise of prescribed processes and tools. People complain about Agile while unknowingly describing its fundamental principles.

Scrum: A Lightweight Wrapper Gone Astray

A central critique revolves around Scrum. The speaker sarcastically quips that Scrum would be fine if you removed the sprints, scrum master, product owner, backlog, sprint review, notions of accountability and commitment, and certificates. Essentially, if you strip away all the added complexities, Scrum becomes a relatively harmless, albeit somewhat pointless, framework.

The original Scrum guide, in its simplicity, is considered mostly harmless. The real damage comes from the additions and interpretations layered on top of it over the years. Scrum's core flaw is its lightweight nature, making it easily replaceable. Extreme Programming (XP), for example, functions perfectly well without Scrum.

The speaker emphasizes that Scrum was initially conceived as a wrapper around XP to make it more palatable for management. However, Scrum without XP is ineffective, raising the question of its inherent value.

The Allure of Easy Cheating

One of the reasons for Scrum's widespread adoption is its perceived ease of implementation, or rather, its susceptibility to being implemented poorly. It became synonymous with Agile not because it was inherently superior, but because it was easier to misrepresent. The focus shifted from being Agile to doing Scrum, prioritizing management's comfort over actual agility.

Accountability, Commitment, and the Priesthood of Agile

The speaker criticizes the modern emphasis on accountability and commitment within Scrum, viewing it as a form of corporate pandering driven by the desire to sell more certifications. They equate this language with violence, echoing Bob Marshall's sentiment. These concepts were deliberately removed from early versions of Scrum, only to be reintroduced to appease large corporate clients.

Furthermore, the speaker describes Agile as having become a "priesthood," where practitioners blindly follow rituals without truly understanding their purpose. While acknowledging that some Scrum trainers genuinely understand Agile principles, they often still resort to rote recitation of the Scrum Guide, treating it as scripture.

The frustration stems from seeing knowledgeable individuals promoting something deemed ultimately detrimental to the industry's direction. While recognizing the economic incentives behind Scrum training, the speaker laments the dilution of genuine Agile principles.