First, let me say I HAVE NO IDEA about the details of the PC web upgrade.
BUT, here are my thoughts on projects of this scope.
I have been with my company for 17 years. I have seen many MAJOR projects either outsourced, have major components outsourced, or a project leader from OUTSIDE hired to run the project (or a combo of all 3). (None of these would know our industry/workflow.)
PC may have hired an outside person to lead this project. That person may have led many similar projects successfully at other types of companies. But, they may not know this industry. They almost certainly would have had to either hire additional tech staff or outsource. Many of these folks may never have ever been involved with the set up P3 and may not know what we need. I don't know this, I am just offering this as a possibility.
I can't tell you how many times at work I have overheard gripes from people about how things were set up and when you realize which people were making the decisions, you would know why it did not make sense or why things didn't follow our workflow.
I work in the IS department of our company. I have a background in this industry and have worked in other depts before ending up in IS. Keep in mind that many IS people at many companies KNOW THEIR job, but aren't necessarily familiar with that particular industry.
I am a very small part of a MAJOR project at our company right now. I am creating web forms for customers to fill out. Here is an example: I have been provided with a list of fields and specs (& restrictions) for these forms. One of the fields had been described to me as numeric only. AS A PROGRAMMER, I should have just kept my mouth shut & coded that restriction, EXCEPT, from my experience in this industry, I know that this particular field can contain letters also! (I can name at least 2 other programmers in my dept who would NOT have known that.)
The 2 people "running" this have no experience in our industry. Both have been with our company less than a year.
If I were just another programmer, I would have done what they said. Instead, I flagged it. I can't tell you how many things have gone by like this and I am SO tempted to say "well, this is what you told me to do". But, I usually bring it to someone's attention.
********
BUT IN THE END...it is REALLY important to email issues to HO. It could be that many of these items are true bugs, but it could also be that the people in charge of this really did not realize some of the "specifics" and requirements of what we do.
Also, keep in mind the tech folks. Many of them are provided exact specs of what needed to be done and they could have gotten all that right only to start hearing from us that things do not follow that spec. It can be EXTREMELY frustrating to have worked very hard at creating something only to have to go back and REWORK it!
For example, they could have been told that everyone will have an email and based EVERYTHING on that very simple fact. To go back now and not require an email could be too major of an overhaul and nearly impossible to "undo". (Maybe that's why they are giving us the "fake" email to use.)
Just guessing at all of this, but in the end, I am SURE the way things have gone with the upgrade was not HO's intention. It is frustrating to us...but it has got to be panicking them!
Just my 2 cents!
BUT, here are my thoughts on projects of this scope.
I have been with my company for 17 years. I have seen many MAJOR projects either outsourced, have major components outsourced, or a project leader from OUTSIDE hired to run the project (or a combo of all 3). (None of these would know our industry/workflow.)
PC may have hired an outside person to lead this project. That person may have led many similar projects successfully at other types of companies. But, they may not know this industry. They almost certainly would have had to either hire additional tech staff or outsource. Many of these folks may never have ever been involved with the set up P3 and may not know what we need. I don't know this, I am just offering this as a possibility.
I can't tell you how many times at work I have overheard gripes from people about how things were set up and when you realize which people were making the decisions, you would know why it did not make sense or why things didn't follow our workflow.
I work in the IS department of our company. I have a background in this industry and have worked in other depts before ending up in IS. Keep in mind that many IS people at many companies KNOW THEIR job, but aren't necessarily familiar with that particular industry.
I am a very small part of a MAJOR project at our company right now. I am creating web forms for customers to fill out. Here is an example: I have been provided with a list of fields and specs (& restrictions) for these forms. One of the fields had been described to me as numeric only. AS A PROGRAMMER, I should have just kept my mouth shut & coded that restriction, EXCEPT, from my experience in this industry, I know that this particular field can contain letters also! (I can name at least 2 other programmers in my dept who would NOT have known that.)
The 2 people "running" this have no experience in our industry. Both have been with our company less than a year.
If I were just another programmer, I would have done what they said. Instead, I flagged it. I can't tell you how many things have gone by like this and I am SO tempted to say "well, this is what you told me to do". But, I usually bring it to someone's attention.
********
BUT IN THE END...it is REALLY important to email issues to HO. It could be that many of these items are true bugs, but it could also be that the people in charge of this really did not realize some of the "specifics" and requirements of what we do.
Also, keep in mind the tech folks. Many of them are provided exact specs of what needed to be done and they could have gotten all that right only to start hearing from us that things do not follow that spec. It can be EXTREMELY frustrating to have worked very hard at creating something only to have to go back and REWORK it!
For example, they could have been told that everyone will have an email and based EVERYTHING on that very simple fact. To go back now and not require an email could be too major of an overhaul and nearly impossible to "undo". (Maybe that's why they are giving us the "fake" email to use.)
Just guessing at all of this, but in the end, I am SURE the way things have gone with the upgrade was not HO's intention. It is frustrating to us...but it has got to be panicking them!
Just my 2 cents!