Christopher Justice · Project Management
Agile Was Never Meant for This
Agile emerged when coding was slow and requirements changed. Now coding is instant and change is constant. The original constraints are gone.
# Agile Was Never Meant for This
Agile emerged when coding was slow and requirements changed. Now coding is instant and change is constant. The original constraints are gone.
The Agile Manifesto was written in 2001. Software development looked nothing like it does today. The practices that emerged were rational responses to the constraints of that era.
Those constraints no longer exist in the same way. But the practices persist.
Agile solved real problems:
Waterfall was too rigid. Requirements changed during long development cycles. By the time software shipped, requirements had evolved. Waterfall couldn't adapt.
Feedback was too slow. Months between concept and delivery. Users didn't see working software for ages. Problems weren't caught until late.
Teams were too siloed. Business people wrote requirements. Developers implemented them. Communication was formal and infrequent.
Related articles
- Coordination Overhead Is Killing Your AI Projects
- Heavyweight PM Is Technical Debt
- Your Process Is Optimized for 2015
- Why Your Sprint Velocity Metric Is Lying to You
- The Standup That Could Have Been an Async Update