Agile and Scrum transformed software development from rigid waterfall planning (6-18 month projects) to iterative sprints (2-week cycles). The Agile Manifesto (2001) prioritized “individuals and interactions over processes and tools” and “responding to change over following a plan.” Scrum, the most popular Agile framework, became ubiquitous in tech by 2010s, with 70%+ software teams claiming to practice it.

The Scrum Framework

Roles:

• Product Owner: Defines features, prioritizes backlog
• Scrum Master: Facilitates process, removes blockers
• Development Team: 5-9 engineers building features

Ceremonies:

• Sprint Planning: Team commits to work for 2-week sprint
• Daily Stand-up: 15-minute status updates (what I did, what I’m doing, blockers)
• Sprint Review: Demo completed work to stakeholders
• Retrospective: Reflect on process, identify improvements

Artifacts:

• Product Backlog: Prioritized list of features/bugs
• Sprint Backlog: Work committed for current sprint
• Burndown Chart: Track remaining work vs. time

The Appeal

Agile/Scrum promised:

• Faster feedback: Ship every 2 weeks, learn from users
• Flexibility: Reprioritize based on changing needs
• Team ownership: Self-organizing teams, not top-down mandates
• Transparency: Everyone knows what everyone’s working on

The methodology suited startups (iterate fast, validate assumptions) and tech companies (requirements change constantly).

The Reality

By 2020s, #AgileScrum became polarizing:

Critiques:

• Ceremony overload: Stand-ups, planning, review, retro = 6+ hours/week of meetings
• Fake agile: Companies adopted rituals (stand-ups, sprints) without cultural shift (still top-down, blame-driven)
• Velocity obsession: Story points gamed, pressure to commit to more points each sprint
• No long-term thinking: 2-week horizons prevent architectural improvements (technical debt accumulates)

The Backlash (2018-2023)

Critics emerged:

• Ron Jeffries (Agile Manifesto co-author): “Developers should abandon Agile” (corporations corrupted it)
• Shape Up (Basecamp, 2019): Rejected Scrum for 6-week cycles, no estimations, no daily stand-ups
• Asana, Linear: Async-first tools reduced meeting overhead
• “Agile Industrial Complex”: Certified Scrum Masters ($1K-$2K courses), consultants selling frameworks

The Useful Parts

Despite backlash, Agile principles endured:

• Iterative shipping: Better than 18-month waterfall projects
• Retrospectives: Teams actually improving processes (when done well)
• Stand-ups: Valuable for coordination (when kept short)
• Backlog prioritization: Forces hard choices about what matters

Cultural Impact

#AgileScrum normalized:

• Shorter release cycles: Weekly/daily deploys vs. quarterly
• Cross-functional teams: Engineers + designers + PMs working together
• Servant leadership: Scrum Masters as facilitators, not managers
• Fail fast: Iteration over perfection

The movement also spawned parodies: Kanban (visual boards, no sprints), SAFe (Scaled Agile for enterprises, widely mocked), and “Dark Scrum” (oppressive micromanagement disguised as Agile).

References

• Agile Manifesto - Original 2001 document
• Scrum Guide - Official framework (Ken Schwaber, Jeff Sutherland)
• Ron Jeffries: Developers Should Abandon Agile - 2018 essay