The Last Agile Ways Post (And the First of Something New)

After years of writing about agile transformations, frameworks, and methodologies, I’m ready to share something that’s been building in my mind for months: Agile Ways is evolving into Adaptive Ways.

Encapsulation and Orchestration Conquer Dependencies in Agile Development

In the world of software development, dependencies are the silent project killers that can transform an agile methodology into a bureaucratic nightmare. But what if there was a way to tame these complex interconnections and restore the promise of rapid, flexible development?

A Simple Framework for Getting More Done

The Four Pillars of Productivity

True productivity isn’t about doing more things—it’s about achieving meaningful results sustainably. After studying productivity research and best practices, I’ve identified four essential pillars that create a balanced approach to getting important work done.

Forces affecting value delivery

Software delivery is influenced by the interplay of several forces. Some are boosters and others antagonists, these forces simultaneously shape the challenges for development teams. Understanding these dynamics is essential to optimize software delivery processes, reduce time-to-market, and maintain competitive advantage while delivering high-quality products that meet customer needs.

Pursuing objectives

Usually in a business profit maximizing world, chasing (business) objectives is part of a plan: deliver more, faster, and cheaper, … please be more productive!

Bringing agile to the organization

An attempt to a systemic approach for an organization’s successful implementation of agile, leading to new ways of working and a cultural change.

The wheel of agility

It all starts with a need that must be satisfied, a problem that needs solving. So there’s a demand for value that is to be released for consumption.

Sense-making agile

In general, when organizations turn to agile, they’ll pick a method and follow it to (hopefully) understand agile. This is somehow not appropriate as it ignores the fundamentals of why we are opting for agile as well as the operational context of the organization.

Agile approach for release constrained teams

It is common in larger traditional organizations that product and/or service delivery is managed through delivery life cycles (DLC). The release is a constraint imposed upon the delivery system. Agility can be brought into the delivery system through decoupling the release outcome into objectives and focus areas while following simple fundamentals.

Implementing simple agility

I have previously explained Simple Agility and now would like to expand a little about how teams can use these concepts to change their ways of working or just improve the way they work.

Minimum suitable ecosystem for agility

Whatever the intent of an organization when it decides to transition towards agility, its ecosystem needs to be adapted for purpose. Just adopting agile practices without attending to the context and how these interact and impact the ways of working will fail to provide the expected results for the investment on agile.

Having a work acceptance system is important for business agility.

The work intake or acceptance system refers to a well-defined method by which the work is taken over by the technology. It is the bridge between the group of stakeholders defining what to work on and the technology group that will build it.