What are the common failure modes in Agile adoption?

Common Agile adoption failures: (1) Cargo Cult Agile — following ceremonies mechanically without understanding principles. Daily Standups become status reports; Sprints become mini-Waterfalls with phases within; (2) Wagile — Waterfall planning (fixed scope, fixed date, fixed team) with Agile reporting (Sprint burndowns). The worst of both worlds; (3) SAFe theater — large PI Planning events with impressive wall coverage but Gantt chart thinking underneath; (4) Product Owner bottleneck — PO unavailable to teams, decisions delayed, backlog not maintained, Sprints miss goals because teams can't get answers; (5) Feature factory — measuring success by features shipped, not outcomes achieved. Teams optimize for velocity, not value; (6) Technical debt accumulation — skipping Definition of Done adherence to "move faster" creates slowing problems; (7) No retrospective action — retrospectives happen but identified improvements are never implemented; (8) Management command-and-control — managers tell Developers what to do rather than enabling self-organization; (9) Unengaged stakeholders — Sprint Reviews with empty rooms; no customer feedback loop; (10) Skipped refinement — Sprint Planning fails because backlog isn't ready, starting Sprints with unclear goals.