Chapter 12: Project Communication and Documentation
84. Teleconferencing can help facilitate the sharing of information in a more interactive way than perhaps email.
a. True
b. False
85. body language can include direct eye contact, a smile, hand gestures, leaning forward, and
nodding acknowledgment or agreement.
a. Neutral
b. Negative
c. Critical
d. Positive
86. body language can be a frown, crossed arms, slouching, fidgeting, gazing or looking away, doodling, or
yawning.
a. Neutral
b. Negative
c. Critical
d. Positive
Chapter 12: Project Communication and Documentation
87. The heart of communication is not words, but
a. listening.
b. responding.
c. understanding.
d. talking.
88. Half of making communication effective is
a. listening.
b. responding.
c. understanding.
d. talking.
Chapter 12: Project Communication and Documentation
89. All of the following are barriers to effective listening except
a. pretending to listen.
b. patience.
c. bias and closed-mindedness.
d. jumping to conclusions.
90. Listening is more than just letting the other person talk. It must be
a. a passive, not an active, process.
b. an impatient, not a patient, process.
c. an reactive, not a proactive, process.
d. an active, not a passive, process.
Chapter 12: Project Communication and Documentation
91. All of the following are suggestions for improving listening skills except
a. focus on the person talking.
b. interrupt the speaker to state clarification.
c. engage in active listening, provide verbal and nonverbal feedback to the person talking.
d. ask questions.
92. A project status review meeting is usually led or called by
a. the project team.
b. the team member that identified a problem.
c. the project manager.
d. the customer.
Chapter 12: Project Communication and Documentation
93. The primary purposes of a are to inform, to identify problems, and to identify action items.
a. project status review meeting
b. problem-solving meeting
c. design review meeting
d. post–project evaluation meeting
94. should be held on a regularly scheduled basis.
a. Project status review meetings
b. Problem–solving meetings
c. Design review meetings
d. Post–project evaluation meetings
Chapter 12: Project Communication and Documentation
95. When a problem or potential problem is identified by an individual project team member, that person
should promptly call a with other appropriate individuals, not wait for a future status review meeting.
a. project status review meetings
b. problem–solving meetings
c. design review meetings
d. post–project evaluation meetings
96. Projects that involve a design phase, such as an information system project, may require one or more technical
to ensure that the customer agrees with or approves of the design.
a. project status review meetings
b. problem–solving meetings
c. design review meetings
d. post–project evaluation meetings
Chapter 12: Project Communication and Documentation
97. A preliminary when the contractor has completed the initial conceptual specifications, drawings, or
flowcharts. The purpose of this preliminary design review meeting is to get the customer’s agreement.
a. project status review meetings
b. problem–solving meetings
c. design review meetings
d. post–project evaluation meetings
98. A final when the contractor has completed the detailed specifications, drawings, screen and report
formats, and such. The purpose of this final design review meeting is to gain approval from the customer.
a. project status review meetings
b. problem–solving meetings
c. design review meetings
d. post–project evaluation meetings
Chapter 12: Project Communication and Documentation
99. Before a project team meeting, the should determine whether a meeting is really necessary, the purpose
of the meeting, and who needs to participate in the meeting.
a. the project team
b. the team member that identified a problem
c. the project manager
d. the customer
Chapter 12: Project Communication and Documentation
100. After the meeting, the project manager should publish the meeting results
a. within 24 hours after the meeting.
b. by the end of the week.
c. before the next meeting.
d. if the project manager has time to send the notes.
101. Use the 3-T approach in your presentation which includes all the following except
a. thank them for coming to the presentation.
b. tell them what you are going to tell them.
c. tell them what you told them.
d. tell them.
Chapter 12: Project Communication and Documentation
102. Written reports are verbal reports in communicating information about a project.
a. just as important as
b. not as important as
c. more important than
d. less effective than
103. It is important to keep in mind that a progress report is not
a. a list of completed milestones.
b. an activity report.
c. the current status of project performance.
d. a list of milestones expected to be achieved by the next meeting.
Chapter 12: Project Communication and Documentation
104. A project progress report might include the following except
a. accomplishments since prior report and milestones expected to be reached during next reporting period.
b. progress toward resolution of previously identified problems.
c. problems or potential problems since prior report and planned corrective actions.
d. list of activities completed by each of the project team members.
Chapter 12: Project Communication and Documentation
105. The final report might include the following except
a. a statement of the customer’s original need, project objective, and original requirements.
b. a description of the project and degree to which the original project objective was met.
c. the actual versus anticipated benefits to the customer as a result of the project and a list of all deliverables
provided to the customer.
d. personal accomplishments of the project team members.