Day 363 - First Production Problems

The testing team was right. They needed more time to test the system.
The first problem found regards product integration and interface testing.

It looks that the data migrated by us is using a key that differs from a satellite system. We checked the data migrated and it complies with the specification, the mapping rules defined and the transformation rules implemented. This was also confirmed various times over the last 4 months by the tests performed on the migrated data.

The other system is sending a different key from the one we're sending.
This is an obvious integration error which would easily be found and corrected if integration tests had been performed.

With less than 3 month from the real data migration, this is not a good sign. Specially because we've already alerted several times to the need of consistent and automatic tests, something that no one here seems to care for except the testing team which, by the way, does not have the power to enforce it.

Day 360 - First Product Go Live

Things didn't went exactly as planned.
Just minutes before the loading of the migrated data someone just noticed that there was something wrong with the configuration and a critical action took place.
This meant a delay of over 4 hours regarding the original plan but eventually everything went well and the first product in GIS is ready for the go live next Monday.

Day 352 - Data Migration Plan For Go Live

We have just received the plan for the data migration part that is required for the new system kick-off.
We will receive the source data, loaded it in our staging area, execute the transformation rules for the entities and create the GIS loading files for the acceptance and production environments.

Since a postpone has not been granted for the new system go live date, the testing team seems to be working a bit harder and things seem to be a lot better.