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.
Tuesday, December 28, 2010
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 629 - Last Qualification Day
As I predicted, account took ages and it's loading has been aborted at 21:50.
This means that not only account was only partially loaded but also that some other residual, but important, data didn't had the chance to be loaded.
Management seems to be unhappy, but my initial report data indicate a very good success rate, except for three insurance claims areas.
This means that not only account was only partially loaded but also that some other residual, but important, data didn't had the chance to be loaded.
Management seems to be unhappy, but my initial report data indicate a very good success rate, except for three insurance claims areas.
Day 628 - Second Qualification Weekend Day
Some insurance claims have been loaded but only one area had no errors, all the other areas had insignificant success rates.
The data migration is running late because the car insurance data loading had to be repeated yesterday and account will take ages to load. This means that the data migration will not be completed during the weekend.
The data migration is running late because the car insurance data loading had to be repeated yesterday and account will take ages to load. This means that the data migration will not be completed during the weekend.
Day 627 - First Qualification Weekend Day
The first weekend day will be mainly for insurance data loading.
All insurances have problems, including the car insurance data.
It seems to be am insignificant amount of errors, but I was not expecting any errors from data insurance.
All insurances have problems, including the car insurance data.
It seems to be am insignificant amount of errors, but I was not expecting any errors from data insurance.
Day 626 - Car Insurance Problems
The loading of the car insurance data has gone totally wrong.
An unidentified problem in GIS has messed up over 11 hours of AS/400 work.
When trying the exact same loading during the day it went just fine, it's one of these awkward problems that happens too many times during the GIS data loading and that no one ever knows the cause...
This will force this migration to be pushed, since car insurances will have to be loaded again during the weekend.
I will be following closely this migration during the weekend.
If some more problems arise I'll be the first one to know and I'll sound the alarms.
I have scheduled a set of checkpoints during the weekend, starting Saturday early and ending Sunday night.
An unidentified problem in GIS has messed up over 11 hours of AS/400 work.
When trying the exact same loading during the day it went just fine, it's one of these awkward problems that happens too many times during the GIS data loading and that no one ever knows the cause...
This will force this migration to be pushed, since car insurances will have to be loaded again during the weekend.
I will be following closely this migration during the weekend.
If some more problems arise I'll be the first one to know and I'll sound the alarms.
I have scheduled a set of checkpoints during the weekend, starting Saturday early and ending Sunday night.
Day 624 - Entity Loading in Qualification
Today we've started a migration for Qualification environment for testing purposes.
Entities have been loading during dawn and it all went well.
This will go on for the hole week and weekend. I've predicted that this will end Monday dawn.
Entities have been loading during dawn and it all went well.
This will go on for the hole week and weekend. I've predicted that this will end Monday dawn.
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.
Subscribe to:
Posts (Atom)
Posts
