Why Tech Giants Are Ditching Scrum: The Rise of Flexible Development Practices

Scrum Masters’ Mass Exodus

Data shows that in the first half of 2023, over 120,000 tech workers were laid off, with Agile coaches and Scrum Masters among the most affected, indicating companies are questioning the value of these roles.

Reality at Tech Giants

Most engineers at leading companies such as Google, Netflix, Facebook, and WhatsApp have never used Scrum; they avoid daily stand‑ups and story‑point estimation, opting for other methods.

Methods Adopted by Tech Giants

Research and interviews reveal several alternative approaches:

1. “No Formal Methodology” Model

Many public‑tech and VC‑backed firms operate without a rigid framework, focusing on hiring top talent, clear goals, and rapid delivery without bureaucratic processes.

Recruit elite talent and trust their problem‑solving abilities.

Set clear objectives rather than detailed procedures.

Deliver quickly without excessive ceremony.

A former Facebook product manager notes that he never created tickets or sprints; product managers concentrate on partnerships, strategy, and vision, while engineers own task design.

2. OKR Over Sprints

Empowered teams prioritize Objectives and Key Results (OKRs) and KPIs over strict Scrum cycles, asking “What do we aim to achieve this quarter?” instead of “What can we deliver this sprint?”

3. Plan‑Build‑Deliver

Tech companies often follow a simple “plan, build, deliver, repeat” loop, emphasizing delivery without unnecessary rituals.

4. Shape Up Methodology

Some VC‑backed firms use Basecamp’s Shape Up, a six‑week cycle with cooldown periods, offering a more flexible alternative to Scrum.

Why Tech Giants Never Needed Scrum

Highly capable, self‑sufficient individuals require less organizational overhead; founders who are engineers (e.g., Google, Facebook) naturally communicate without formal frameworks.

Is Agile Still Popular?

According to the 17th State of Agile report, 71% of respondents still use agile methods, but many are customizing or blending frameworks rather than adopting standardized ones like SAFe.

The Real Issues with Scrum

Scrum works well for “big‑mix” teams, teams facing stakeholder interference, or organizations lacking engineering understanding, but becomes cumbersome when teams are already knowledgeable and autonomous.

Economic Considerations of Agile Roles

In a tight economy, few companies can afford full‑time salaries for Agile experts comparable to engineers, leading to cuts of meeting‑facilitating roles.

What This Means for the Industry

Agile principles remain valuable for collaboration and feedback.

Companies are shedding ineffective rituals while keeping what works.

The shift is from “doing agile” to “being agile,” fostering autonomous, experimental cultures.

Tools Reveal the Truth

JIRA receives overwhelmingly negative feedback; a survey of 13 tech companies shows a Net Promoter Score of –83, with 83% of engineers advising against its use.

What Should You Do?

Agile coaches and Scrum leads should move beyond memorizing the Scrum Guide, focusing on facilitating collaboration without strict frameworks, helping teams align with goals, removing systemic obstacles, and nurturing culture rather than enforcing processes.

Bottom Line

The agile ecosystem is evolving, but its spirit endures; success will come from building self‑directed, creative teams rather than clinging to prescribed ceremonies.