A. Building an excellent product or system that no one really wants
B. Losing the support of senior management due to a change in focus or change in people
C. Lack of documented requirements or software scope
D. Losing budgetary or personnel commitment
A. Known risks
B. Business risks
C. Project risks
D. Technical risks
A. Risk identification
B. Performance risk
C. Support risk
D. Risk projection
A. Business impact risks
B. Process definition risks
C. Product size risks
D. Development environment risks
A. Staff turnover
B. Technology change
C. Management change
D. Product competition
A. Performance risk
B. Cost risk
C. Support risk
D. Schedule risk
A. Product risk
B. Project risk
C. Business risk
D. Programming risk
A. Managerial risks
B. Technology risks
C. Estimation risks
D. Organizational risks
A. Avoidance strategies
B. Minimization strategies
C. Contingency plans
D. All of the mentioned
A. Software project estimation is a form of problem solving
B. Developing a cost and effort estimate for a software project is too complex
C. All of the mentioned
D. None of the mentioned