Your development, testing, data migration and more needs to be aligned to how you will deploy and therefore you need to decide this approach very early on - or you may accidentally end up with a big bang deployment.
Once an ERP programme has mobilised there is an eagerness amongst the workstreams to get stuck in to early sprints, requirements captures, design sessions etc. Before long Development, Data and Testing workstreams are formed and begin to consider their respective approaches. It is at this point that you need to have a long hard think about how to deploy this thing! The way you develop the system, the way you build data migration routines, the way you test are all dependent on how it will cutover. It is vital you test interim states created by phased deployments before you get to the end state. If you don’t think about this early enough you could be backed into a corner and faced with a big bang deployment which could cause significant disruption to business operations.
Comments