The new GIS version has been installed but the data we've prepared has not been loaded.
A new request for the same data has already been made in order to load it over the next weekend.
Within two weeks from the, still planned, first simulation, the target system, GIS, is still unstable, the claims are not fully mapped, account is still untested and automatic tests are still on paper.
We are precisely were we where some weeks ago, when management showed that did believe on this plan.
Monday, July 19, 2010
Day 472 - Bad, Bad News.
We've got the data ready for loading, as requested by management, for this weekend test.
When I went to talk with management, I was surprised to know that probably the data will not be loaded because a new GIS version was going to be installed. And it was not only me that was surprised, management didn't new this was going to happen!
Definitely management is unable to manage this project, planed things do not happen when they should and unplanned things with high impact happen without management acknowledgment.
Because of this new GIS version installation this means we have been working the last two days for nothing and the testing team will have to perform the same old ad hoc tests again.
This was also the day that the administration received the bad news. We, the data migration team, have officially stated that the immaturity of GIS, the current state of mapping rules, and the nonexistence of automated tests have made the first simulation, still scheduled for the last weekend of this month, impractical.
We also officially stated that this has a direct impact on the overall project and a new plan is now required because the current one will not happen.
When I went to talk with management, I was surprised to know that probably the data will not be loaded because a new GIS version was going to be installed. And it was not only me that was surprised, management didn't new this was going to happen!
Definitely management is unable to manage this project, planed things do not happen when they should and unplanned things with high impact happen without management acknowledgment.
Because of this new GIS version installation this means we have been working the last two days for nothing and the testing team will have to perform the same old ad hoc tests again.
This was also the day that the administration received the bad news. We, the data migration team, have officially stated that the immaturity of GIS, the current state of mapping rules, and the nonexistence of automated tests have made the first simulation, still scheduled for the last weekend of this month, impractical.
We also officially stated that this has a direct impact on the overall project and a new plan is now required because the current one will not happen.
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 468 - New Week, Old Problems
Data has been loaded into GIS with some errors. We already expected errors from the account area, that was not properly tested, and the claims are not even close to be totally defined.
On the top of that, insurances have suffered a review which will result on a set of changes and, of course, a new set of tests.
Only three weeks left for the first simulation, but things are pretty unstable. I forecast a no-go decision for that first simulation. And if things don't get straight, I forecast a re-plan of the entire data migration project.
On the top of that, insurances have suffered a review which will result on a set of changes and, of course, a new set of tests.
Only three weeks left for the first simulation, but things are pretty unstable. I forecast a no-go decision for that first simulation. And if things don't get straight, I forecast a re-plan of the entire data migration project.
Day 464 - Small Test Planed
Things are not working out as expected. The first data loaded into GIS was rejected due to inconsistencies between the mapping rules and the GIS products configuration.
This is a recurring problem, every time a clean data load is performed GIS is not correctly configured to take it and errors that should not exist arise.
Account cannot be tested as expected because we need to prepare a small set of data to load into GIS this weekend. This has became the main focus for this week.
On the top of that, the automatic test strategy is still on paper. It is on paper for some weeks now and it seems it will not go anywhere anytime soon. The testing team is also tired of performing the same ad hoc tests again and again, they feel like little hamsters running on the wheel, they work hard but don't really go anywhere.
The first simulation is in less than 4 week and I'm already tired to tell management that account, accidents and tests are running late. If no action is performed, this will compromise the first simulation and, probably, the entire data migration project plan.
This is a recurring problem, every time a clean data load is performed GIS is not correctly configured to take it and errors that should not exist arise.
Account cannot be tested as expected because we need to prepare a small set of data to load into GIS this weekend. This has became the main focus for this week.
On the top of that, the automatic test strategy is still on paper. It is on paper for some weeks now and it seems it will not go anywhere anytime soon. The testing team is also tired of performing the same ad hoc tests again and again, they feel like little hamsters running on the wheel, they work hard but don't really go anywhere.
The first simulation is in less than 4 week and I'm already tired to tell management that account, accidents and tests are running late. If no action is performed, this will compromise the first simulation and, probably, the entire data migration project plan.
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 454 - New GIS Version Required
A new GIS software version is required in order to overcome a problem in account that has been stalled for weeks.
Time is running out and the new GIS version should be available at the end of this week.
This will be a major improvement in the account area because the mapping and testing teams will finally be able to define it and test it.
Time is running out and the new GIS version should be available at the end of this week.
This will be a major improvement in the account area because the mapping and testing teams will finally be able to define it and test it.
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.
Day 427 - No Real Improvements
Things are not going as expected.
The mapping is still unstable and there are delays in solving the problems.
The test team is not working full time since there is not much to test.
Management is trying to act in order to put everything on track again, I sincerely hope it can go on track. There is still time, with an added effort, to make things work on time.
The mapping is still unstable and there are delays in solving the problems.
The test team is not working full time since there is not much to test.
Management is trying to act in order to put everything on track again, I sincerely hope it can go on track. There is still time, with an added effort, to make things work on time.
Subscribe to:
Posts (Atom)
Posts
