Agilish — Your Get Out of Jail Free Card

We do not live in a perfect world. Most of our industry has spent the better part of two decades moving toward Agile adoption, and the case for it has never been stronger. But there are still plenty of clients, managers, and organizations that are comfortable with Waterfall — and either will not or cannot change. You can make your case. You can share the evidence. And sometimes, at the end of the day, you are still doing Waterfall.

This Dilbert sums up the challenge better than I can:

Pick Your Battles

Dale Carnegie famously argued that you cannot win an argument. Even when you are right. Even when you have the data. The moment someone feels they are being argued into a corner, they dig in — and you have lost them, regardless of the facts. The same principle applies to how we work and the methods we use.

Sometimes the smartest thing you can do is let the client or the manager be right. Not because they are, but because the relationship and the work matter more than winning the debate. You are not going to transform an organization's methodology by force of argument in a meeting. Real change takes time, trust, and demonstrated results.

So what do you do in the meantime?

What Agilish Gives You

Agilish is not a methodology. It does not compete with Agile or Waterfall as a framework. Think of it instead as a practical strategy — a way of applying Agile values and thinking inside whatever constraints you are actually working within, rather than the ones you wish you had.

When you are boxed into a Waterfall process — whether by a PMO, a client contract, a regulatory environment, or simply by the culture of the organization — Agilish is your get out of jail free card. You work within the rules that exist. But you work smart.

A Practical Strategy That Works

Here is one approach I have used many times: work ahead wherever possible, deliver early and often to UAT or pre-production environments, and let the Waterfall governance mechanisms take over for the final push to production.

Your team is still doing iterative, incremental work. You are still delivering working software frequently, getting feedback, and catching problems early. You are still applying Agile values where it matters most — in how the team actually works day to day. The Waterfall reporting, sign-offs, and release gates happen on top of that, satisfying the process requirements without strangling the work.

Nobody loses face. The client or manager gets the structure and the paper trail they need. The team gets to work in a way that actually makes sense. And you get to demonstrate what good delivery looks like — which, over time, is the most persuasive argument of all.

You cannot always choose your environment. But you can almost always choose how you work within it.

Popular posts from this blog

The Agilish Method

Combining Agile and Waterfall methodologies into a cohesive approach, we call "Agilish" can be an effective way to deal with individuals and organizatons that struggle with the natural fuzziness of the Agile approach. Agilish offers the flexibility of Agile while accommodating the structured planning of Waterfall. This hybrid approach can help ensure that projects are adaptable while still meeting deadlines effectively. Here are a few tips to successfully implement Agilish: Start with a Clear Vision : Define the end goal and major milestones upfront, much like in Waterfall. This provides a roadmap that guides the Agile sprints. Iterative Planning : Use Agile sprints for iterative development and planning. Regularly review and adjust plans based on progress and feedback. Strong Communication : Maintain open lines of communication between Agile teams and Waterfall stakeholders to ensure alignment and manage expectations. Flexible Prioritization : Allow for dynamic prioritizatio...
Read more

Blind Alleys and the Case for Incremental Delivery

Image
A friend recently shared a fascinating article about a mistake made by some of the greatest scientific minds of the 19th century. For decades, the best mathematicians and astronomers in the world were convinced there was an undiscovered planet — named Vulcan — orbiting between Mercury and the Sun, hidden from view. The math seemed to demand it. The calculations were elegant. The theory was accepted as fact. There was no planet. A Star-Crossed 'Scientific Fact': The Story of Vulcan, Planet That Never Was Two lines from the article stuck with me. The first: "It's easy to forget that there are people behind the data and equations. And when people are involved, there is always room for human error." The second hit even harder: "In science, you don't dwell on the blind alleys... but the blind alleys are most of what science actually does. You have to go down the blind alley, you bang your head against that blank wall at the end of it, come b...
Read more