A) people, performance, payoff, product
B) people, product, performance, process
C) people, product, process, project
D) people, process, payoff, product
A) determine the budget.
B) select a team organizational model.
C) determine the project constraints.
D) establish the objectives and scope.
B) work products
C) QA points
D) All of the above
C) project managers
D) sales people
A) closed paradigm
B) open paradigm
C) random paradigm
D) synchronous paradigm
A) degree of communication desired
B) predicted size of the resulting program
C) rigidity of the delivery date
D) size of the project budget
A) give team members more control over process and technical decisions.
B) give team members less control over process and technical decisions.
C) hide bad news from the project team members until things improve.
D) reward programmers based on their productivity.
A) context, lines of code, function
B) context, function, communication requirements
C) information objectives, function, performance
D) communications requirements, performance, information objectives
A) customer workflow
B) functionality to be delivered
C) process used to deliver functionality
D) software process model
A) when the project is extremely small in size
B) any time the software is mission critical
C) rapid prototyping does not require their use
D) never—the activities should always occur
A) double the project team size
B) request a large budget
C) start on the right foot
D) track progress
A) Why is the system being developed?
B) What will be done by whom?
C) Where are they organizationally located?
D) How much of each resource is required?
A) assessing product usability
B) defect tracking against quality targets
C) empirical cost estimation
D) formal risk management
E) b, c, and d