Development Frameworks: Underlying Principles Trump Specifics, Argues John Cutler

In a recent LinkedIn post, John Cutler explores the common ground and underlying principles shared by various development frameworks, suggesting that the specific methodology chosen often matters less than the core concepts it embodies. Cutler contends that the landscape of development frameworks, including popular options like Scrum and Kanban, has reached a point of “peak commodity,” where the distinctions between them are less significant than commonly perceived.

The central promise of these frameworks, Cutler explains, is to enable teams to manage incoming demand effectively without succumbing to overload, while simultaneously fostering impact and rapid learning. He highlights a shared emphasis on key practices across different methodologies.

“Each, in its own way, encourages back-pressure and reducing work in progress. Each has an approach to ‘stop starting, start finishing.’”

The Common Denominators of Development Frameworks

Cutler breaks down the fundamental elements that unite these diverse development approaches. He points out that whether a team uses Scrum, Kanban, Shape Up, or a custom-built system, they often incorporate principles designed to improve flow and predictability.

Encouraging Throughput and Pace

According to Cutler, a common thread is the establishment of understandable metrics for throughput and pace. These metrics, whether expressed as velocity, flow, or fixed cycles with defined capacity, provide teams with a means to understand and forecast their progress over time.

Leveraging Forcing Functions

Furthermore, Cutler argues that most frameworks utilize “forcing functions” as a catalyst for observability and continuous improvement. These can include timeboxes, work-in-progress (WIP) limits, fixed cycles, or capacity-based planning instead of traditional estimation. He notes that these mechanisms, when coupled with attention and action, drive adaptation.

“Each uses forcing functions—timeboxes, work in progress limits, fixed cycles, appetite instead of estimation, explicit policies for advancing work—as a catalyst for observability and continuous improvement (provided you pay attention and do something about it).”

Inputs, Optionality, and Risk Management

Cutler also observes that frameworks provide structured ways to manage inputs and promote desirable team behaviors. He describes how inputs enter the team’s workflow through backlogs, replenishment cadences, or similar mechanisms. Crucially, these systems offer ways to decline work, enforced by boundaries like sprint limits or WIP caps.

He further elaborates on the techniques employed to foster optionality, encourage self-organization, support replenishment, and surface risks early. Practices such as backlog refinement, work shaping, and early integration are common across many methodologies. As Cutler states:

“More broadly, they help make trade-offs explicit, clarify roles and responsibilities, create shared language, enable feedback loops, enforce cadence and rhythm, and provide mechanisms for adapting over time, including retrospectives, cool-down periods, and circuit breakers.”

The Principle of Convergence

Cutler posits that the convergence of results across different cultures and contexts, despite varied practices, leads to a rational conclusion: the underlying principles are paramount. He suggests that even teams who eschew formal frameworks often adopt similar underlying concepts, albeit without the associated terminology.

To illustrate his point, Cutler draws an analogy to fitness regimens.

“It’s like Zumba, SoulCycle, CrossFit, HIIT, yoga, and Pilates. All of them will get you in shape, but they appeal to very different preferences and personalities.”

In essence, John Cutler’s analysis on LinkedIn suggests that while the specific framework might cater to different preferences and mindsets, the true value lies in the adherence to fundamental principles that drive efficient and effective development, regardless of the chosen label.