ADAPT and CONTROLThe governance framework or agile governance model is used in conjunction with a standard Agile processes, such as Scrum. They work in two specific ways:
In the excitement of understanding requirements, selecting stories for development, defining acceptance criteria, building some software, getting feedback from users and regular re-prioritisation its easy to put aside infrastructure and deployment constraints. Putting off these considerations can have an impact on your agility later in a project.
I often hear the complaint that Agile reduces the amount of design possible on a project. The typical scenario cited is that design work has had to be "cut short" because the developers are ready to play the story. I get the image of a nest full of baby birds clamouring for food.
The intent is quote the opposite: Agile should increase the amount of design, but decrease the amount that occurs up-front. This requires a fundamental mindset shift: design is not synonymous with up-front design.
Agile Programme and Project ManagementScaling Agile to large projects demands balance between the ability to be responsive to change with an absolute business requirement for certainty requiring elements of predictive programme management and control.