The Slow, Painful Death of Agile and Jira

Original Article ↗ Hacker News Discussion ↗

Overall sentiment on Jira

  • Many participants say Jira “sucks” but also note that most alternatives are worse or only “less bad.”
  • Criticisms:
    • Sluggish performance, especially in cloud / heavily customized instances.
    • Overly complex UI with many clicks, panels, and slow page loads.
    • Infinite customization encourages bloated workflows and micromanagement.
  • Defenses:
    • Extremely configurable; with an experienced admin/consultant and “just enough” process, it can handle complex workflows few others can.
    • For simple use (bug tracking, basic Kanban, linking to repos), it’s “fine” or even appreciated.
    • Some argue hatred is often misdirected at Jira instead of at bad processes and managers.

Agile vs “Agile™” / Scrum

  • Strong distinction between original Agile Manifesto values and today’s ritualized “Agile” (Scrum, ceremonies, Jira-driven metrics).
  • Common view: current corporate Agile is process-heavy, top‑down, and often functions as formalized micromanagement.
  • Iterative development predates Agile; some say Agile “won” in that sense, others argue true Agile (self‑organizing teams, fewer managers) never really happened.
  • Ceremonies (standups, sprint demos, points) are frequently seen as wasteful, especially when poorly run or detached from real outcomes.

Process, management, and culture

  • Root problem identified as bad management and process accretion, not tools per se:
    • Steps are added after rare failures and never removed.
    • Processes become heavy to avoid blame and litigation rather than to maximize value.
    • Metrics (tickets closed, points) are abused for control and performance ranking.
  • Several note that good teams “think for themselves,” minimize process, and emphasize trust, ownership, and direct communication.

Alternatives and variations

  • Mixed experiences with alternatives: Azure DevOps, ClickUp, Monday, Asana, ServiceNow, Redmine, GitHub Projects, Linear, Trello, FogBugz, etc.; each has its own flaws.
  • Simpler boards and paper cards (XP-style) are praised for fostering communication but are hard to scale and to support remote work.
  • Some teams report success dropping Scrum for Kanban, reducing ceremonies, or tailoring lightweight hybrid approaches.

Unclear / contested points

  • Whether Agile is truly “dying” is disputed; many still see it and Jira everywhere despite mounting criticism.