Each project is different although the approach is the same: common sense, simplicity and capacity of a team to execute a high level plan i.e. deliver working software. This is a model that can fit some types of projects where governance is important to an organization, where project management is being used and where UX work is key to the launch of a product.

I would highlight again “simplicity”: agile is about making improvement and a good way to identify improvements is to ask yourself: “Can this cost less energy? Can this be reused? Can this be replaced by something that already exist if I change it?”

This picture shows 3 levels of planning, a gated process with review of business cases (yearly budgeting and quarterly funding) as well as quality criteria such as INVEST, DEEP for the product backlog, DoD etc


Big picture