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.
Monday, February 7, 2011
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Subscribe to:
Posts (Atom)
Posts
