The data migration is now officially in the critical path of the entire corporation data migration project.
This are very bad news. But actually are not unexpected news.
Only this week I consider the data migration stable in a way that allow us to code the transformation rules with low change requests.
In fact, looking back, I sense we are precisely in the same point were we were when we went on vacations, except that now we have the insurance claims ready.
I sense that this data project has been stalled for three months, and I also sense I'm not the only one.
Friday, November 19, 2010
Day 582 - Nervous Managament and Team Delusion
Management is getting more nervous every time.
Things are still not fully stable and insurance claims are delayed. This is still not a real problem, but if this continues it can jeopardise April's dead line.
Instead of helping the migration team, management react with the classical control move, forcing people to report more things. This will, obviously, increase the team effort and consume more time.
Many times management seems to blame its own team for the project delays, and most of those times it is unfair.
This actually results from political problems, since management has committed itself in a way that it can only look good by blaming its own team.
People are, obviously, very unhappy with this situation. I actually feel that the team is kind of "wrecked", they just don't care as they did before. In the beginning the team embraced this project in a very positive way. They always fought for the best interest of the corporation, but they have been unfairly blamed so many times by the management that they just "cracked". I sense that, unfortunately, management has destroyed one great team, one kind of team that one doesn't see every day nor everywhere.
Things are still not fully stable and insurance claims are delayed. This is still not a real problem, but if this continues it can jeopardise April's dead line.
Instead of helping the migration team, management react with the classical control move, forcing people to report more things. This will, obviously, increase the team effort and consume more time.
Many times management seems to blame its own team for the project delays, and most of those times it is unfair.
This actually results from political problems, since management has committed itself in a way that it can only look good by blaming its own team.
People are, obviously, very unhappy with this situation. I actually feel that the team is kind of "wrecked", they just don't care as they did before. In the beginning the team embraced this project in a very positive way. They always fought for the best interest of the corporation, but they have been unfairly blamed so many times by the management that they just "cracked". I sense that, unfortunately, management has destroyed one great team, one kind of team that one doesn't see every day nor everywhere.
Day 575 - Sample Loading
After overcoming the DB2 problems, the sample has been loaded into the quality system.
We had some errors, some we were already expecting, and overall management were satisfied with it because the integration tests can be performed.
We had some errors, some we were already expecting, and overall management were satisfied with it because the integration tests can be performed.
Day 573 - DB2 Crash
This weekend we are going to load a specific sample in the quality system for integration tests.
Unfortunately this task were almost compromised because our DB2 staging area database crashed real hard.
It took me around 4 hours to put everything working again, and I had to reconstruct the entire staging area responsible for holding the transformed data.
Unfortunately this task were almost compromised because our DB2 staging area database crashed real hard.
It took me around 4 hours to put everything working again, and I had to reconstruct the entire staging area responsible for holding the transformed data.
Day 563 - Tests and Validations
The 13.5% of automatic validation are half-way developed. We've met in order to check if everyone was checking the same things the same way in all the systems.
As expected, there were some differences which will easily be corrected.
Meanwhile, the tests performed by the test team are still half-speed, things are not as stable as they should be, which means the team does not have much work.
As expected, there were some differences which will easily be corrected.
Meanwhile, the tests performed by the test team are still half-speed, things are not as stable as they should be, which means the team does not have much work.
Day 558 - Mapping Review
Since there is a mismatch between what target system has now implemented and current mappings, the mappings have been fully reviewed.
This consolidation action will result in a much desired stability.
Insurance policies are still not as stable as they were before the vacations, and management is starting to get nervous about it.
This consolidation action will result in a much desired stability.
Insurance policies are still not as stable as they were before the vacations, and management is starting to get nervous about it.
Day 549 - GIS Frozen
It seems that GIS has now frozen its development.
I hope this will bring some stability to the mappings is particular and to all the data migration project in general.
I hope this will bring some stability to the mappings is particular and to all the data migration project in general.
Day 534 - New Team Reshape
The team will suffer a new reshape.
Professionally I had planed to start a new project with a new client when this data migration ended next month.
But since the dead line has been pushed to April next year, that will not be possible.
Currently I'm the technical leader of this data migration and there is no one else in the team, or among any other team involved, that can replace me with a low cost and zero impact in the project.
Since I cannot leave and had agreed a new start date for another client, I had to negotiate my involvement in both projects. This was actually easy to do and the result is a balance between my involvement in both projects.
I already had requested one more person to our team, and this situation has just speed up that process. The team will actually be reinforced with two people, half-time.
They are both knowledge about Data Fusion and data migrations, so their integration will be easy and fast.
Professionally I had planed to start a new project with a new client when this data migration ended next month.
But since the dead line has been pushed to April next year, that will not be possible.
Currently I'm the technical leader of this data migration and there is no one else in the team, or among any other team involved, that can replace me with a low cost and zero impact in the project.
Since I cannot leave and had agreed a new start date for another client, I had to negotiate my involvement in both projects. This was actually easy to do and the result is a balance between my involvement in both projects.
I already had requested one more person to our team, and this situation has just speed up that process. The team will actually be reinforced with two people, half-time.
They are both knowledge about Data Fusion and data migrations, so their integration will be easy and fast.
Day 528 - The Start of a New Era
The new plan is now in action but things are about the same.
Insurance policy had a backset. Thins that were stable, are now being rejected and mappings are now suffering many changes.
Stability has still not been achieved and GIS is still a moving target, and the migration team is struggling to keep up with the new plan in order to comply with it.
Tests still have not full started because it's still not possible to load data into GIS.
The start of this new era is fictional because everything is about the same as before.
Insurance policy had a backset. Thins that were stable, are now being rejected and mappings are now suffering many changes.
Stability has still not been achieved and GIS is still a moving target, and the migration team is struggling to keep up with the new plan in order to comply with it.
Tests still have not full started because it's still not possible to load data into GIS.
The start of this new era is fictional because everything is about the same as before.
Subscribe to:
Posts (Atom)
Posts
