Agilish — What It Means and Why It Exists

ag·il·ish

/ˈajəliSH/

adjective

  1. Able to apply Agile values and principles to execute a plan quickly and easily.
    "The team worked in an Agilish way to meet their deadline in spite of unplanned obstacles."

  2. Relating to or denoting a method of project management characterized by the division of tasks into short phases of work and frequent reassessment and adaptation of plans.
    "Agilish methods apply Agile concepts to different types and sizes of projects."

The World Agile Assumes

The Agile Manifesto was written in 2001 by seventeen practitioners who believed — rightly — that there was a better way to build software. The values and principles they articulated have stood the test of time. Incremental delivery, collaboration, responding to change, working software over documentation — these ideas work. The evidence is overwhelming.

But the Agile Manifesto was not written with a Program Management Office in the room. It was not written with a heavily regulated industry in mind. And it was not written for the reality that many of us work in every day — large organizations with established processes, compliance requirements, governance frameworks, and stakeholders who have been doing things a certain way for a very long time.

The PMO Challenge

A Program Management Office exists for legitimate reasons. In large organizations, PMOs provide structure, oversight, and accountability. They track budgets, manage risk, ensure compliance, and give leadership visibility across a complex portfolio of work. These are not bad goals.

But PMOs are typically built around a Waterfall model of the world — one where projects have defined phases, fixed scope, detailed upfront plans, formal stage gates, and documented sign-offs at every milestone. The assumption is that you can know, at the beginning of a project, most of what you will need to know at the end. Requirements are gathered, approved, and locked. Budgets are set against those requirements. Timelines are committed. And then the organization is expected to execute against the plan.

Anyone who has delivered software in the real world knows how that usually goes.

Bringing Agile into a PMO environment can feel like trying to fit a round peg into a very square, very well-documented hole. Sprints do not map neatly onto stage gates. Backlogs are not the same as requirements documents. Velocity does not translate directly into a project completion date. And the PMO, quite reasonably from its perspective, needs answers to questions that Agile is not always designed to provide upfront.

The Regulated Industry Challenge

Heavily regulated industries — banking, insurance, healthcare, government — add another layer of complexity on top of all of this. Regulatory frameworks often mandate specific documentation, audit trails, approval workflows, and evidence of testing that must exist before software can be released to production. Change management processes require formal review boards. Releases may need to be scheduled weeks or months in advance.

In these environments, the idea of deploying to production at the end of every sprint is not always realistic. The regulatory infrastructure was not built for it, and changing that infrastructure is not within the power of any single development team. You work within the rules that exist, because the consequences of not doing so — failed audits, regulatory penalties, reputational damage — are real and serious.

None of this means Agile is wrong. It means the environment is complicated, and that complication has to be respected.

Where Agilish Comes From

Agilish is the answer to a simple question: what do you do when you believe in Agile values and principles, but you cannot implement Agile the way the textbook describes it?

You do the best you can, within the structure you are actually working in.

You break work into small increments even if the formal release to production happens at a defined milestone. You deliver to UAT or pre-production environments frequently, getting real feedback from real users before the governance gates open. You hold retrospectives even if nobody calls them that. You collaborate with your business stakeholders continuously even if the requirements document says the scope was locked in January. You respond to what you learn even if the change management process makes it harder than it should be.

You apply Agile values — collaboration, transparency, incremental delivery, continuous improvement — as thoroughly as the environment allows. Not perfectly. But purposefully.

That is Agilish. It is not a compromise of Agile. It is a pragmatic application of Agile thinking in a world that did not ask for it but can still benefit from it. And in my experience, it works. The teams that operate this way consistently outperform the ones that either abandon Agile thinking entirely because the PMO requires Waterfall, or try to force a pure Agile implementation into an environment that is not ready for it.

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

Agilish — Your Get Out of Jail Free Card

Image
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...
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