Resource Dependency Constraint
Scenario 1:
Full time allocated Engineers and Domain Champions - Scrum
Scenario 2:
Part time contributors, strategic allocation for delivery phases - Hybrid - Kanban post month 4
Use case complexity Constraints
Scenario 1:
Isolated use cases, no risk of prolonged duplicated systems for ops - UAT, Parallel run, Go live and Cut over spreaded in Migration Epics
Scenario 2:
Interdependent use cases - major Roll out during Validation phase - breaking the work into Product/Business related use cases (Particular set of apps, data and vendors enabling certain product stack backed by dedicated support lines and finops)
Scenario 3:
Full interdependency (e.g. FinOps might end in situation invoicing from 2 data sources for 2+ months) - War room roll out, increased intensity in UAT