Chapter5
Order by
48 terms
Terms | Definitions |
|---|---|
 One of the most important and most difficult aspects of project management is defining the ________ of the project. | SCOPE |
| ________ can be product-related, such as a piece of hardware or software, or process-related, such as a planning document or meeting minutes. | DELIVERABLES |
| Which of the following processes of project scope management involves defining and documenting the features and functions of the products produced during the project as well as the processes used for creating them?See page 178 | COLLECTING REQUIREMENTS |
| Which of the following processes of project scope management involves subdividing the major project deliverables into smaller, more manageable components? | CREATING the WBS |
| Key project stakeholders, such as the customer and sponsor for the project, inspect and then formally accept the deliverables of the project during the ________ process of project scope management. | SCOPE VERIFICATION |
| Which of the following processes of project scope management involves reviewing the project charter and preliminary scope statement created during the initiation process and adding more information during the planning process as requirements are developed and change requests are approved?See page 179 | SCOPE DEFINITION |
| ________ is the first step in project scope management and is often the most difficult. | COLLECTING REQUIREMENTS |
| The project scope statement, stakeholder requirements documentation, and organizational process assets are the primary inputs for creating a ________. | scope baseline -- work package -- WBS -- prototype |
| A ________ represents the lowest level of work that the project manager is using to monitor and control the project. | WORK PACKAGE |
| One approach for constructing a WBS is the ________, in which you use a similar project's WBS as a starting point. | ANALOGY APPROACH |
| In which approach to creating a WBS do team members first identify as many specific tasks related to the project as possible? | BOTTOM-UP APPROACH |
| Most project managers consider the ________ of WBS construction to be conventional; you start with the largest items of the project and break them into their subordinate items. | TOP-DOWN APPROACH |
| Instead of writing tasks down in a list or immediately trying to create a structure for tasks, the ________ allows people to write and even draw pictures of ideas in a nonlinear format. | MIND MAPPING Approach |
| Which of the following is a basic principle that applies to creating any good WBS and its WBS dictionary? | RESPONSIBILITY ONE PERSON |
| The approved project scope statement and its associated WBS and WBS dictionary form the ________. | SCOPE BASELINE |
| Even when the project scope is fairly well defined, many information technology projects suffer from ________, which is the tendency for project scope to keep getting bigger and bigger. | SCOPE CREEP |
| The project management plan, requirements documentation, the requirements traceability matrix, and validated deliverables are the main inputs for ________. | SCOPE VERIFICATION |
| ________ is the difference between planned and actual performance. | VARIANCE |
| ________ 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 |
| ________ is a process for identifying and modeling business events, who initiated them, and how the system should respond to them. | USE CASE MODELING |
| analogy approach | creating a WBS by using a similar projects WBS as a starting point |
| bottom-up approach | creating a WBS by having team members identify as many specific tasks related to the project as possible and then into higher-level categories |
| decomposition | subdividing project deliverables into smaller pieces |
| joint application design (JAD) | using highly organized and intensive workshops to bring together project stakeholders e.g. sponsors, users, business analysts, programmers and so, to jointly define and design information systems |
| project scope management | processes involved in defining and controlling what work is and is not included in the project |
| prototyping | developing a working replica of the system or some aspect of the system to help define user requirements |
| requirement | a condition or capability that must be met or possessed by a system, product, service, result, or component to satisfy a contract, standard, specification, or other formal document |
| requirements management plan | a plan that describes how project requirements will be analyzed, documented and managed |
| requirements traceability matrix (RTM) | a table that lists requirements, various attributes of each requirement and the status of the requirement to ensure that all requirements are a rest |
| scope | all of the work involved in creating the products of the project and the processes used to create them |
| scope baseline | the approved projects scpoestatement and its associated WBS and WBS dictionary |
| scope creep | the tendency for projects scope to keep getting bigger |
| top-down approach | creating a WBS by starting with the largest items of the project and breaking them down into their subordinate items |
| use case modeling | a process for identifying and modeling business events, who initiated them and how the system should respond to them |
| variance | the difference between planned and actual performance |
| WBS dictionary | a document that describes detailed information about each WBS item |
| work breakdown structure (WBS) | a deliverable-oriented grouping of the work involved in a project that defines the total scope of the project |
| work package | a task at the lowest level of the WBS |
| _________refers to all the work involved in creating the products of the project and the processes used to create them. | Deliverables -- milestones -- SCOPE -- product development |
| which tool or technique for collecting requirements is often the most expensive and time-consuming | INTERVIEWS -- focus groups -- surveys -- observation |
| a_______ is a deliverable oriented grouping of the work involved in a project that defines the total scope of the project | scope statement -- WBS -- WBS dictionary -- work package |
| what approach in developing a WBS involves writing down or crawling ideas in a nonlinear format | top-down -- bottom-up-- analogy -- MIND MAPPING |
| Assume you have a project with a major categories called planning, analysis, design , testing. What level of the WBS would these items fall under | TWO |
| which of the following is not a best practice that can help in avoiding scope problems on information technology projects | DON'T INVOLVE TOO MANY USERS IN SCOPE MANAGEMENT |
| what major restaurant chain terminated a large project after spending $170 million on it, primarily because they read it realize that the project scope was too much to handle | mikeyD |
| scope_________ is often achieved by a customer inspection and then sign off on key deliverables | VERIFICATION |
| which of the following is not a suggestion for improving user input | ONLY HAVE MEETINGS AS NEEDED, NOT ON A REGULAR BASIS |
| project management software helps you develop a_______, which serves as a basis for creating Gantt charts, assigning resources, and allocating costs | WBS |
First Time Here?
Welcome to Quizlet, a fun, free place to study. Try these flashcards, find others to study, or make your own.