Things are not going the way I, and the management team, was expecting.
After the restart, teams start working with focused on the current official project dates, even if they don't really believe it.
But the last GIS loadings we've performed showed that there was a major mapping regression. For instance car insurances were all loading correctly and now there isn't a single insurance that loads correctly, they have all been rejected.
It turns out that the products configuration in GIS, that should be concluded some weeks ago, has changed again.
And that was not all, all the product insurance mapping rules are changing. This mapping instability means that the project has an overall regression when there's only 8 weeks left to the first data migration simulation.
But this is not all. When the testing team tried to perform tests, they canceled the task because there was nothing that they could test. The migrated data that was loaded and available for testing will change soon.
Friday, May 28, 2010
Thursday, May 20, 2010
Day 413 - Restart
Today there was a migration meeting between the migration team, one management team responsible and I. It seems the migration will be performed in one shot and October is still the official date. But the management team is ready to take a four week delay, which means the migration would happen in November 1st.
This dates have been largely refuted by the migration team for several reasons. The most important of all is that they do not believe that the GIS implementation will be ready on time form compliance with these dates. This disbelieve has resulted in a very interesting discussion between management and the migration team.
The migration team is tired, the project has now an overall of two working years where these people have a work overload, they have to perform all their usual tasks plus they have to develop the migration. The worst problem came from the fact that historically the GIS implementation has failed to deliver the implementation of the defined requirements on time. Plus, there is still an huge amount of work to be done in this area, so the migration team is more than skeptical, they actually do not believe on these dates.
Worst, they are mad about the fact that the management team is being permissive with the GIS development delays and the features are not fully implementing to the define requirements.
After some pressure by the migration team, the management team admitted that they believe on these dates but do not put aside the possibility of another postpone.
On the top of all that, I've pointed out that there's still a considerable amount of work to be done regarding the tests and quality assurance. We already have identified counting checks and summary checks, but the identification of business rules validation is still work to be done.
Once the validations have been identified, they must be development on critical points: at data extraction, at data loading into the staging area, at data extraction from the staging area, and at data loading into GIS.
Nevertheless, the entire team has agreed to make another extra effort in order to try to comply with the current defined date. After a four week stop, the project restart is planed for tomorrow.
This dates have been largely refuted by the migration team for several reasons. The most important of all is that they do not believe that the GIS implementation will be ready on time form compliance with these dates. This disbelieve has resulted in a very interesting discussion between management and the migration team.
The migration team is tired, the project has now an overall of two working years where these people have a work overload, they have to perform all their usual tasks plus they have to develop the migration. The worst problem came from the fact that historically the GIS implementation has failed to deliver the implementation of the defined requirements on time. Plus, there is still an huge amount of work to be done in this area, so the migration team is more than skeptical, they actually do not believe on these dates.
Worst, they are mad about the fact that the management team is being permissive with the GIS development delays and the features are not fully implementing to the define requirements.
After some pressure by the migration team, the management team admitted that they believe on these dates but do not put aside the possibility of another postpone.
On the top of all that, I've pointed out that there's still a considerable amount of work to be done regarding the tests and quality assurance. We already have identified counting checks and summary checks, but the identification of business rules validation is still work to be done.
Once the validations have been identified, they must be development on critical points: at data extraction, at data loading into the staging area, at data extraction from the staging area, and at data loading into GIS.
Nevertheless, the entire team has agreed to make another extra effort in order to try to comply with the current defined date. After a four week stop, the project restart is planed for tomorrow.
Wednesday, May 5, 2010
Day 399 - Incremental Strategy Analysis
I've finished the requested analysis on performing the data migration incrementally.
Actually, it has a low impact for us because the requested split per product is already implemented and used on most of the data migration mappers. With less than three days work one can adapt the remaining mappers to use this strategy.
Actually, it has a low impact for us because the requested split per product is already implemented and used on most of the data migration mappers. With less than three days work one can adapt the remaining mappers to use this strategy.
Day 398 - Kickoff Planing of Migration Strategy
Management seems to believe that the current data migration will happen in the first weekend of October. We have met and discuss a lot about what needs to be done so that all the required tasks can be officially planed.
But the big news is not that management seems to believe on October as the dead-line. The big news is that management actually does not believe on that date as the final date. Management request me to evaluate the impact of an incremental data migration by product. They've said that this idea was fresh new, but they seem to believe that in October only half of the products will be ready on GIS and the rest will not be available for at least two more months. This new strategy will imply that one data migration will occur in October and another one will probably occur three months later, around January 2011.
But the big news is not that management seems to believe on October as the dead-line. The big news is that management actually does not believe on that date as the final date. Management request me to evaluate the impact of an incremental data migration by product. They've said that this idea was fresh new, but they seem to believe that in October only half of the products will be ready on GIS and the rest will not be available for at least two more months. This new strategy will imply that one data migration will occur in October and another one will probably occur three months later, around January 2011.
Day 391 - Team Leading
I'm now leading the data migration team.
In practice this means that now I decide, instead of discussing things with the ex-team leader, and I have to make all the status reports and other management stuff.
In practice this means that now I decide, instead of discussing things with the ex-team leader, and I have to make all the status reports and other management stuff.
Subscribe to:
Posts (Atom)
Posts
