100%(24)24 out of 24 people found this document helpful
This preview shows page 1 - 4 out of 14 pages.
Chapter 3: Planning the ProjectTrue/False1. Defining resource needs is not necessary on small projects.Response: See page 81Level: medium2. A representative of senior management should be invited to the project launch meeting.Response: See page 85Level: medium3. The primary purpose of the launch meeting is to develop the project plan and budget.Response: See pages 85 and 86Level: medium4.When planning, it is best for the project manager to breakdown and define the different levels of the project plan.Response: See page 87Level: medium5. The initial project meeting is just to coordinate the project, so areas of responsibility do not need to be discussed.
Response: See page 85Level: medium6. The project plan should begin with a complete description of all agreements made with the client or any third party.Response: See page 80Level: medium7. As a rule of thumb, the lowest level tasks in a typical project should not take longer than two days to complete.Response: See page 87Level: medium8. The start and finish date of a project must be specified before the action plan canbe completed.Response: See page 93Level: medium9. Procedures for monitoring, collecting, and storing data on project performance should be discussed in the Schedules section of the project master plan.Response: See page80Level: medium
10. The details of the project work force are discussed in the Resource Requirementssection of the project master plan.Response: See page 78Level: medium11. It is acceptable to restrict the launch meeting to brainstorming a problem.Response: See page 82Level: medium12. The action plan should identify the project’s deliverable.Response: See page 82Level: easy13. It is not possible to overdo it when it comes to project planning.Response: See page 79Level: medium14.Predecessors must be listed in the WBS because they are critical for scheduling.Response: See page 90Level: easy