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.
Showing posts with label team. Show all posts
Showing posts with label team. Show all posts
Saturday, January 22, 2011
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.
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.
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 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.
Monday, September 6, 2010
Day 521 - Re-Plan
Today we have re-planned.
The new dead-line will be April 2nd.
This leaves a lot of time to develop and test things.
Unfortunately management is, in my opinion, doing a terrible mistake when it comes to testing. I've personally helped in the draft test document, where around 100 tests that covered the technical part of the data migration, things such as control counts and sums. I've officially stated, more than once, that the test document should be expanded with the business tests, which should be around the 100 test also. In short, the testing document should cover around 200 tests, minimum.
My professional opinion on this has been ignored, and management identified only 27 tests to be implemented. This is, obviously, insufficient. Only 13.5% of the tests that should be performed will not guarantee the data migration quality.
This is clearly a high risk, but management has been so under pressure due to the time delays that it is making the most old, common and newbie mistake of them all: cutting on quality.
This is entirely a client problem, since its business will have to live with the data as it has been migrated. Everybody knows how bad, dirty and erroneous data impacts a business, but management seems to be ignoring this.
It looks like time is not the only issue with this project. It seems that cost has slip 50% already. No wonder administration is now taking a closer look and paying extra attention to this project.
The new dead-line will be April 2nd.
This leaves a lot of time to develop and test things.
Unfortunately management is, in my opinion, doing a terrible mistake when it comes to testing. I've personally helped in the draft test document, where around 100 tests that covered the technical part of the data migration, things such as control counts and sums. I've officially stated, more than once, that the test document should be expanded with the business tests, which should be around the 100 test also. In short, the testing document should cover around 200 tests, minimum.
My professional opinion on this has been ignored, and management identified only 27 tests to be implemented. This is, obviously, insufficient. Only 13.5% of the tests that should be performed will not guarantee the data migration quality.
This is clearly a high risk, but management has been so under pressure due to the time delays that it is making the most old, common and newbie mistake of them all: cutting on quality.
This is entirely a client problem, since its business will have to live with the data as it has been migrated. Everybody knows how bad, dirty and erroneous data impacts a business, but management seems to be ignoring this.
It looks like time is not the only issue with this project. It seems that cost has slip 50% already. No wonder administration is now taking a closer look and paying extra attention to this project.
Day 517 - Back from Vacations
We've just came back from our vacations and we've just found out that things have taken a twist.
The GIS is still not ready, instead of speeding up it actually delayed, thus it should be ready by the end of September.
Also, as I though, administration gave management one last chance to make it. It looks that this time there will be watch points, where management will decide to continue, or cancel the project, depending on its status.
We already have a working plan for this week, which kind of makes it serious when management says this time is for real.
The GIS is still not ready, instead of speeding up it actually delayed, thus it should be ready by the end of September.
Also, as I though, administration gave management one last chance to make it. It looks that this time there will be watch points, where management will decide to continue, or cancel the project, depending on its status.
We already have a working plan for this week, which kind of makes it serious when management says this time is for real.
Day 486 - First Simulation is No-Go
The first simulation will not happen this weekend.
As predicted, things must be re-planned since the dead lines will be impossible to accomplish mainly because the GIS software is not ready.
I've just discovered that the claims area is still under development and should be ready somewhere around mid August.
The re-plan will be a though decision for the administration, since management will have to explain very well why a new re-plan is required.
I have the idea that management has one last shot on getting this project done. I believe administration will allow this, last, re-plan, and that it will be the last one.
The data migration team will now go on vacation for the entire month of August.
We expect things to be better when we get back.
As predicted, things must be re-planned since the dead lines will be impossible to accomplish mainly because the GIS software is not ready.
I've just discovered that the claims area is still under development and should be ready somewhere around mid August.
The re-plan will be a though decision for the administration, since management will have to explain very well why a new re-plan is required.
I have the idea that management has one last shot on getting this project done. I believe administration will allow this, last, re-plan, and that it will be the last one.
The data migration team will now go on vacation for the entire month of August.
We expect things to be better when we get back.
Day 482 - Really Bad News
The tests over the weekend when somewhat OK, but the first simulation of the data migration is compromised.
Things are still pretty unstable and there isn't a single test for validation defined. The first simulation will receive a no-go decision from me, and probably from management to, which means a re-plan will most probably occur.
Things are still pretty unstable and there isn't a single test for validation defined. The first simulation will receive a no-go decision from me, and probably from management to, which means a re-plan will most probably occur.
Day 479 - Another Data Set for Weekend Tests
We have set up a new data set for the weekend tests, but things are so delayed that the minimum conditions for the first simulation to happen.
In particular, there isn't a single test defined to validate the data migration.
In particular, there isn't a single test defined to validate the data migration.
Monday, July 19, 2010
Day 475 - New GIS Version Ready
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.
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.
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
