A. Product risk
B. Project risk
C. Business risk
D. Programming risk
Explanation: Risks that affect the quality or performance of the software being developed.
A. Performance risk
B. Cost risk
C. Support risk
D. Schedule risk
A. Staff turnover
B. Technology change
C. Management change
D. Product competition
A. Business impact risks
B. Process definition risks
C. Product size risks
D. Development environment risks
A. Risk identification
B. Performance risk
C. Support risk
D. Risk projection
Explanation: By identifying known and predictable risks, the project manager takes a first step toward avoiding them when possible and controlling them when necessary.
A. Known risks
B. Business risks
C. Project risks
D. Technical risks
Explanation: Technical risks identify potential design, implementation, interface, verification, and maintenance problems.
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
Explanation: This is not considered as a business risk.
A. Business impact risks
B. Process definition risks
C. Product size risks
D. Development environment risks
A. Known risks
B. Business risks
C. Project risks
D. Technical risks
Explanation: Business risks often jeopardize the project or the product
A. Risk exposure
B. Risk prioritization
C. Risk analysis
D. All of the mentioned