Sustainable Cultural Agile Release in the Enterprise (SCARE) assumes that a group is in the development stage of a project. Rather than a prescriptive approach that requires developers and other team members to make major changes, SCARE uses the theory of constraints to boost Agile productivity. The SCARE framework helps teams identify the change that will be most effectual and implement it. The simplest plan is to find the largest delay or the largest dependency, and make it the focus of Agile team building for a high-functioning group.
Excelon Development created the SCARE method to improve large projects and programs. SCARE doesn't require any HR changes, new processes or methods outside the capability of the individuals doing the work.
SCARE method pros and cons
As happened with the Agile Manifesto, the consultants who created the SCARE method derived it from practice, from looking at what they did that worked, and codifying those concepts with names.
To improve Agile productivity, a SCARE implementation requires real change, potentially across team lines and in the form of staff reorganization. People involved in that change could fear and fight it. There is also no end state or Gantt chart for SCARE adopters. The SCARE approach promises continual improvement that is faster and cheaper than alternatives, with less risk, but without a prescriptive route to get there.