LeadingAgile is Now LiminalArc. Read the Full Announcement

Move beyond isolated AI experiments to build scalable, domain-driven systems with AI-ready architectures.

Enhance valuation and accelerate ROI through due diligence, tech migrations, and strategic restructuring.

Control cloud costs, streamline data, and focus investments on high-value, scalable solutions.

Streamline operations and improve decision-making by aligning your ERP systems with how your business actually works.

Reduce risk and increase resilience by closing the security gaps hiding in your architecture and workflows.

Optimize operations, restructure teams, and modernize technology to maximize the value of digital investments.

Deliver mission-critical software in production-ready increments that create measurable value early.

Reduce risk and complexity with every cycle, turning legacy systems into platforms that can evolve.

The belief that shaped us — and how it evolved into LiminalArc, the natural next step in our journey.

Our team of over 100 experts spans the nation, from consultants and technical architects to product specialists.

We are looking to hire mature, pragmatic consultants who are deeply passionate about meaningful change.

Modular, Over Monolithic

Tom Churchwell Senior Consultant
Reading: Modular, Over Monolithic

There is a natural tension between the predictability an organization needs in order to plan and budget and the adaptability it also needs to accommodate for change and the unknowns. At the outset of a new project, especially if it is using new technologies, there can be an order of magnitude difference between how long we think it will take and what it really ends up taking. This is frustrating and even infuriating for anyone in charge of a budget.

We all do our best to estimate and plan and to nail down as many unknowns as possible. Traditionally, we have used requirements documents, GANTT charts and rigorous sequential processes to iron out the natural fluidity of a project. Change and the unknowns are treated like an enemy and whatever change we cannot control, we oversee with rigorous Change Control Processes and a steadfast commitment to as much of our original plan as we can salvage.

Bridge Out

 

So….Why Agile?

Intentionally or not, our traditional practices are designed to drive change and fluidity out. That may be because we inherited our project management metaphor from construction projects. For decades, we have shaped our software delivery practices as if we were building
a skyscraper and no-one could enter the construction site until after the whole thing was built and we had completed the ribbon cutting ceremony.

Software…and knowledge projects in general…do not suffer such limitations. They more resemble an old farmhouse that grows up room by room, lived in and used throughout construction. Agile encourages modular over monolithic. Adjustments are made like the captain of a sailboat reading the weather and making iterative course corrections all the time. Design is more emergent and pragmatically, the final design may differ significantly from the original plan. The customer and their feedback actually influence the solution approach and THAT, virtually never used to happen with traditional delivery.

When computers were new, the world was changing much slower than it is today. In one human lifetime, we have gone from computers as an anomaly sequestered away in data centers with only a select few users to today’s mobile 24X7 interconnection of most everyone on the planet.

Our world has changed, and as adaptable as people are, our processes have not changed enough to keep up. Agile is an attempt, to help us all rely less on predictability and more on adaptability. It lets us put the customer, and their changing needs at the forefront of design and, done well, relieves some of that tension that has existed between the business & IT.

Next Agile 2016 - Michael Sahota and Olaf Lewitz on Showing Up

Leave a comment

Your email address will not be published. Required fields are marked *

×