20.5 Years of XP and Agile (2020)
Agile and Extreme Programming (XP) are revisited here through 20+ years of practice, with developers contrasting the genuine benefits—iterative development, automated testing, refactoring, and closer collaboration—with the fatigue of mandated pair programming and rigid process dogma. Many argue that while core ideas like short feedback loops and CI/CD have become mainstream and valuable, “capital-A Agile” has been co‑opted by bureaucracy, certification industries, and management rituals that add overhead without improving outcomes. The central question is whether agile methods still help teams deliver better software today, or whether flexible, context-specific practices have quietly replaced their branded frameworks.
Pair Programming and XP Practices
- Many found full‑time pairing exhausting, intrusive, or incompatible with their working style; some said they’d quit rather than do it continuously.
- Others reported peak productivity and learning during intense pairing, especially in “teacher/student” mode or when chemistry was good.
- Several noted pairing works best with good culture and voluntary use; forced XP is viewed as arrogant or dogmatic.
- XP is praised for giving concrete guidance on what programmers should do (tests, refactoring, incremental design) rather than only process around coding.
Agile, Scrum, and Misuse
- Common complaint: Scrum and Agile are often applied dogmatically, with “you’re doing it wrong” used to deflect criticism.
- Many describe “rituals” (standups, reviews, sprints) being followed mechanically without clear goals, collaboration, or adaptation.
- Misinterpretation of sprints as fixed deadlines leads to sandbagging, lowball estimates, and perceived slowness.
- Some argue agile itself is sound but has been co‑opted by bureaucracy and consulting; others say it was always about selling services and controlling developers.
- Kanban is seen by some as better aligned with interrupt‑driven work.
Testing, TDD, and Coverage
- Unit tests, refactoring, and test‑aware design are widely seen as major long‑term wins.
- Others argue unit tests are high‑maintenance, often redundant, and less valuable than end‑to‑end tests.
- Debate over “100% coverage”: some see it as harmful extremism; others point out XP texts explicitly say not every method needs a test, focusing instead on confidence.
- Concern that designing for testability can introduce backdoors, performance issues, or testing code leaking into production.
Evolution of Practices and Tooling
- Many practices once considered “radical” (CI, automated builds/tests, refactoring, incremental design, source control) are now mainstream, partly attributed to the broader agile/XP wave.
- Others counter that these existed earlier in “waterfall” or pre‑agile environments; agile did not invent them but may have helped spread them.
Agile Industry and Organizational Dynamics
- Strong criticism of “agile theater”: proliferation of roles (coaches, scrum masters, product owners) without removing real impediments.
- Developers feel overloaded with ceremonies, clerical work, and accountability for delays outside their control.
- Some see agile’s failure as political: bureaucracy adapted the language while subverting the principles, resulting in “WaterScrumFall” and rigid, non‑agile implementations.