1) These days to get cost and time runs under control, parts of IT projects are outsourced. That seems to be easier option. Do you know any example of this from your experience?

2) The requirements or generally mentioned as "scope creep" seems to be the best candidate to blame. Can you believe that given the importance of requirements specifications, even in these days, IT projects would begin without properly defining them?

3) As a project manager, you are asked to prepare the budget estimate for an IS/IT application for a client for whom a similar IS/IT application was delivered in a different project three years ago. The budget estimate has a short deadline" Given the above, all that is necessary is to look at the cost differentials? Given the experience of the previous project, what needs to be done?

4) As a project manager, you are asked to prepare the budget estimate for an IS/IT application for a client for whom a similar IS/IT application was delivered in a different project three years ago. The budget estimate has a short deadline" What you have discussed may have been the case for the first time when an IT project undergoes budget estimation. But within the same company when a similar project was completed and deliver just 3 years ago, would there be "reinventing the wheel" again?

5) As a project manager, you are asked to prepare the budget estimate for an IS/IT application for a client for whom a similar IS/IT application was delivered in a different project three years ago. The budget estimate has a short deadline Hence, how would your revised discussion look like?