Pivotal Tracker will shut down

Original Article ↗ Hacker News Discussion ↗

Overall sentiment

  • Many see Tracker’s shutdown as “the end of an era” and express genuine sadness.
  • It’s frequently described as the least-bad or best PM tool they’ve used, especially compared to Jira and Azure DevOps.
  • Some argue all PM tools/to‑do apps are largely interchangeable and low‑moat, so its demise isn’t surprising.

Why Pivotal Tracker Was Liked

  • Praised for simplicity, opinionated design, and staying out of the way.
  • Core concepts like a single prioritized queue (icebox/backlog/current), velocity-based auto‑planning, and a small fixed set of states are seen as powerful and clarifying.
  • Users liked the dense, one‑screen UX, keyboard‑centric flow, and limited customization, which reduced process bloat.
  • It was valued for making tradeoffs visible to stakeholders and improving predictability.

Critiques and Limitations

  • Some found it too rigid: missing states around deployment/user validation, weak higher‑level views for multi‑team coordination, and limited “enterprise” features.
  • A few felt it was overly simplistic once workflows got complex and preferred more customizable tools.

Alternatives and Migration Plans

  • Common suggestions: Linear, Shortcut (with explicit PT importers), GitHub Projects, Trello, Taiga, Basecamp, and various open‑source/self‑hosted tools (e.g., Redmine, OpenProject, Plane, Phorge).
  • Linear and Shortcut are most often cited as spiritual successors; Linear is praised for UX and support, Shortcut for being closer to PT’s model.
  • Concerns that promising tools eventually bloat (often to chase enterprise/VC returns) and add heavy AI features.
  • Some continue to prefer spreadsheets/Google Docs; others list concrete reasons they break down at scale.

Pivotal Culture and Pair Programming

  • Extensive discussion of Pivotal’s pairing/TDD culture: many ex‑users remember it as their most productive and enjoyable period; others found mandatory pairing exhausting or incompatible with their work style.
  • Some current teams still practice daily pairing and report benefits in quality and knowledge sharing.

Business and Open‑Source / Clone Debates

  • Shutdown is broadly attributed to the VMware→Broadcom acquisition chain and Broadcom’s focus on cost-cutting and high-margin products.
  • Several ask for Tracker to be open‑sourced; others debate whether law should require code escrow or open‑sourcing after some time or public funding.
  • Multiple commenters see a business opportunity to build a PT clone; others doubt the long‑term profitability of PM tools or note that if PT were highly profitable it likely wouldn’t be shuttered.