Projects typically consist of a collection of features implemented within a timeframe. A project team is temporarily assembled to complete the set of features within that time frame. When the defined work is complete, the team is disbanded. This process creates several constraints on maximizing value for the customer. First, the temporary nature of

change. Often organizations treat a Transformation (with a capital T) as a project with a start date and an end date, applying an old way of thinking to new ways of working. Imposing Agile is not agile, nor is treating it as a deterministic project. In addition, humans have an evolutionary bias to be averse to loss. Collectively, all of this can ge

The biggest single common impediment to building evolutionary architecture is intractable operations. If developers cannot easily deploy changes, all parts of the feedback cycle are hampered.

Implementing Scrum is revolutionary because the implementation of Scrum requires the creation of new roles (such as Product Owner and Scrum Master), new team structures, new artifacts, new events, and new behaviors. It is unadaptable. The official Scrum Guide states: “Scrum’s roles, events, artifacts, and rules are immutable and although implementi