Monday, February 7, 2011

Day 678 - New Data Migration Strategy

The data migration strategy has changed again.
Now we will have 2 phases, and the first one will be slitted in two, making it an incremental data migration.
In phase One A, we will migrate clients and a big part of insurances that are wither active or that have accidents on it.
The phase One B, we will migrate the remaining insurances that are wither active or that have accidents on it, and everything related with those insurances.
And in the final phase, phase Two, we will migrate everything else, commonly known as historical data.

This will force me to implement control mechanisms in order to know which data will go in which phase. We will test this mechanism within a week or so in another big data migration.

Day 671 - Murphy Was Nicer

The data migration over this last weekend worked better.
But Murphy's law still stroke back, but in a lighter way.
For the next two weeks we will have lots of work fixing everything that went wrong in this past two weekends.

Day 667 - Not bad Results

We actually had very good results in data that was loaded property into GIS.
Since most of the problems occurred outside GIS, the data we sent into it had an overall success above 90%, and many over 99%, which is quite good considering all the problems we had.
The tests performed over that migrated data are also satisfying, which is quite good.

Day 664 - Another Data Migration Try

This weekend data migration was stroke hard by Murphy's law.
It was terrible. It really seemed that everything that could go wrong, went wrong.
Many of the failed data loads will be repeated during the week.
And in the next weekend we'll try again with another data set.

Saturday, January 22, 2011

Day 660 - "Go" Decision For Half Data Migration

This situation and the pressure people is getting to make things fast it's totally unbelievable. This has lead management into splitting the data migration by the next two weekends. Thus, the next weekend it will migrate customers, insurance claims and invoices. But only if they are not involved in some kind of accident, otherwise it's migration will happen in the other weekend.

This will allow the integration test teams to perform preliminary validations and I also believe it will be great because I know that the entire data migration does not integrate into GIS during a single weekend with the current AS/400 system configuration.

Meanwhile, the software patches continues to give us problems.

Day 658 - Next Qualification Migration In Risk

According to planing, in the next weekend a new data migration should occur in the qualification environment. But unfortunately there's so many problems and change requests happening that the mapping is very unstable within a few days from the beginning of the data migration.

This next weekend data migration is in risk, and this is critical for the entire project, since the data migration is in the project critical path.

Management still doesn't know if it's a "go" or a "no go", that decision will be taken late this week.

Day 655 - Under Pressure

This past week the team has been reinforced with one extra person. This was critical because we had 4% of change requests during this past 5 week. He have implemented and tested 146 change requests, including new mapping tables and claim mappings that should be stable for weeks now.

This kind of instability is making the entire team under great pressure beacause within one week, a new data migration will be performed to qualification environment.

Tuesday, January 11, 2011

Day 651 - Distinct Views of the Same Situation

Management and me disagree when it comes to the current status of the data migration project.
Management seems happy with it and I'm concerned with the quantity of change requests we're getting when we're so near the next big data migration.
After that we'll have only one month before the beginning of the simulations and I'm not happy because I already know things will change a lot again.

I'm very concerned with this kind of undesired activity since it may be a no-go factor.
Management has not taken my opinion too seriously and has assured its own team things are ok.

Day 647 - New Patch

It's unbelievable the quantity of patches GIS has already received in order to increase its functionality and to fix the bugs previous patches have introduced!
I've lost two mornings working with the functional team in the account module just to find out that we were on a witch chase.
The problem was on GIS and we have just been informed that the new patch fixes the errors we were getting. The problem is that these errors only appeared after a previous software installation the week before.

Day 643 - The Begining of Massive Changes

New year's gone and we're starting a massive change set on things that should be closed and stable.
Change requests have already started, but management asked me to increase the team since there will be a lot of change requests very soon and they need to be ready and the mapping must be stabilized for the next big data migration into the Q&A environment.
I have some concerns with this kind of activity when we're just two weeks away from the next big test.

Tuesday, December 28, 2010

Day 637 - Everything's on Time

It seems that everything is OK by now.
After some stressing weeks, the Christmas break seems to have a positive effect on everyone. New end dates for functional mapping have been defined and thus, according with the plan, we're on time again.

Thursday, December 23, 2010

Day 632 - Christmas Break

This is the last work day before a short Christmas break.
It seems the "I'll tell you how to do your job" symptom is getting worst.
Now management, instead of managing, is, literally, querying the target database with SQL in AS/400 and is creating a fuss by asking and making assumptions about things that he finds awkward.
The problem is that he doesn't know the target system that well and is just getting on everyone's nerves because people has to stop working the data migration and waste time to get data right to answer him and showing how he was wrong.

I hope this short Christmas break helps everyone to calm down.

Day 630 - Qualification Preliminary Report

The preliminary report indicates a very good success rate.
It has been presented to management, and administration, during the weekly meeting.

But even with good results, management is really panicking and it's showing it semi-publicly.
Now management is trying to tell everybody how to do their work, me included.
Management really told me how to do my work, technically, with database details and everything. When we started discussing the problem I realised pretty quickly that actually, he didn't knew what he was talking about. So, I've just agreed with him and let it go. The other way was to "beat him up" in front of his entire team showing that he didn't not even had a clue about how the process was set up, and he knew even less about our requirements and the technical solutions we had to set up to met them.
This kind of action is one more panic symptom, and it's not helping the team.

Day 629 - Last Qualification Day

As I predicted, account took ages and it's loading has been aborted at 21:50.
This means that not only account was only partially loaded but also that some other residual, but important, data didn't had the chance to be loaded.

Management seems to be unhappy, but my initial report data indicate a very good success rate, except for three insurance claims areas.

Day 628 - Second Qualification Weekend Day

Some insurance claims have been loaded but only one area had no errors, all the other areas had insignificant success rates.

The data migration is running late because the car insurance data loading had to be repeated yesterday and account will take ages to load. This means that the data migration will not be completed during the weekend.

Day 627 - First Qualification Weekend Day

The first weekend day will be mainly for insurance data loading.
All insurances have problems, including the car insurance data.
It seems to be am insignificant amount of errors, but I was not expecting any errors from data insurance.

Day 626 - Car Insurance Problems

The loading of the car insurance data has gone totally wrong.
An unidentified problem in GIS has messed up over 11 hours of AS/400 work.
When trying the exact same loading during the day it went just fine, it's one of these awkward problems that happens too many times during the GIS data loading and that no one ever knows the cause...

This will force this migration to be pushed, since car insurances will have to be loaded again during the weekend.

I will be following closely this migration during the weekend.
If some more problems arise I'll be the first one to know and I'll sound the alarms.
I have scheduled a set of checkpoints during the weekend, starting Saturday early and ending Sunday night.

Day 624 - Entity Loading in Qualification

Today we've started a migration for Qualification environment for testing purposes.
Entities have been loading during dawn and it all went well.
This will go on for the hole week and weekend. I've predicted that this will end Monday dawn.

Day 623 - New Processes

As expected, the new controlling team as set up a new set of controlling procedures, or processes, or, as they actually are, bureaucracies.
I've been asked to help setting this processes for the GIS data loading step.
I'll be glad to help, since it will allow me to actually make this a useful thing.

Day 616 - No Commitment

In the weakly meeting management tried to commit the team with new dates for some task that probably will delay in the next few days.
But since the team is not sure that this delay will happen and, if it happens, how much time will it be, there was no answer whatsoever.

Management was not happy with this situation. Currently there's a lot of friction between management and the migration team that resulted from the way management has treated it's own team along the way, and specially since the migration is part of the critical path.