Designing Your Own Delivery Process
Breaking Free from Prescriptive Agile: A Case for Designing Your Own Delivery ProcessAgile is everywhere. It’s become a buzzword that infiltrates almost every team meeting, strategy session, or project kick-off across industries. But somewhere along the way, "being Agile" has morphed into a rigid adherence to specific frameworks like Scrum, SAFe (Scaled Agile Framework), or Kanban. People often talk about these methodologies like they’re sacred texts, leaving little room for adapting processes t
Agile is everywhere. It’s become a buzzword that infiltrates almost every team meeting, strategy session, or project kick-off across industries. But somewhere along the way, "being Agile" has morphed into a rigid adherence to specific frameworks like Scrum, SAFe (Scaled Agile Framework), or Kanban. People often talk about these methodologies like they’re sacred texts, leaving little room for adapting processes to meet the specific needs of a team or project.
However, Agile doesn’t have to be prescriptive. In fact, it shouldn’t be. The whole point of Agile is to be, well, agile — flexible, responsive, and adaptable.
Members only
Keep reading for $2 / month.
The rest of this essay — along with every other members-only post, playbook, and working note — is behind a small paywall. Cancel anytime.
Payment handled by Stripe. Card details never touch this site.