Exam
Name___________________________________
MULTIPLE CHOICE. Choose the one alternative that best completes the statement or answers the question.
1)
The process of carrying out the project plan is called:
1)
A)
project integration.
B)
project execution.
C)
project administration.
D)
project performance.
Answer:
B
A)
B)
C)
D)
2)
________ involves evaluating project progress on a regular basis in order to determine if the project
will satisfy established quality standards.
2)
A)
Manage project quality
B)
Perform quality control
C)
Monitor progress
D)
Perform quality assurance
Answer:
D
A)
B)
C)
D)
3)
________ is the tendency of systems requirements to change over the lifetime of the development
project.
3)
A)
Scope creep
B)
Feature creep
C)
The silver bullet syndrome
D)
Requirements gold–plating
Answer:
B
A)
B)
C)
D)
4)
What is NOT true about managing change?
4)
A)
Not every request for change results in a change to the requirements.
B)
Most changes will not affect the project deliverables, schedule, and budget.
C)
Every change request should be documented.
D)
Every change will affect the project deliverables, schedule, and budget.
Answer:
B
A)
B)
C)
D)
1
5)
Why is documentation important for a project?
5)
A)
It may be used as a source of best practices to improve other projects.
B)
It provides a record that can be audited or used as part of a legal defense.
C)
It is valuable for the project team in case they need to trace how a decision was made.
D)
All of the above.
Answer:
D
A)
B)
C)
D)
6)
Requirements gold–plating is a ________ system development mistake.
6)
A)
product–related
B)
process–related
C)
technology–related
D)
people–related
Answer:
A
A)
B)
C)
D)
7)
Having overly optimistic schedules is a ________ system development mistake.
7)
A)
process–related
B)
technology–related
C)
product–related
D)
people–related
Answer:
A
A)
B)
C)
D)
8)
Which of the following is NOT an output of project execution?
8)
A)
Implemented corrective actions
B)
implemented quality changes
C)
Implemented change requests
D)
implemented preventive action
Answer:
B
A)
B)
C)
D)
9)
A ________ is a ceremonial meeting marking the beginning of a project in a public way.
9)
A)
project launch meeting
B)
project kickoff meeting
C)
project inauguration meeting
D)
project initiation meeting
Answer:
B
A)
B)
C)
D)
2
10)
Which of the following is NOT part of project integration management?
10)
A)
Develop project schedule
B)
Develop project management plan
C)
Develop project charter
D)
Develop preliminary scope statement
Answer:
A
A)
B)
C)
D)
11)
The silver bullet syndrome is a ________ system development mistake.
11)
A)
product–related
B)
technology–related
C)
people–related
D)
process–related
Answer:
B
A)
B)
C)
D)
12)
Project execution is part of:
12)
A)
project execution management.
B)
project integration management.
C)
project scope management.
D)
project procurement management.
Answer:
B
A)
B)
C)
D)
13)
Which of the following is NOT part of project execution?
13)
A)
Perform quality assurance
B)
Request seller responses
C)
Develop project budget
D)
Develop project team
Answer:
C
A)
B)
C)
D)
14)
________ refers to adding more requirements than necessary to an application, even before the
beginning of a project.
14)
A)
Requirements gold–plating
B)
The silver bullet syndrome
C)
Scope creep
D)
Feature creep
Answer:
A
A)
B)
C)
D)
3
15)
Overestimating savings from new tools or methods is a ________ system development mistake.
15)
A)
process–related
B)
technology–related
C)
people–related
D)
product–related
Answer:
B
A)
B)
C)
D)
16)
Feature creep is a ________ system development mistake.
16)
A)
product–related
B)
people–related
C)
process–related
D)
technology–related
Answer:
A
A)
B)
C)
D)
17)
________ is a problem occurring when developers believe a new and usually untried technology is
all that is needed to cure the ills of any development project.
17)
A)
The silver bullet syndrome
B)
Feature creep
C)
Requirements gold–plating
D)
Scope creep
Answer:
A
A)
B)
C)
D)
18)
All of the following are people–related system development project problems EXCEPT:
18)
A)
unrealistic expectations.
B)
weak personnel.
C)
planning to catch up.
D)
adding people too late to a project.
Answer:
C
A)
B)
C)
D)
19)
Which of the following is an input to project execution?
19)
A)
Project scope statement
B)
Project management plan
C)
Project baseline
D)
Project scope baseline
Answer:
B
A)
B)
C)
D)
4
20)
All of the following are process–related system development project problems EXCEPT:
20)
A)
unrealistic expectations.
B)
overly optimistic schedules.
C)
insufficient planning.
D)
planning to catch up later.
Answer:
A
A)
B)
C)
D)
21)
Having unrealistic expectations is a ________ system development mistake.
21)
A)
technology–related
B)
process–related
C)
people–related
D)
product–related
Answer:
C
A)
B)
C)
D)
22)
Which of the following procurement activities does NOT happen during project execution?
22)
A)
Contract administration
B)
Select sellers
C)
Contract closure
D)
Request seller responses
Answer:
C
A)
B)
C)
D)
SHORT ANSWER. Write the word or phrase that best completes each statement or answers the question.
23)
Project execution is part of project ________ management.
23)
Answer:
integration
24)
________ is valuable for project team members in case they need to trace how a decision
was made.
24)
Answer:
Documentation
25)
________ refers to adding more requirements than necessary to an application, even before
the beginning of a project.
25)
Answer:
Requirements gold–plating
26)
________ is the tendency of systems requirements to change over the lifetime of the
development project.
26)
Answer:
Feature creep
27)
Requirements gold–plating is a ________ system development mistake.
27)
Answer:
product–related
5
28)
Overestimating savings from new tools or methods is a ________ system development
mistake.
28)
Answer:
technology–related
29)
Unrealistic expectations is a ________ system development mistake.
29)
Answer:
people–related
30)
________ is the process of carrying out the project plan.
30)
Answer:
Project execution
31)
Documentation may be used as a source of ________ to improve other projects.
31)
Answer:
best practices
32)
Feature creep is a ________ system development mistake.
32)
Answer:
product–related
33)
The silver bullet syndrome is a ________ system development mistake.
33)
Answer:
technology–related
34)
It is easier to compare reality to expectations when expectations are ________.
34)
Answer:
explicitly defined
35)
Having overly optimistic schedules is a ________ system development mistake.
35)
Answer:
process–related
36)
The ________ is a problem occurring when developers believe a new and usually untried
technology is all that is needed to cure the ills of any development project.
36)
Answer:
silver bullet syndrome
37)
A ________ is a ceremonial meeting marking the beginning of a project in a public way.
37)
Answer:
project kickoff meeting
38)
________ is the process of keeping track of all project tasks and the details surrounding
each one.
38)
Answer:
Monitor progress
6
TRUE/FALSE. Write ‘T’ if the statement is true and ‘F’ if the statement is false.
39)
If something goes wrong during project execution, it helps to adding people late to the project.
39)
Answer:
True
False
40)
Not every request for change results in a change in requirements.
40)
Answer:
True
False
41)
Most project teams are static during a given project.
41)
Answer:
True
False
42)
Requirements gold–plating means that an application may have more requirements than it needs,
even before the development begins.
42)
Answer:
True
False
43)
“Feature creep” refers to the tendency of system requirements to change over the lifetime of the
development project.
43)
Answer:
True
False
44)
Documentation is only used as a source of best practices for other projects.
44)
Answer:
True
False
45)
Changes to an application typically cost 50 to 200 times less if they are made during requirements
determination rather than during the physical design process.
45)
Answer:
True
False
46)
Using new technologies can usually help to bring a project back on track, even if the technologies
haven’t been tried before.
46)
Answer:
True
False
47)
The kickoff meeting does not have to be a big party.
47)
Answer:
True
False
48)
For IT projects, execution is where the system is developed and released.
48)
Answer:
True
False
49)
Requests for minor changes don’t have to be formally reviewed before they are implemented.
49)
Answer:
True
False
7
50)
The average project may see a 10% change in requirements.
50)
Answer:
True
False
51)
During the project kickoff meeting, much of the most important work gets started.
51)
Answer:
True
False
52)
Reports about the project and its progress should be written, rather than oral, and regular, rather
than ad hoc.
52)
Answer:
True
False
ESSAY. Write your answer in the space provided or on a separate sheet of paper.
53)
What is a kickoff meeting and how/why is it held?
Answer:
The project kickoff meeting is largely ceremonial. It is important because it marks the beginning of a
project in a public and memorable way. Sometimes a project kickoff can be quite an elaborate affair, with
food and live music and gifts and decorations. The kickoff does not always have to be a big party.
Sometimes it is a simple meeting where the project team meets with the project sponsor, who explains
what is involved and what is expected for the project. Who attends the kickoff sends a strong signal to the
project team and the company as a whole as to how important the project is. For example, if the chief
executive officer and the company president both attend the kickoff, everyone knows this project is
important to the entire organization. Whatever form the kickoff takes, it should be something special and
out of the ordinary that signifies the start of a dedicated group effort. Just how elaborate the kickoff is
depends on the style of the project manager and the budget for the project, too.
54)
Compare and contrast “feature creep” and “requirements gold–plating.”
Answer:
Feature creep refers to the tendency of system requirements to change over the lifetime of the
development project. It’s called feature creep because more and more features that were not in the
original specifications for the application “creep in” during the development process. The average project
may see a 25 percent change in requirements, all of which can delay the project and add costs. Changes to
an application typically cost 50 to 200 times less if they are made during requirements determination
rather than during the physical design process. Requirements gold–plating means an application may
have more requirements than it needs, even before the development project begins. In addition to being
unnecessary, many of these requirements can be extreme and complex.
8