adplus-dvertising
frame-decoration

Question

How can cost estimates be used for type of project where the product certainty, process certainty and resource certainty are all low?

a.

As a fixed anchor point for finishing the project and determining the cost

b.

As a rough guide for the magnitude of the project

c.

As a sensitivity analysis for cost drivers

d.

To allocate effort and time for the project

Posted under Software Engineering

Answer: (b).As a rough guide for the magnitude of the project Explanation:In a project where the product certainty, process certainty and resource certainty are all low, cost estimation using formalized models is not feasible. Use of such models presupposes that we know enough about project at hand to be able to compare it with previous projects, but in this type of project, this is not the case. Instead, we may rely on expert judgments to achieve a rough cost estimate. However, this estimate should not be used as a fixed anchor point as to when project should be finished and how much it may cost, as there are too many uncertainties involved. Rather, it provides us with some guidance as to the magnitude of project. Based on this estimate, effort and time can be allocated for the project, for instance to produce a certain no. of prototypes, a feasibility study, a pilot implementation of part of product, or to start a certain number of time boxes. The hope is that in time the uncertainties will diminish sufficiently so that project shifts to one of the other situations.

Engage with the Community - Add Your Comment

Confused About the Answer? Ask for Details Here.

Know the Explanation? Add it Here.

Q. How can cost estimates be used for type of project where the product certainty, process certainty and resource certainty are all low?

Similar Questions

Discover Related MCQs

Q. What is the recommended approach for coordinating work at the macro level in big projects?

Q. Is it recommended to use the same control mechanisms at the macro and micro level in big projects?

Q. What are the consequences of neglecting project-specific characteristics during the planning stage of a software development project?

Q. What is the goal of tailoring the project's management to the situation at hand?

Q. What is the control situation that involves the most uncertainty?

Q. What is the main focus of the risk management in software development?

Q. What is a common attitude towards risks in software development?

Q. What is the recommended approach for dealing with risks in a software project?

Q. What is the difference between a risk and a problem?

Q. What is the importance of identifying risks early on in a software development project?

Q. How can unstable, immature, unrealistic, or excessive requirements be dealt with as a risk in a software development project?

Q. What is a common way to deal with communication problems when a project involves more than one development site?

Q. What are the three general strategies to mitigate risks?

Q. What is the process of determining the risk exposure?

Q. What is the final step in risk management?

Q. What is the main goal of risk management?

Q. What is the risk exposure of a risk?

Q. How often should the risk management process be carried out?

Q. What are the four types of risks identified by Wallace and Keil (2004)?

Q. What is the first step in risk management strategy?