PM chap 5 t/f
12. The scope baseline in a WBS consists of the requirements documentation and enterprise environmental factors.
F
14. A work package represents one component of the product that the project aims to deliver.
F
15. A work package must always represent less than 80 hours of work.
F
16. Given the project management software that is available, it is relatively easy to create a good WBS.
F
17. The tasks in a WBS must be developed as a sequential list of steps.
F
18. The executing tasks of the WBS remain constant from project to project.
F
2. Deliverables are only product-related, such as a piece of hardware or software.
F
21. The format of the WBS dictionary is essentially the same for all projects.
F
5. The project's size, complexity, importance, and other factors do not affect how much effort is spent on collecting requirements for scope planning.
F
7. Project scope statements must include the project boundaries, constraints, and assumptions.
F
8. The scope of a project is clear and specific from the start.
F
1. Scope refers to all the work involved in creating the products of the project and the processes used to create them.
T
10. The project scope statement should reference supporting documents, such as product specifications that will affect what products are produced or purchased, or corporate policies, which might affect how products or services are produced.
T
11. The project management plan, project documents, enterprise environmental factors, and organizational process assets are the primary inputs for creating a WBS.
T
13. The main purpose of the WBS is to define all of the work required to complete a project.
T
19. Many organizations provide different guidelines and templates for developing WBSs.
T
20. Mind mapping allows people to write and even draw pictures of ideas in a nonlinear format.
T
22. A unit of work should appear at only one place in the WBS.
T
23. Scope creep if not managed well can lead to the failure of information technology projects.
T
3. Project scope management includes the processes involved in defining and controlling what is or is not included in a project.
T
4. The scope management plan can be informal and broad or formal and detailed, based on the needs of the project.
T
6. Information from the project charter provides a basis for further defining the project scope.
T
9. Many information technology projects also require detailed functional and design specifications for developing software, which also should be referenced in the detailed scope statement.
T
