PM: Chapter 5
Many information technology projects also require detailed functional and design specifications for developing software, which also should be referenced in the detailed scope statement.
True
Mind mapping allows people to write and even draw pictures of ideas in a nonlinear format.
True
Project scope management includes the processes involved in defining and controlling what is or is not included in a project.
True
7. The main outputs of scope definition are the _____ and project document updates.
ANS: project scope statement
10. The _____ includes the approved project scope statement and its associated WBS and WBS dictionary.
ANS: scope baseline
8. The scope of a project is clear and specific from the start.
FALSE
12. The scope baseline in a WBS consists of the requirements documentation and enterprise environmental factors.
FALSE The scope baseline includes the approved project scope statement and its associated WBS and WBS dictionary.
63. Some organizations prescribe the form and content for WBSs for particular projects. These are known as _____.
guidelines
33. A(n) _____ is a deliverable-oriented grouping of the work involved in a project that defines the total scope of the project.
work breakdown structure
In the WBS, the name of the entire project is the top box, called Level ____. a. 0 c. 2 b. 1 d. 3
1
In the WBS, the main groupings for the work are listed in Level ____. a. 0 c. 2 b. 1 d. 3
2
21. A unit of work should appear at only one place in the WBS.
: TRUE A basic principle of creating a good WBS and its WBS dictionary is that a unit of work should appear at only one place in the WBS.
A(n) _____ is a table that lists requirements, their various attributes, and the status of the requirements to ensure that all are addressed. a. requirements traceability matrix b. Gantt chart c. state transition table d. entity-attribute-value model
A
73. List and briefly describe the six main processes involved in project scope management.
1. Planning scope management involves determining how the project's scope and requirements will be managed. The project team works with appropriate stakeholders to create a scope management plan and requirements management plan. 2. Collecting requirements involves defining and documenting the features and functions of the products produced during the project as well as the processes used for creating them. The project team creates stakeholder requirements documentation, a requirements management plan, and a requirements traceability matrix as outputs of the requirements collection process. 3. Defining scope involves reviewing the project charter, requirements documents, and organizational process assets to create a scope statement, adding more information as requirements are developed and change requests are approved. The main outputs of scope definition are the project scope statement and updates to project documents. 4. Creating the WBS involves subdividing the major project deliverables into smaller, more manageable components. The main outputs include a work breakdown structure, a WBS dictionary, a scope baseline, and updates to project documents. 5. Verifying scope involves formalizing acceptance of the project deliverables. Key project stakeholders, such as the customer and sponsor for the project, inspect and then formally accept the deliverables during this process. If the deliverables are not acceptable, the customer or sponsor usually requests changes. The main outputs of this process, therefore, are accepted deliverables, change requests, work performance information, and updates to project documents. 6. Controlling scope involves controlling changes to project scope throughout the life of the project—a challenge on many information technology projects. Scope changes often influence the team's ability to meet project time and cost goals, so project managers must carefully weigh the costs and benefits of scope changes. The main outputs of this process are work performance information, change requests, and updates to the project management plan, project documents, and organizational process assets.
Creating the WBS is a subprocess associated with the _____ process in project scope management. a. planning b. monitoring and controlling c. closing d. executing
A
Scope creep refers to: a. the tendency for project scope to keep getting bigger and bigger. b. subdividing project deliverables into smaller pieces. c. the approved project scope statement and its associated WBS. d. a task at the lowest level of the WBS.
A
____ refers to the process of developing a working replica of the system or some aspect of the system. a. Prototyping b. Variance c. Decomposition d. Use case modeling
A
_____ involves defining and documenting the features and functions of the products produced during the project as well as the processes used for creating them. a. Collecting requirements b. Defining scope c. Controlling scope d. Validating scope
A
_____ involves formal acceptance of the completed project scope by the stakeholders. a. Scope validation b. Scope planning c. Scope control d. Scope baseline
A
9. A(n) _____ is a table that lists requirements, their various attributes, and the status of the requirements to ensure that all are addressed. a. requirements traceability matrix b. Gantt chart c. state transition table d. entity-attribute-value model
A A requirements traceability matrix (RTM) is a table that lists requirements, their various attributes, and the status of the requirements to ensure that all are addressed.
3. _____ involves defining and documenting the features and functions of the products produced during the project as well as the processes used for creating them. a. Collecting requirements b. Defining scope c. Controlling scope d. Validating scope
A Collecting requirements involves defining and documenting the features and functions of the products for the project as well as the processes used for creating them. The project team creates requirements documentation and a requirements traceability matrix as outputs of the requirements collection process.
6. Creating the WBS is a subprocess associated with the _____ process in project scope management. a. planning b. monitoring and controlling c. closing d. executing
A Creating the WBS is a subprocess associated with the planning process of the project scope management.
. 23. _____ refers to the process of developing a working replica of the system or some aspect of the system. a. Prototyping b. Variance c. Decomposition d. Use case modeling
A Prototyping involves developing a working replica of the system or some aspect of the system.
20. Scope creep refers to: a. the tendency for project scope to keep getting bigger and bigger. b. subdividing project deliverables into smaller pieces. c. the approved project scope statement and its associated WBS. d. a task at the lowest level of the WBS.
A Scope creep refers to the tendency for project scope to keep getting bigger and bigger.
21. _____ involves formal acceptance of the completed project scope by the stakeholders. a. Scope validation b. Scope planning c. Scope control d. Scope baseline
A Scope validation involves formal acceptance of the completed project deliverables. This acceptance is often achieved by a customer inspection and then sign-off on key deliverables.
43. Which of the following is recommended for the creation of a good WBS?
A unit of work should appear at only one place in the WBS.
74. What is a work breakdown structure? What are the inputs and tools used for creating one?
A work breakdown structure (WBS) is a deliverable-oriented grouping of the work involved in a project that defines the total scope of the project. Because most projects involve many people and many different deliverables, it is important to organize and divide the work into logical parts based on how the work will be performed. The WBS is a foundation document in project management because it provides the basis for planning and managing project schedules, costs, resources, and changes. Since the WBS defines the total scope of the project, some project management experts believe that work should not be done on a project if it is not included in the WBS. Therefore, it is crucial to develop a good WBS. The project scope statement, stakeholder requirements documentation, and organizational process assets are the primary inputs for creating a WBS. The main tool or technique is decomposition, that is, subdividing project deliverables into smaller pieces. The outputs of the process of creating the WBS are the WBS itself, the WBS dictionary, a scope baseline, and project document updates.
Work package
A(n) ____ is a task at the lowest level of the WBS.
work package
A(n) ____ is a task at the lowest level of the WBS.
Work breakdown structure
A(n) _____ is a deliverable-oriented grouping of the work involved in a project that defines the total scope of the project.
Requirements traceability matrix
A(n) _____ is a table that lists requirements, their various attributes, and the status of the requirements to ensure that all are addressed.
8. A(n) _____ is a deliverable-oriented grouping of the work involved in a project that defines its total scope.
ANS: WBS work breakdown structure
4. Creating the _____ involves subdividing the major project deliverables into smaller, more manageable components.
ANS: WBS work breakdown structure work breakdown structure (WBS) WBS (work breakdown structure)
6. A(n) _____ is a table that lists requirements, their various attributes, and the status of the requirements to ensure that all are addressed.
ANS: requirements traceability matrix requirements traceability matrix (RTM) RTM
18. The _____ technique for creating a WBS uses branches radiating from a core idea to structure thoughts and ideas instead of writing down tasks in a list or immediately trying to create a structure for tasks. a. analogy b. bottom-up c. top-down d. mind mapping
ANS: D Mind mapping is a technique that uses branches radiating from a core idea to structure thoughts and ideas.Instead of writing down tasks in a list or immediately trying to create a structure for tasks, mind mapping allows people to write and even draw pictures of ideas in a nonlinear format.
16. _____ is a technique that uses branches radiating out from a core idea to structure thoughts and ideas when creating a WBS.
ANS: Mind mapping
1. _____ includes the processes involved in defining and controlling what work is or is not included in a project.
ANS: Project scope management
22. _____ involves developing a working replica of the system or some aspect of the system.
ANS: Prototyping
5. _____ refer to "conditions or capabilities that must be met by the project or present in the product, service, or result to satisfy an agreement or other formally imposed specification."
ANS: Requirements
2. _____ refers to all the work involved in creating the products of the project and the processes used to create them.
ANS: Scope
20. _____ involves controlling changes to the project scope while keeping project goals and business strategy in mind.
ANS: Scope control
18. _____ is the tendency for project scope to keep getting bigger and bigger.
ANS: Scope creep
23. _____ is a process for identifying and modeling business events, who initiated them, and how the system should respond to them.
ANS: Use case modeling
21. _____ is the difference between planned and actual performance.
ANS: Variance
17. A(n) _____ is a document that describes detailed information about each WBS item.
ANS: WBS dictionary
15. In the _____ approach to creating a WBS, team members first identify as many specific tasks related to the project as possible.
ANS: bottom-up
9. Subdividing the project deliverables into smaller pieces is known as _____.
ANS: decomposition
14. Some organizations prescribe the form and content for WBSs for particular projects. These are known as _____.
ANS: guidelines
19. The main tool for performing scope validation is _____ and group decision making techniques
ANS: inspection
13. A work package is a task at the _____ level of the WBS.
ANS: lowest
3. The main outputs of _____are the project scope statement and updates to project documents.
ANS: scope definition
11. Tasks in a WBS that are decomposed into smaller tasks are called _____ tasks.
ANS: summary
12. PMI uses the term "_____" to describe each level of work in the WBS.
ANS: task
Generating ideas by comparing specific project practices or product characteristics to those of other projects or products inside or outside the performing organization is known as _____. a. variance b. benchmarking c. prototyping d. decomposition
B
In the _____ approach, team members first identify as many specific tasks related to the project as possible and then aggregate the specific tasks and organize them into summary activities, or higher levels in the WBS. a. analogy b. bottom-up c. top-down d. mind mapping
B
The _____ should list and describe all of the deliverables required for the project. a. project charter b. scope statement c. WBS d. Gantt chart
B
The ______ documents how project needs will be analyzed, documented, and managed. a. requirements traceability matrix b. requirements management plan c. WBS d. project scope statement
B
Which of the following is recommended for the creation of a good WBS? a. Any WBS item should be the responsibility of all the people working on it. b. A unit of work should appear at only one place in the WBS. c. Each WBS item should be created assuming that the requirements are inflexible. d. The work content of a WBS item is independent of the WBS items below it.
B
_____ involves reviewing the project charter, requirements documents, and organizational process assets to create a scope statement, adding more information as requirements are developed and change requests are approved. a. Creating scope b. Defining scope c. Controlling scope d. Validating scope
B
_____ refers to the difference between planned and actual performance. a. Decomposition b. Variance c. Scope validation d. Scope creep
B
_____ uses highly organized and intensive workshops to bring together project stakeholders—the sponsor, users, business analysts, programmers, and so on—to jointly define and design information systems. a. Prototyping b. JAD c. RAD d. Use case modeling
B
8. Generating ideas by comparing specific project practices or product characteristics to those of other projects or products inside or outside the performing organization is known as _____. a. variance b. benchmarking c. prototyping d. decomposition
B Benchmarking, or generating ideas by comparing specific project practices or product characteristics to those of other projects or products inside or outside the performing organization, can be used to collect requirements.
4. _____ involves reviewing the project charter, requirements documents, and organizational process assets to create a scope statement, adding more information as requirements are developed and change requests are approved. a. Creating scope b. Defining scope c. Controlling scope d. Validating scope
B Defining scope involves reviewing the scope management plan, project charter, requirements documents, and organizational process assets to create a scope statement, adding more information as requirements are developed and change requests are approved.
17. In the _____ approach, team members first identify as many specific tasks related to the project as possible and then aggregate the specific tasks and organize them into summary activities, or higher levels in the WBS. a. analogy b. bottom-up c. top-down d. mind mapping
B In the bottom-up approach, team members first identify as many specific tasks related to the project as possible. They then aggregate the specific tasks and organize them into summary activities, or higher levels in the WBS. Project managers often use the bottom-up approach for projects that represent entirely new systems or approaches to doing a job, or to help create buy-in and synergy with a project team.
25. _____ uses highly organized and intensive workshops to bring together project stakeholders—the sponsor, users, business analysts, programmers, and so on—to jointly define and design information systems. a. Prototyping b. JAD c. RAD d. Use case modeling
B Joint Application Design (JAD) uses highly organized and intensive workshops to bring together project stakeholders — the sponsor, users, business analysts, programmers, and so on —to jointly define and design information systems.
19. Which of the following is recommended for the creation of a good WBS? a. Any WBS item should be the responsibility of all the people working on it. b. A unit of work should appear at only one place in the WBS. c. Each WBS item should be created assuming that the requirements are inflexible. d. The work content of a WBS item is independent of the WBS items below it.
B Some basic principles apply to creating any good WBS and its WBS dictionary. Firstly, a unit of work should appear at only one place in the WBS. The work content of a WBS item is the sum of the WBS items below it.
7. The ______ documents how project needs will be analyzed, documented, and managed. a. requirements traceability matrix b. requirements management plan c. WBS d. project scope statement
B The requirements management plan documents how project requirements will be analyzed, documented, and managed.
13. The _____ should list and describe all of the deliverables required for the project. a. project charter b. scope statement c. WBS d. Gantt chart
B The scope statement should list and describe all of the deliverables required for the project. It is very important to ensure consistency between the project charter, scope statement, WBS, and Gantt chart to define the scope of the project accurately.
22. _____ refers to the difference between planned and actual performance. a. Decomposition b. Variance c. Scope validation d. Scope creep
B Variance is the difference between planned and actual performance
Mind mapping can be used for developing WBSs using a. the analogy approach only b. the bottom-up or analogy approach c. the top-down or bottom-up approach d. any approach
C
The _____ approach for constructing a WBS starts with the largest items of the project and breaks them into subordinate items. a. analogy b. bottom-up c. top-down d. mind mapping
C
The main technique used in creating a WBS is _____, which involves subdividing project deliverables into smaller pieces. a. conglomeration b. accumulation c. decomposition d. catalyzation
C
The term ______ describes a product produced as part of a project. a. variance b. scope c. deliverable d. work package
C
11. The main technique used in creating a WBS is _____, which involves subdividing project deliverables into smaller pieces. a. conglomeration b. accumulation c. decomposition d. catalyzation
C The main tool or technique involved in creating a WBS is decomposition—that is, subdividing project deliverables into smaller pieces.
1. The term ______ describes a product produced as part of a project. a. variance b. scope c. deliverable d. work package
C Thee term deliverable describes a product created as part of a project. Deliverables can be product related, such as a piece of hardware or software, or process-related, such as a planning document or meeting minutes.
16. The _____ approach for constructing a WBS starts with the largest items of the project and breaks them into subordinate items. a. analogy b. bottom-up c. top-down d. mind mapping
C To use the top-down approach, start with the largest items of the project and break them into subordinate items.The top-down approach is best suited to project managers who have vast technical insight and a big-picture perspective.
15. The _____ approach for constructing a WBS involves refining the work into greater and greater levels of detail. a. analogy b. bottom-up c. top-down d. mind mapping
C To use the top-down approach, start with the largest items of the project and break them into subordinate items. This process involves refining the work into greater and greater levels of detail.
26. _____ involves defining and documenting the features and functions of the products produced during the project as well as the processes used for creating them.
Collecting requirements
____ involves defining and documenting the features and functions of the products produced during the project as well as the processes used for creating them. a. Collecting requirements c. Controlling scope b. Defining scope d. Verifying scope
Collecting requirements
____ involves controlling changes to project scope throughout the life of the project, which is a challenge on many information technology projects. a. Planning scope c. Controlling scope b. Defining scope d. Verifying scope
Controlling scope
Planning
Creating the WBS is a subprocess associated with the _____ process in project scope management.
planning
Creating the WBS is a subprocess associated with the _____ process in project scope management.
A(n) ____ is a task at the lowest level of the WBS. a. variance b. objective c. deliverable d. work package
D
A(n) _____ is a deliverable-oriented grouping of the work involved in a project that defines the total scope of the project. a. project charter b. business case c. project scope statement d. work breakdown structure
D
In the _____approach for constructing a WBS, you use a similar project's WBS as a starting point. a. top-down b. bottom-up c. mind-mapping d. analogy
D
Scope refers to: a. each level of work that is outlined in a work breakdown structure. b. the end product created as part of a project that is delivered to the client. c. tasks that are decomposed into smaller tasks in a work breakdown structure. d. the work involved in creating the products and the processes used to create them.
D
The _____ technique for creating a WBS uses branches radiating from a core idea to structure thoughts and ideas instead of writing down tasks in a list or immediately trying to create a structure for tasks. a. analogy b. bottom-up c. top-down d. mind mapping
D
_____ involves formalizing acceptance of the project deliverables and during this phase the key project stakeholders, such as the customer and sponsor for the project, inspect and then formally accept the deliverables. a. Creating scope b. Defining scope c. Controlling scope d. Validating scope
D
_____ is a process for identifying and modeling business events, who initiated them, and how the system should respond to them. a. Prototyping b. JAD c. RAD d. Use case modeling
D
14. In the _____approach for constructing a WBS, you use a similar project's WBS as a starting point. a. top-down b. bottom-up c. mind-mapping d. analogy
D A method for constructing a WBS is the analogy approach. In the analogy approach, you use a similar project's WBS as a starting point.
12. A(n) ____ is a task at the lowest level of the WBS. a. variance b. objective c. deliverable d. work package
D A work package is a task at the lowest level of the WBS.
10. A(n) _____ is a deliverable-oriented grouping of the work involved in a project that defines the total scope of the project. a. project charter b. business case c. project scope statement d. work breakdown structure
D After collecting requirements and defining scope, the next step in project scope management is to create a work breakdown structure. A work breakdown structure (WBS) is a deliverable oriented grouping of the work involved in a project that defines its total scope
2. Scope refers to: a. each level of work that is outlined in a work breakdown structure. b. the end product created as part of a project that is delivered to the client. c. tasks that are decomposed into smaller tasks in a work breakdown structure. d. the work involved in creating the products and the processes used to create them.
D Scope refers to all the work involved in creating the products of the project and the processes used to create them.
24. _____ is a process for identifying and modeling business events, who initiated them, and how the system should respond to them. a. Prototyping b. JAD c. RAD d. Use case modeling
D Use case modeling is a process for identifying and modeling business events, who initiated them, and how the system should respond to them. It is an effective tool for understanding requirements of information systems.
5. _____ involves formalizing acceptance of the project deliverables and during this phase the key project stakeholders, such as the customer and sponsor for the project, inspect and then formally accept the deliverables. a. Creating scope b. Defining scope c. Controlling scope d. Validating scope
D Validating scope involves formalizing acceptance of the project deliverables. Key project stakeholders, such as the customer and sponsor for the project, inspect and then formally accept the deliverables during this process.
27. _____ involves reviewing the project charter, requirements documents, and organizational process assets to create a scope statement, adding more information as requirements are developed and change requests are approved.
Defining scope
____ involves reviewing the project charter, requirements documents, and organizational process assets to create a scope statement, adding more information as requirements are developed and change requests are approved. a. Planning scope c. Controlling scope b. Defining scope d. Verifying scope
Defining scope
12. The scope baseline in a WBS consists of the requirements documentation and enterprise environmental factors.
FALSE
13. The WBS is organized solely around project phases.
FALSE
14. A work package represents one component of the product that the project aims to deliver.
FALSE
15. A work package must always represent less than 80 hours of work.
FALSE
16. Given the project management software that is available, it is relatively easy to create a good WBS.
FALSE
17. The tasks in a WBS must be developed as a sequential list of steps.
FALSE
18. The executing tasks of the WBS remain constant from project to project.
FALSE
2. Deliverables are only product-related, such as a piece of hardware or software.
FALSE
21. The format of the WBS dictionary is essentially the same for all projects.
FALSE
5. The project's size, complexity, importance, and other factors do not affect how much effort is spent on collecting requirements for scope planning.
FALSE
7. Project scope statements must include the project boundaries, constraints, and assumptions.
FALSE
16. The tasks in a WBS must be developed as a sequential list of steps.
FALSE A concern when creating a WBS is how to organize it to provide the basis for the project schedule. You should focus on what work needs to be done and how it will be done, not when it will be done. In other words, the tasks do not have to be developed as a sequential list of steps.
13. The WBS is organized solely around project phases.
FALSE A project team often organizes the WBS around project products, project phases, or the project management process groups.
14. A work package represents one component of the product that the project aims to deliver.
FALSE A work package is a task at the lowest level of the WBS. It represents the level of work that the project manager monitors and controls.
15. A work package must always represent less than 80 hours of work.
FALSE A work package represents the level of work that the project manager monitors and controls. If a project has a relatively short time frame and requires weekly progress reports, a work package might represent work completed in one week or less. If a project has a very long time frame and requires quarterly progress reports, a work package might represent work completed in one month or more.
8. The scope of a project is clear and specific from the start.
FALSE As time progresses, the scope of a project should become more clear and specific.
2. Deliverables are only product-related, such as a piece of hardware or software.
FALSE Deliverables can be product-related, such as a piece of hardware or software, or process-related, such as a planning document or meeting minutes.
7. Project scope statements must include the project boundaries, constraints, and assumptions.
FALSE Project scope statements should include at least a product scope description, product user acceptance criteria, and detailed information on all project deliverables. It is also helpful to document other scope-related information, such as the project boundaries, constraints, and assumptions.
17. The executing tasks of the WBS remain constant from project to project.
FALSE The executing tasks vary the most from project to project, but many of the tasks under the other project management process groups would be similar for all projects.
5. The project's size, complexity, importance, and other factors do not affect how much effort is spent on collecting requirements for scope planning.
FALSE The project's size, complexity, importance, and other factors affect how much effort is spent on collecting requirements.
20. The format of the WBS dictionary is essentially the same for all projects.
FALSE WBS dictionary is a document that provides detailed information about each WBS item. The format of the WBS dictionary can vary based on project needs.
A project team always organizes the WBS around project products.
False
A work package must always represent less than 80 hours of work. a. True b. False
False
A work package represents one component of the product that the project aims to deliver. a. True b. False
False
Deliverables are only product-related, such as a piece of hardware or software. a. True b. False
False
Given the project management software that is available, it is relatively easy to create a good WBS. a. True b. False
False
Project scope statements must include the project boundaries, constraints, and assumptions. a. True b. False
False
The WBS is organized solely around project phases. a. True b. False
False
The executing tasks of the WBS remain constant from project to project. a. True b. False
False
The project's size, complexity, importance, and other factors do not affect how much effort is spent on collecting requirements for scope planning. a. True b. False
False
The scope baseline in a WBS consists of the requirements documentation and enterprise environmental factors. a. True b. False
False
The scope of a project is clear and specific from the start. a. True b. False
False
The tasks in a WBS must be developed as a sequential list of steps. a. True b. False
False
Benchmarking
Generating ideas by comparing specific project practices or product characteristics to those of other projects or products inside or outside the performing organization is known as _____.
49. _____ uses highly organized and intensive workshops to bring together project stakeholders—the sponsor, users, business analysts, programmers, and so on—to jointly define and design information systems.
JAD
65. _____ is a technique that uses branches radiating out from a core idea to structure thoughts and ideas when creating a WBS.
Mind mapping
50. _____ includes the processes involved in defining and controlling what work is or is not included in a project.
Project scope management
47. _____ refers to the process of developing a working replica of the system or some aspect of the system.
Prototyping
71. _____ involves developing a working replica of the system or some aspect of the system.
Prototyping
54. _____ refer to "conditions or capabilities that must be met by the project or present in the product, service, or result to satisfy an agreement or other formally imposed specification."
Requirements
51. _____ refers to all the work involved in creating the products of the project and the processes used to create them.
Scope
69. _____ involves controlling changes to the project scope while keeping project goals and business strategy in mind.
Scope control
____________________ involves controlling changes to the project scope.
Scope control
67. _____ is the tendency for project scope to keep getting bigger and bigger.
Scope creep
____________________ is the tendency for project scope to keep getting bigger and bigger.
Scope creep
The work involved in creating the products and the processes used to create them.
Scope refers to:
45. _____ involves formal acceptance of the completed project scope by the stakeholders.
Scope validation
____ involves formal acceptance of the completed project scope by the stakeholders. a. Scope verification c. Scope control b. Scope planning d. Scope definition
Scope verification
1. Scope refers to all the work involved in creating the products of the project and the processes used to create them.
TRUE
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.
TRUE
11. The project scope statement, stakeholder requirements documentation, and organizational process assets are the primary inputs for creating a WBS.
TRUE
19. Many organizations provide different guidelines and templates for developing WBSs.
TRUE
20. Mind mapping allows people to write and even draw pictures of ideas in a nonlinear format.
TRUE
22. A unit of work should appear at only one place in the WBS.
TRUE
23. Scope creep if not managed well can lead to the failure of information technology projects.
TRUE
3. Project scope management includes the processes involved in defining and controlling what is or is not included in a project.
TRUE
4. The scope management plan can be informal and broad or formal and detailed, based on the needs of the project.
TRUE
6. Information from the project charter provides a basis for further defining the project scope.
TRUE
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.
TRUE
22. Scope creep if not managed well can lead to the failure of information technology projects.
TRUE Even when the project scope is fairly well defined, many IT projects suffer from scope creep—the tendency for project scope to keep getting bigger and bigger. Many IT projects fail due to scope creep.
19. Mind mapping allows people to write and even draw pictures of ideas in a nonlinear format.
TRUE Instead of writing down tasks in a list or immediately trying to create a structure for tasks, mind mapping allows people to write and even draw pictures of ideas in a nonlinear format. This more visual, less structured approach to defining and then grouping tasks can unlock creativity among individuals and increase participation and morale among teams.
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.
TRUE Many IT projects require detailed functional and design specifications for developing software, which also should be referenced in the detailed scope statement.
18. Many organizations provide different guidelines and templates for developing WBSs.
TRUE Many organizations provide guidelines and templates for developing WBSs, as well as examples of WBSs from past projects. Microsoft Project 2010 comes with several templates, and more are available on Microsoft's Web site and other sites.
Scope refers to all the work involved in creating the products of the project and the processes used to create them.
TRUE One of the most important and most difficult aspects of project management is defining the scope of a project. Scope refers to all the work involved in creating the products of the project and the processes used to create them.
3. Project scope management includes the processes involved in defining and controlling what is or is not included in a project.
TRUE Project scope management includes the processes involved in defining and controlling what work is or is not included in a project. It ensures that the project team and stakeholders have the same understanding of what products the project will produce and what processes the project team will use to produce them.
6. Information from the project charter provides a basis for further defining the project scope.
TRUE The charter describes the high-level scope, time, and cost goals for the project objectives and success criteria, a general approach to accomplishing the project's goals, and the main roles and responsibilities of important project stakeholders.
11. The project scope statement, stakeholder requirements documentation, and organizational process assets are the primary inputs for creating a WBS.
TRUE The project scope management plan, scope statement, requirements documentation, enterprise environmental factors, and organizational process assets are the primary inputs for creating a WBS.
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.
TRUE The project scope statement should reference supporting documents, such as product specifications that will affect what products are created or purchased, or corporate policies, which might affect how products or services are produced.
4. The scope management plan can be informal and broad or formal and detailed, based on the needs of the project.
TRUE The scope management plan is a subsidiary part of the project management plan. It can be informal and broad or formal and detailed, based on the needs of the project.
Scope statement
The _____ should list and describe all of the deliverables required for the project.
Requirements management plan
The ______ documents how project needs will be analyzed, documented, and managed.
Decomposition
The main technique used in creating a WBS is _____, which involves subdividing project deliverables into smaller pieces.
decomposition
The main technique used in creating a WBS is _____, which involves subdividing project deliverables into smaller pieces.
.deliverable
The term ______ describes a product produced as part of a project.
Deliverable
The term ______ describes a product produced as part of a project.
A unit of work should appear at only one place in the WBS.
True
A unit of work should appear at only one place in the WBS. a. True b. False
True
Information from the project charter provides a basis for further defining the project scope. a. True b. False
True
Many information technology projects also require detailed functional and design specifications for developing software, which also should be referenced in the detailed scope statement. a. True b. False
True
Many organizations provide different guidelines and templates for developing WBSs. a. True b. False
True
Mind mapping allows people to write and even draw pictures of ideas in a nonlinear format. a. True b. False
True
Project scope management includes the processes involved in defining and controlling what is or is not included in a project. a. True b. False
True
Scope creep if not managed well can lead to the failure of information technology projects. a. True b. False
True
Scope refers to all the work involved in creating the products of the project and the processes used to create them. a. True b. False
True
The format of the WBS dictionary is essentially the same for all projects. a. True b. False
True
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. a. True b. False
True
The project scope statement, stakeholder requirements documentation, and organizational process assets are the primary inputs for creating a WBS. a. True b. False
True
The scope management plan can be informal and broad or formal and detailed, based on the needs of the project. a. True b. False
True
48. _____ is a process for identifying and modeling business events, who initiated them, and how the system should respond to them.
Use case modeling
72. _____ is a process for identifying and modeling business events, who initiated them, and how the system should respond to them.
Use case modeling
____ is a process for identifying and modeling business events, who initiated them, and how the system should respond to them. a. Prototyping c. RAD b. JAD d. Use case modeling
Use case modeling
28. _____ involves formalizing acceptance of the project deliverables and during this phase the key project stakeholders, such as the customer and sponsor for the project, inspect and then formally accept the deliverables.
Validating scope
46. _____ refers to the difference between planned and actual performance.
Variance
70. _____ is the difference between planned and actual performance.
Variance
____________________ is the difference between planned and actual performance.
Variance
57. A(n) _____ is a deliverable-oriented grouping of the work involved in a project that defines its total scope.
WBS
66. A(n) _____ is a document that describes detailed information about each WBS item.
WBS dictionary
A(n) ____________________ is a document that describes detailed information about each WBS item.
WBS dictionary
37. In the _____approach for constructing a WBS, you use a similar project's WBS as a starting point.
analogy
31. Generating ideas by comparing specific project practices or product characteristics to those of other projects or products inside or outside the performing organization is known as _____.
benchmarking
41. In the _____ approach, team members first identify as many specific tasks related to the project as possible and then aggregate the specific tasks and organize them into summary activities, or higher levels in the WBS.
bottom-up
64. In the _____ approach to creating a WBS, team members first identify as many specific tasks related to the project as possible.
bottom-up
In the ____________________ approach, team members first identify as many specific tasks related to the project as possible.
bottom-up
Project managers often use the ____ approach for projects that represent entirely new systems or approaches to doing a job, or to help create buy-in and synergy with a project team. a. analogy c. top-down b. bottom-up d. mind mapping
bottom-up
The ____ approach involves refining the work into greater and greater levels of detail. a. analogy c. top-down b. bottom-up d. mind mapping
bottom-up
34. The main technique used in creating a WBS is _____, which involves subdividing project deliverables into smaller pieces.
decomposition
58. Subdividing the project deliverables into smaller pieces is known as _____.
decomposition
24. The term ______ describes a product produced as part of a project.
deliverable
The term ____ describes a product produced as part of a project. a. end-product c. deliverable b. scope d. outcome
deliverable
The ____ tasks vary the most from project to project. a. closing c. planning b. monitoring and controlling d. executing
executing
There are ____ main processes involved in project scope management. a. three c. five b. four d. six
five
68. The main tool for performing scope validation is _____ and group decision making techniques.
inspection
62. A work package is a task at the _____ level of the WBS.
lowest
40. The _____ technique for creating a WBS uses branches radiating from a core idea to structure thoughts and ideas instead of writing down tasks in a list or immediately trying to create a structure for tasks.
mind mapping
29. Creating the WBS is a subprocess associated with the _____ process in project scope management.
planning
Factors such as user involvement, clear business objectives, a minimized or clearly defined scope, and firm basic requirements, are elements of ____________________.
project scope management
56. The main outputs of scope definition are the _____ and project document updates.
project scope statement
30. The ______ documents how project needs will be analyzed, documented, and managed.
requirements management plan
32. A(n) _____ is a table that lists requirements, their various attributes, and the status of the requirements to ensure that all are addressed.
requirements traceability matrix
55. A(n) _____ is a table that lists requirements, their various attributes, and the status of the requirements to ensure that all are addressed.
requirements traceability matrix (RTM)
Of the following constraints, it is most difficult to describe, agree upon, and meet the ____ goal of many projects. a. scope c. cost b. time d. technical
scope
59. The _____ includes the approved project scope statement and its associated WBS and WBS dictionary.
scope baseline
52. The main outputs of _____are the project scope statement and updates to project documents.
scope definition
36. The _____ should list and describe all of the deliverables required for the project.
scope statement
60. Tasks in a WBS that are decomposed into smaller tasks are called _____ tasks.
summary
61. PMI uses the term "_____" to describe each level of work in the WBS.
task
PMI uses the term "___________________" to describe each level of work in the WBS.
task
44. Scope creep refers to:
the tendency for project scope to keep getting bigger and bigger.
42. Mind mapping can be used for developing WBSs using
the top-down or bottom-up approach
25. Scope refers to:
the work involved in creating the products and the processes used to create them.
38. The _____ approach for constructing a WBS involves refining the work into greater and greater levels of detail.
top-down
39. The _____ approach for constructing a WBS starts with the largest items of the project and breaks them into subordinate items.
top-down
A(n) ____________________ project scope statement is an important document for developing and confirming a common understanding of the project scope.
up-to-date - up to date -
The main outputs of ____ are accepted deliverables and change requests. a. planning scope c. defining scope b. controlling scope d. verifying scope
verifying scope
53. Creating the _____ involves subdividing the major project deliverables into smaller, more manageable components.
work breakdown structure (WBS)
35. A(n) ____ is a task at the lowest level of the WBS.
work package
A(n) ____________________ is a task at the lowest level of the WBS.
work package
Collecting requirements
_____ involves defining and documenting the features and functions of the products produced during the project as well as the processes used for creating them.
Prototyping
_____ refers to the process of developing a working replica of the system or some aspect of the system.
JAD
_____ uses highly organized and intensive workshops to bring together project stakeholders—the sponsor, users, business analysts, programmers, and so on—to jointly define and design information systems.
Many people confuse tasks on a WBS with ____. a. goals c. responsibilities b. objectives d. specifications
specifications
77. What are some of the suggestions for improving the requirements process?
1. Develop and follow a requirements management process that includes procedures for initial requirements determination. 2. Employ techniques such as prototyping, use case modeling, and Joint Application Design to understand user requirements thoroughly. Prototyping involves developing a working replica of the system or some aspect of the system. These working replicas may be throwaways or an incremental component of the deliverable system. Prototyping is an effective tool for gaining an understanding of requirements, determining the feasibility of requirements, and resolving user interface uncertainties. Use case modeling is a process for identifying and modeling business events, who initiated them, and how the system should respond to them. It is an effective tool for understanding requirements for information systems. Joint Application Design (JAD) uses highly organized and intensive workshops to bring together project stakeholders—the sponsor, users, business analysts, programmers, and so on—to jointly define and design information systems. These techniques also help users become more active in defining system requirements. 3. Put all requirements in writing and keep them current and readily available. Several tools are available to automate this function. For example, a type of software called a requirements management tool aids in capturing and maintaining requirements information, provides immediate access to the information, and assists in establishing necessary relationships between requirements and information created by other tools. 4. Create a requirements management database for documenting and controlling requirements. Computer Aided Software Engineering (CASE) tools or other technologies can assist in maintaining a repository for project data. A CASE tool's database can also be used to document and control requirements. 5. Provide adequate testing to verify that the project's products perform as expected. Conduct testing throughout the project life cycle. 6. Use a process for reviewing requested requirements changes from a systems perspective. 7. Emphasize completion dates. 8. Allocate resources specifically for handling change requests.
A WBS is often depicted as a task-oriented pie chart.
False
A work package should always represent less than 80 hours of work.
False
Deliverables are only product-related, such as a piece of hardware or software.
False
It is easy to create a good WBS.
False
Project scope statements should include, at a minimum, a product scope description and detailed information on all project deliverables.
False
The executing tasks of the WBS remain constant from project to project.
False
The project scope statement provides the basis for planning and managing project schedules, costs, resources, and changes.
False
The project's size, complexity, importance, and other factors will not affect how much effort is spent on collecting requirements for scope planning.
False
The scope of a project should be clear and specific from the start.
False
benchmarking
Generating ideas by comparing specific project practices or product characteristics to those of other projects or products inside or outside the performing organization is known as _____.
bottom-up
In the _____ approach, team members first identify as many specific tasks related to the project as possible and then aggregate the specific tasks and organize them into summary activities, or higher levels in the WBS.
analogy
In the _____approach for constructing a WBS, you use a similar project's WBS as a starting point.
work breakdown structure
A(n) _____ is a deliverable-oriented grouping of the work involved in a project that defines the total scope of the project.
requirements traceability matrix
A(n) _____ is a table that lists requirements, their various attributes, and the status of the requirements to ensure that all are addressed.
____ uses highly organized and intensive workshops to bring together project stakeholders—the sponsor, users, business analysts, programmers, and so on—to jointly define and design information systems. a. Prototyping c. RAD b. JAD d. Use case modeling
JAD COMPLETION
____________________ can be used for developing WBSs using the top-down or bottom-up approach.
Mind mapping
____________________ is a technique that uses branches radiating out from a core idea to structure thoughts and ideas.
Mind mapping
the tendency for project scope to keep getting bigger and bigger.
Scope creep refers to:
76. Describe the process of scope verification.
Scope verification involves formal acceptance of the completed project scope by the stakeholders. This acceptance is often achieved by a customer inspection and then sign-off on key deliverables. To receive formal acceptance of the project scope, the project team must develop clear documentation of the project's products and procedures to evaluate if they were completed correctly and satisfactorily. To minimize scope changes, it is crucial to do a good job of verifying project scope. The scope management plan, scope baseline, requirements documentation, requirements traceability matrix, validated deliverables, and work performance data are the main inputs for scope validation. The main tools for performing scope validation are inspection and group decision-making techniques. The customer, sponsor, or user inspects the work after it is delivered and decides if it meets requirements. The main outputs of scope validation are accepted deliverables, change requests, work performance information, and project documents updates.
top-down
The _____ approach for constructing a WBS starts with the largest items of the project and breaks them into subordinate items.
scope statement
The _____ should list and describe all of the deliverables required for the project.
mind mapping
The _____ technique for creating a WBS uses branches radiating from a core idea to structure thoughts and ideas instead of writing down tasks in a list or immediately trying to create a structure for tasks.
If you want some time-based flow for the work, you can create a WBS using the project management process groups of initiating, planning, executing, monitoring and controlling, and closing as Level 2 in the WBS.
True
Information from the project charter provides a basis for further defining the project scope.
True
Lack of user input leads to problems with managing scope creep and controlling change.
True
Many organizations provide guidelines and templates for developing WBSs.
True
Scope refers to all the work involved in creating the products of the project and the processes used to create them.
True
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.
True
The project scope statement, stakeholder requirements documentation, and organizational process assets are the primary inputs for creating a WBS.
True
The tasks in a WBS do not have to be developed as a sequential list of steps.
True
You can only enter duration estimates for work packages.
True
____ involves formalizing acceptance of the project deliverables and during this phase the key project stakeholders, such as the customer and sponsor for the project, inspect and then formally accept the deliverables during this process. a. Planning scope c. Controlling scope b. Defining scope d. Verifying scope
Verifying scope
Creating the ____________________ involves subdividing the major project deliverables into smaller, more manageable components.
WBS - work breakdown structure - work breakdown structure (WBS)
Some project management experts believe that work should not be done on a project if it is not included in the ____________________.
WBS - work breakdown structure - work breakdown structure (WBS)
A unit of work should appear at only one place in the WBS.
Which of the following is recommended for the creation of a good WBS?
Variance
_____ refers to the difference between planned and actual performance.
In the ____, you use a similar project's WBS as a starting point. a. top-down approach c. mind-mapping approach b. bottom-up approach d. analogy approach
analogy approach
The ____ approach is best suited to project managers who have vast technical insight and a big-picture perspective. a. analogy c. top-down b. bottom-up d. mind mapping
bottom-up
If ____________________ for developing a WBS exist, it is very important to follow them.
guidelines
The main tool for performing scope verification is ____________________.
inspection
After discovering WBS items and structure using the ____ technique, you could then translate the information into chart or tabular form. a. analogy c. top-down b. bottom-up d. mind mapping
mind mapping
An up-to-date ____ is an important document for developing and confirming a common understanding of the project scope. a. scope management plan c. WBS b. project scope statement d. decomposition
project scope statement
The approved project scope statement and its associated WBS and WBS dictionary form the ____________________.
scope baseline
The goal of ____ is to influence the factors that cause scope changes, assure changes are processed according to procedures developed as part of integrated change control, and manage changes when they occur. a. scope verification c. scope planning b. scope control d. scope definition
scope control
Good ____ is very important to project success because it helps improve the accuracy of time, cost, and resource estimates, it defines a baseline for performance measurement and project control, and it aides in communicating clear work responsibilities. a. scope planning c. scope definition b. scope management d. scope verification
scope definition
The main outputs of ____________________ are the project scope statement and updates to project documents.
scope definition
The ____ should list and describe all of the deliverables required for the project. a. project charter c. WBS b. scope statement d. Gantt chart
scope statement
The project scope statement should reference ____________________, 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.
supporting documents
A(n) ____ is a deliverable-oriented grouping of the work involved in a project that defines the total scope of the project. a. project charter c. project scope statement b. business case d. work breakdown structure
work breakdown structure
requirements management plan
The ______ documents how project needs will be analyzed, documented, and managed.
A work package represents the level of work that the project manager monitors and controls.
True
75. List and briefly describe five approaches for creating work breakdown structures.
*Using Guidelines If guidelines for developing a WBS exist, it is very important to follow them. Some organizations—the U.S. Department of Defense (DOD) for example—prescribe the form and content for WBSs for particular projects. Many organizations provide guidelines and templates for developing WBSs, as well as examples of WBSs from past projects. At the request of many of its members, the Project Management Institute recently developed a WBS Practice Standard to provide guidance for developing and applying the WBS to project management. Project managers and their teams should review appropriate information to develop their unique project WBSs more efficiently. *The Analogy Approach In the analogy approach, you use a similar project's WBS as a starting point. Some organizations keep a repository of WBSs and other project documentation on file to assist people working on projects. Viewing examples of other similar projects' WBSs allows you to understand different ways to create a WBS. *The Top-down and Bottom-up Approaches Most project managers consider the top-down approach of WBS construction to be conventional. To use the top-down approach, start with the largest items of the project and break them into their subordinate items. This process involves refining the work into greater and greater levels of detail. After finishing the process, all resources should be assigned at the work package level. The top-down approach is best suited to project managers who have vast technical insight and a big-picture perspective. In the bottom-up approach, team members first identify as many specific tasks related to the project as possible. They then aggregate the specific tasks and organize them into summary activities, or higher levels in the WBS. The bottom-up approach can be very time-consuming, but it can also be a very effective way to create a WBS. Project managers often use the bottom-up approach for projects that represent entirely new systems or approaches to doing a job, or to help create buy-in and synergy with a project team. *Mind Mapping Mind mapping is a technique that uses branches radiating out from a core idea to structure thoughts and ideas. Instead of writing tasks down in a list or immediately trying to create a structure for tasks, mind mapping allows people to write and even draw pictures of ideas in a nonlinear format. This more visual, less structured approach to defining and then grouping tasks can unlock creativity among individuals and increase participation and morale among teams. After discovering WBS items and structure using the mind-mapping technique, you could then translate the information into chart or tabular form. Mind mapping can be used for developing WBSs using the top-down or bottom-up approach.
The format of the WBS dictionary should be the same from project to project.
False
the work involved in creating the products and the processes used to create them.
Scope refers to:
top-down
The _____ approach for constructing a WBS involves refining the work into greater and greater levels of detail.
Scope validation
_____ involves formal acceptance of the completed project scope by the stakeholders.
Validating scope
_____ involves formalizing acceptance of the project deliverables and during this phase the key project stakeholders, such as the customer and sponsor for the project, inspect and then formally accept the deliverables.
Defining scope
_____ involves reviewing the project charter, requirements documents, and organizational process assets to create a scope statement, adding more information as requirements are developed and change requests are approved.
Use case modeling
_____ is a process for identifying and modeling business events, who initiated them, and how the system should respond to them.
Key inputs for preparing the project scope statement include the ____________________, requirements documentation, and organizational process assets such as policies and procedures related to scope statements as well as project files and lessons learned from previous, similar projects.
project charter
The main outputs of scope definition are the ____________________ and project document updates.
project scope statement
