![](/olcweb/styles/shared/spacer.gif) |
1 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Effective software project management focuses on |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | people, performance, payoff, product |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | people, product, performance, process |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | people, product, process, project |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | people, process, payoff, product |
|
|
![](/olcweb/styles/shared/spacer.gif) |
2 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Organizations that achieve high levels of maturity in people management have a higher likelihood of implementing effective software engineering processes. |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | True |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | False |
|
|
![](/olcweb/styles/shared/spacer.gif) |
3 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) The first step in project planning is to |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | determine the budget. |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | select a team organizational model. |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | determine the project constraints. |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | establish the objectives and scope. |
|
|
![](/olcweb/styles/shared/spacer.gif) |
4 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Process framework activities are populated with |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | milestones |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | work products |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | QA points |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | all of the above |
|
|
![](/olcweb/styles/shared/spacer.gif) |
5 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Project management is less important for modern software development since most projects are successful and completed on time. |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | True |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | False |
|
|
![](/olcweb/styles/shared/spacer.gif) |
6 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Which of the following is not considered a stakeholder in the software process? |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | customers |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | end-users |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | project managers |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | sales people |
|
|
![](/olcweb/styles/shared/spacer.gif) |
7 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) The best person to hire as a project team leader is the most competent software engineering practitioner available. |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | True |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | False |
|
|
![](/olcweb/styles/shared/spacer.gif) |
8 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) The best project team organizational model to use when tackling extremely complex problems is the |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | closed paradigm |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | open paradigm |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | random paradigm |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | synchronous paradigm |
|
|
![](/olcweb/styles/shared/spacer.gif) |
9 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Which factors should be considered in choosing the organizational structure for a software team? |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | degree of communication desired |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | predicted size of the resulting program |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | rigidity of the delivery date |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | size of the project budget |
| ![](/olcweb/styles/shared/spacer.gif) | E)![](/olcweb/styles/shared/spacer.gif) | a, b, c |
|
|
![](/olcweb/styles/shared/spacer.gif) |
10 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) One of the best ways to avoid frustration during the software development process is to |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | give team members more control over process and technical decisions. |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | give team members less control over process and technical decisions. |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | hide bad news from the project team members until things improve. |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | reward programmers based on their productivity. |
|
|
![](/olcweb/styles/shared/spacer.gif) |
11 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Small agile teams have no place in modern software development. |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | True |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | False |
|
|
![](/olcweb/styles/shared/spacer.gif) |
12 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Which of these software characteristics is not a factor contributing to project coordination difficulties? |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | interoperability |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | performance |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | scale |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | uncertainty |
|
|
![](/olcweb/styles/shared/spacer.gif) |
13 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Which of these software characteristics are used to determine the scope of a software project? |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | context, lines of code, function |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | context, function, communication requirements |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | information objectives, function, performance |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | communications requirements, performance, information objectives |
|
|
![](/olcweb/styles/shared/spacer.gif) |
14 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) The major areas of problem decomposition during the project scoping activity are the |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | customer workflow |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | functionality to be delivered |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | process used to deliver functionality |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | software process model |
| ![](/olcweb/styles/shared/spacer.gif) | E)![](/olcweb/styles/shared/spacer.gif) | b and c |
|
|
![](/olcweb/styles/shared/spacer.gif) |
15 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Product and process decomposition occurs simultaneously as the project plan evolves. |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | True |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | False |
|
|
![](/olcweb/styles/shared/spacer.gif) |
16 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) When can selected common process framework activities be omitted during process decomposition? |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | when the project is extremely small in size |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | any time the software is mission critical |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | rapid prototyping does not require their use |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | never the activities are invariant |
|
|
![](/olcweb/styles/shared/spacer.gif) |
17 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) How does a software project manager need to act to minimize the risk of software failure? |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | double the project team size |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | request a large budget |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | start on the right foot |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | track progress |
| ![](/olcweb/styles/shared/spacer.gif) | E)![](/olcweb/styles/shared/spacer.gif) | c and d |
|
|
![](/olcweb/styles/shared/spacer.gif) |
18 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) The W5HH principle contains which of the following questions? |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | Why is the system being developed? |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | What will be done by whom? |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | Where are they organizationally located? |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | How much of each resource is required? |
| ![](/olcweb/styles/shared/spacer.gif) | E)![](/olcweb/styles/shared/spacer.gif) | a, c d |
|
|
![](/olcweb/styles/shared/spacer.gif) |
19 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Which of these are critical practices for performance-based project management? |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | assessing product usability |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | defect tracking against quality targets |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | empirical cost estimation |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | formal risk management |
| ![](/olcweb/styles/shared/spacer.gif) | E)![](/olcweb/styles/shared/spacer.gif) | b, c, d |
|
|