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.
Showing posts with label plan. Show all posts
Showing posts with label plan. Show all posts
Saturday, January 22, 2011
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.
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.
Friday, November 19, 2010
Day 595 - Critical Path
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.
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.
Monday, July 19, 2010
Day 470 - New Data Set for Weekend Tests
During the weekly team meeting I got a request from management to prepare a very specific data set to test during this weekend.
It is not hard do get it, but the quantity of work involved will fulfill us for a couple of days.
During the meeting I've told management that by now the implementation of the automatic tests should have been finished. But in fact they have not even started. Plus, management has decided to cut the number of tests to implement and perform. I've officially stated that, in my professional opinion, the original number of tests should be expanded and not cut, since there was still many business things left out untested. But management things the opposite and they rule, it's their project.
Again, as I've been doing for over the past weeks, I've told management that the first simulation, and the entire plan, will be compromised if no action is taken this week.
It is not hard do get it, but the quantity of work involved will fulfill us for a couple of days.
During the meeting I've told management that by now the implementation of the automatic tests should have been finished. But in fact they have not even started. Plus, management has decided to cut the number of tests to implement and perform. I've officially stated that, in my professional opinion, the original number of tests should be expanded and not cut, since there was still many business things left out untested. But management things the opposite and they rule, it's their project.
Again, as I've been doing for over the past weeks, I've told management that the first simulation, and the entire plan, will be compromised if no action is taken this week.
Day 461 - New GIS Version
The new GIS software version has been installed. I've just found out it actually should be ready three weeks ago. It seems the new version wasn't finished on time and that has cost the entire migration project 3 weeks of delay.
This means account has may be tested this week.
Some weeks ago management had planned to make up the lost time and put the project on track.
Unfortunately, reality is totally different, time is running out and the project is getting even more delayed every day...
This means account has may be tested this week.
Some weeks ago management had planned to make up the lost time and put the project on track.
Unfortunately, reality is totally different, time is running out and the project is getting even more delayed every day...
Day 447 - Small Vacations
Lots of people, me included, has taken some time off due to a couple of holidays.
This means that the mapping team has not performed as fast as it was required, thus the project did not recover the lost time as it needed.
The actions taken by management and the mapping team show that it will be very difficult to comply with the current plan.
This means that the mapping team has not performed as fast as it was required, thus the project did not recover the lost time as it needed.
The actions taken by management and the mapping team show that it will be very difficult to comply with the current plan.
Monday, November 2, 2009
Day 212 - Replaning
The data migration is just one item in the entire project, and since the main project is always changing, it was time to re-plan the data migration sub-project.
The result of such action showed that we're around 5% behind schedule.
The problem is not the number, it is not a worrying number since it can be recovered in one week.
The problem is the reason for that number.
We are behind schedule because the project sponsor is unable to close data migration tasks.
We do several rounds of functional mapping, every time we left some unmapped fields because doubts exists, which is totally normal, but then inertia comes in!
If we do not push the project sponsor teams by making extra mapping sessions, they will not move and will not find the answers for the doubts.
We could live with this model previously, since we did manage to get time for that, but now we have our hands full so we cannot participate in extra mappings sessions.
The result of such action showed that we're around 5% behind schedule.
The problem is not the number, it is not a worrying number since it can be recovered in one week.
The problem is the reason for that number.
We are behind schedule because the project sponsor is unable to close data migration tasks.
We do several rounds of functional mapping, every time we left some unmapped fields because doubts exists, which is totally normal, but then inertia comes in!
If we do not push the project sponsor teams by making extra mapping sessions, they will not move and will not find the answers for the doubts.
We could live with this model previously, since we did manage to get time for that, but now we have our hands full so we cannot participate in extra mappings sessions.
Wednesday, July 1, 2009
Day 88 - Mappings at Cruse Speed
Insurance claims mapping is rolling at cruse speed and we're already implementing some of them.
There's already other areas eager to start the functional mapping, but we've decided to close the insurance claims before starting up new areas.
Since the due date has been shifted from October to April next year, the project sponsor decided to interrupt the project in August for a full month vacation. This makes sense since October was only possible if the sponsor, and ourselves, worked full time, meaning no vacation for anyone.
There's already other areas eager to start the functional mapping, but we've decided to close the insurance claims before starting up new areas.
Since the due date has been shifted from October to April next year, the project sponsor decided to interrupt the project in August for a full month vacation. This makes sense since October was only possible if the sponsor, and ourselves, worked full time, meaning no vacation for anyone.
Subscribe to:
Posts (Atom)
Posts
