How Big Tech Runs Tech Projects and the Curious Absence of Scrum
Central idea
Project process is an enabler, not the goal; capable teams execute through autonomy, clear ownership, direct communication, and strong tooling.
Summary
There is no universally best project-management method. The right amount of structure depends on the team’s maturity, environment, and problem. In many large technology companies, engineers lead team-level projects and teams choose their own working method. Product managers keep attention on the right problem, while the engineering lead and team own execution. Technical Program Managers become valuable when coordination spans many teams, time zones, or external commitments. This model works because it is supported by clear team missions, transparency, strong developer tooling, business context, and people trusted to solve problems—not merely complete assigned tasks. Copying the absence of Scrum without copying those conditions is cargo culting.
Key ideas
Context chooses the process
Scrum, Kanban, a lightweight plan-build-ship loop, or no named method can each work when matched to the team’s needs.
Engineers lead execution
Rotating project leadership develops senior engineers while preserving direct engineer-to-engineer communication.
Scale coordination deliberately
Team projects need little ceremony; complex cross-organization programs may justify dedicated TPM leadership.
Choose by coordination scale
One team: engineer-led, lightweight execution.
Several teams: explicit dependencies and a clear program lead.
Strategic or external program: dedicated program management where coordination is full-time work.
Why it matters now
As AI reduces the cost of producing code, execution quality depends even more on autonomy, fast information flow, clear ownership, and the ability to adapt process to context.
Continue with the original
This short version preserves the main argument. Follow the source for the complete talk, article, or book.