What is Agile?

Agile frameworks have been used for over 20 years in the software development space. Many adaptations have been branded over the years, but none have effectively ventured too far from the software development roots. The basics of agile are typically a framework for delivering a “product” that provides for collaborative adaptation as the effort progresses to delivery of the “product”.

Can ABT help my company?

If you have a project or initiative that exists with a context of continuous change, shifting resource constraints, perpetual delivery delays and/or constant bottlenecks… an adaptive agile framework could likely benefit your organization.

ABT focuses on the outcome, not the plan and allows for shifting among of all the activities between the current state and future state, for optimal ROI on effort.

Traditional vs. ABT

The following chart depicts that of a typical plan to get from current to future state. This depiction is far more simple than most plans, however you can see that every step is an opportunity for a bottleneck. Retooling for the issues/bottlenecks would also require modifying the streams that are flowing as intended; that’s easier said than done, and is often the crux of many initiatives.

Depiction of traditional project plan.

Depiction of traditional project plan.


In ABT, we prioritize and plan for interdependencies of workflow elements, but do not map it out end to end as a “plan”. Leaving this open sets the stage for agility and collaboration.

Depiction of ABT “Plan”

Depiction of ABT “Plan”