This situation and the pressure people is getting to make things fast it's totally unbelievable. This has lead management into splitting the data migration by the next two weekends. Thus, the next weekend it will migrate customers, insurance claims and invoices. But only if they are not involved in some kind of accident, otherwise it's migration will happen in the other weekend.
This will allow the integration test teams to perform preliminary validations and I also believe it will be great because I know that the entire data migration does not integrate into GIS during a single weekend with the current AS/400 system configuration.
Meanwhile, the software patches continues to give us problems.
Showing posts with label management. Show all posts
Showing posts with label management. Show all posts
Saturday, January 22, 2011
Day 658 - Next Qualification Migration In Risk
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.
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.
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.
Day 643 - The Begining of Massive Changes
New year's gone and we're starting a massive change set on things that should be closed and stable.
Change requests have already started, but management asked me to increase the team since there will be a lot of change requests very soon and they need to be ready and the mapping must be stabilized for the next big data migration into the Q&A environment.
I have some concerns with this kind of activity when we're just two weeks away from the next big test.
Change requests have already started, but management asked me to increase the team since there will be a lot of change requests very soon and they need to be ready and the mapping must be stabilized for the next big data migration into the Q&A environment.
I have some concerns with this kind of activity when we're just two weeks away from the next big test.
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.
Thursday, December 23, 2010
Day 632 - Christmas Break
This is the last work day before a short Christmas break.
It seems the "I'll tell you how to do your job" symptom is getting worst.
Now management, instead of managing, is, literally, querying the target database with SQL in AS/400 and is creating a fuss by asking and making assumptions about things that he finds awkward.
The problem is that he doesn't know the target system that well and is just getting on everyone's nerves because people has to stop working the data migration and waste time to get data right to answer him and showing how he was wrong.
I hope this short Christmas break helps everyone to calm down.
It seems the "I'll tell you how to do your job" symptom is getting worst.
Now management, instead of managing, is, literally, querying the target database with SQL in AS/400 and is creating a fuss by asking and making assumptions about things that he finds awkward.
The problem is that he doesn't know the target system that well and is just getting on everyone's nerves because people has to stop working the data migration and waste time to get data right to answer him and showing how he was wrong.
I hope this short Christmas break helps everyone to calm down.
Day 630 - Qualification Preliminary Report
The preliminary report indicates a very good success rate.
It has been presented to management, and administration, during the weekly meeting.
But even with good results, management is really panicking and it's showing it semi-publicly.
Now management is trying to tell everybody how to do their work, me included.
Management really told me how to do my work, technically, with database details and everything. When we started discussing the problem I realised pretty quickly that actually, he didn't knew what he was talking about. So, I've just agreed with him and let it go. The other way was to "beat him up" in front of his entire team showing that he didn't not even had a clue about how the process was set up, and he knew even less about our requirements and the technical solutions we had to set up to met them.
This kind of action is one more panic symptom, and it's not helping the team.
It has been presented to management, and administration, during the weekly meeting.
But even with good results, management is really panicking and it's showing it semi-publicly.
Now management is trying to tell everybody how to do their work, me included.
Management really told me how to do my work, technically, with database details and everything. When we started discussing the problem I realised pretty quickly that actually, he didn't knew what he was talking about. So, I've just agreed with him and let it go. The other way was to "beat him up" in front of his entire team showing that he didn't not even had a clue about how the process was set up, and he knew even less about our requirements and the technical solutions we had to set up to met them.
This kind of action is one more panic symptom, and it's not helping the team.
Day 623 - New Processes
As expected, the new controlling team as set up a new set of controlling procedures, or processes, or, as they actually are, bureaucracies.
I've been asked to help setting this processes for the GIS data loading step.
I'll be glad to help, since it will allow me to actually make this a useful thing.
I've been asked to help setting this processes for the GIS data loading step.
I'll be glad to help, since it will allow me to actually make this a useful thing.
Day 616 - No Commitment
In the weakly meeting management tried to commit the team with new dates for some task that probably will delay in the next few days.
But since the team is not sure that this delay will happen and, if it happens, how much time will it be, there was no answer whatsoever.
Management was not happy with this situation. Currently there's a lot of friction between management and the migration team that resulted from the way management has treated it's own team along the way, and specially since the migration is part of the critical path.
But since the team is not sure that this delay will happen and, if it happens, how much time will it be, there was no answer whatsoever.
Management was not happy with this situation. Currently there's a lot of friction between management and the migration team that resulted from the way management has treated it's own team along the way, and specially since the migration is part of the critical path.
Day 609 - New Controlling Team
There's a new team in the project. It's an outside management consultancy that will be responsible for the project control.
Things will be pretty much the same, but I presume some more bureaucracy will appear soon, again under the label of "control"...
Things will be pretty much the same, but I presume some more bureaucracy will appear soon, again under the label of "control"...
Day 598 - Management Pressure
Since the data migration project is part of the project critial path, there's a lot more pressure on the team.
Management is pressuring the team because management is starting panicking.
And, as usual, when management is in panic mode, there's an increase of bureaucracy hidden under the label of "control".
Management needs to control in order to know really fast if things start to slide again.
Now, the migration team has to do more reporting documents, witch is not very pleasant when people are already working 10-12 hours per day for some consecutive weeks.
Management is pressuring the team because management is starting panicking.
And, as usual, when management is in panic mode, there's an increase of bureaucracy hidden under the label of "control".
Management needs to control in order to know really fast if things start to slide again.
Now, the migration team has to do more reporting documents, witch is not very pleasant when people are already working 10-12 hours per day for some consecutive weeks.
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 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.
Subscribe to:
Posts (Atom)
Posts
