Environment: We have a multi-terabyte database at our company. I am in the reporting department. On a weekly basis, we have a meeting with our IT contacts regarding bug-fix and enhancement requests.
On most of our issues, there is an ETA provided that represents either the date the code will go live or the date the analysis on the issue/enhancement is expected to be complete. If analysis determines that a code change will be implemented, the ETA is changed to reflect the go-live date.
All is good to this point.
On a number of entries, there is no ETA provided. This doesn’t make sense to me. I have never worked in an environment where people are unable to provide even an estimate of when they will be able to complete a task. In fact, I have been on the receiving end of having to provide an ETA at other companies so I know it is not an exact science… that is why the word Estimate is used.
When I requested that we get ETAs from the other department, I ran into a wall of opposition even from my own department.
Am I wrong to think that people should be able to provide an ETA on analysis of a problem?
~Thadeus
On most of our issues, there is an ETA provided that represents either the date the code will go live or the date the analysis on the issue/enhancement is expected to be complete. If analysis determines that a code change will be implemented, the ETA is changed to reflect the go-live date.
All is good to this point.
On a number of entries, there is no ETA provided. This doesn’t make sense to me. I have never worked in an environment where people are unable to provide even an estimate of when they will be able to complete a task. In fact, I have been on the receiving end of having to provide an ETA at other companies so I know it is not an exact science… that is why the word Estimate is used.
When I requested that we get ETAs from the other department, I ran into a wall of opposition even from my own department.
Am I wrong to think that people should be able to provide an ETA on analysis of a problem?
~Thadeus