Scrum is broken: The productivity paradox

Bridging Ancient Wisdom and Modern Software Development

This is a breakdown of Pulse Development. We have started with first remote teams and working challenges of scrum. If interested, you can read the first part here.

Here we go…

Many of us have the misconception that the ways we live today have been the norm since the beginning of human history. We often overlook the fact that numerous practices and beliefs that shape our daily lives have only been around for about a century. Norms and daily lives have evolved, adapting to the changing tides of technology, culture, and knowledge.

For instance, 8 hour work day concept is a relatively modern development, primarily established during the industrial revolution to structure the labor force. Our educational system includes schools that train children to be better workers for the industry. Or consider the time zones used in the US, which did not exist before 1883. The necessity of using time zones erupted after the tech advancement of rail roads! These are like an outdated software patch, applied to synchronize the human workforce with the mechanical rhythms of factories.

As we create our truths, we also create our myths. These are mostly unrealistic expectations in project schedule, budget, or quality. One of the strongest myths that is inflated by Scrum is the myth of constant productivity. However, a closer look at our ancestral roots, specifically the hunter-gatherer societies, reveals a rhythm of work that is more attuned to the nature of human beings.

The very first question we should ask from the beginning of time is: Why do people work? As James Suzman also states in this book (Work: A Deep History, from the Stone Age to the Age of Robots) people work mainly to obtain the energy required for our bodies to function. In other words, ancient people had no intention to work if they had enough energy. That is why the hunter-gatherer societies thrived on intermittent work patterns, characterized by bursts of intense activity followed by periods of rest and leisure. This approach was not merely a survival tactic but a well-calibrated strategy that fostered focus, reduced stress, and increased creativity. Their lives were woven into the fabric of immediacy, where work showed direct and tangible outcomes, and the fruits of labor were promptly enjoyed. We can easily see the need, the effort, and the reward in this context.

In contrast, the modern software development, including Scrum, believes in the myth of constant productivity. This misalignment with our intrinsic human nature leads to burnout, low quality of work, and a destruction of the creative spirit.

So, how can we bridge the ancient wisdom of our hunter-gatherer ancestors with modern software development? The key lies in embracing the rhythms of intermittent work and allowing space for rest and slack time. No one can run sprint for 2 weeks or 1 week, not even 2 days. Breaking the work into smaller, manageable chunks can prevent overwhelm and foster a sense of accomplishment. Encouraging breaks and slack time, not as luxuries but as essential components of the work process, can enhance mental clarity and creativity.

Moreover, shifting the focus from story points or the mere number of hours worked to the actual results produced can cultivate an environment where quality is prioritized over quantity. This approach also aligns with our desire for focused and purposeful work.

In conclusion, the path to redefining productivity in software development can be influenced by the lessons from our hunter-gatherer ancestors. By adapting a rhythm of work that resonates with our nature, we can achieve a sustainable productivity. This forces us to reimagine our workspaces, our software development methodologies.