Finally, the MDM team needs to consider how many environments it maintains. Often, 2 development environments are required. One is a replica of production, which is used to work on production hot fixes and quick development activities as a result of production findings. The other is the environment that MDM is doing its ongoing development on. From the development environments, MDM maintains the path-to-production which incorporates all other pre-production environments.
It could come up as to which MDM environment application development environments will use and who will maintain those environments. If applications are going to use one of the MDM environments, there may be conflict with MDM's development. If a copy is used, space must be procured and that copy must be managed.
There are also MDM workflows, where we find a ton of confusion in regards to who will update them, since they are very focused on the business. If the project is providing data to MDM, the data will need to be sourced. If an ESB is present in the shop, its utilization must be considered.
Pre-production testing will likely need to involve multiple teams. Certainly, this is nothing new as many projects have had this need before. However, it increases the need for coordination of personnel, environments and testing resources. It is likely that each team will have its own set of tests, as well as the overall integrated test.
And finally, let's not forget good old production support. MDM normally needs to be on a 24 x 7 x 365 support schedule. Shops vary in terms of activity that might occur with MDM data overnight. Regardless, production support carries with it all the usual concerns of utilizing and educating existing first level support personnel and creating the escalation plan.
Posted March 8, 2011 12:46 PM
Permalink | No Comments |