Term
|
Definition
| Creating a WBS by using a similar project’s WBS as a starting point. |
|
|
Term
|
Definition
| A technique used to generate ideas for quality improvements by comparing specific project practices or product characteristics to those of other projects or products within or outside the performing organization. |
|
|
Term
|
Definition
| Creating a WBS by having team members identify as many specific tasks related to the project as possible and then grouping them into higher-level categories. |
|
|
Term
|
Definition
| Subdividing project deliverables into smaller pieces. |
|
|
Term
|
Definition
| A product or service, such as a technical report, a training session, a piece of hardware, or a segment of software code, produced or provided as part of a project. |
|
|
Term
| Joint Application Design (JAD) |
|
Definition
| Using 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. |
|
|
Term
|
Definition
| The processes involved in defining and controlling what work is or is not included in a project. |
|
|
Term
|
Definition
| A document that includes at least a description of the project, including its overall objectives and justification, detailed descriptions of all project deliverables, and the characteristics and requirements of products and services produced as part of the project. |
|
|
Term
|
Definition
| Developing a working replica of the system or some aspect of it to help define user requirements. |
|
|
Term
|
Definition
| A condition or capability that must be met by the project or that must be present in the product, service, or result to satisfy an agreement or other formally imposed specification. |
|
|
Term
| Requirements management plan |
|
Definition
| A plan that describes how project requirements will be analyzed, documented, and managed. |
|
|
Term
|
Definition
| All the work involved in creating the products of the project and the processes used to create them. |
|
|
Term
|
Definition
| The approved project scope statement and its associated WBS and WBS dictionary. |
|
|
Term
|
Definition
| The tendency for project scope to keep getting bigger. |
|
|
Term
|
Definition
| Formal acceptance of the completed project deliverables. |
|
|
Term
|
Definition
| Creating a WBS by starting with the largest items of the project and breaking them into subordinate items. |
|
|
Term
|
Definition
| A process for identifying and modeling business events, who initiated them, and how the system should respond to them. |
|
|
Term
|
Definition
| The difference between planned and actual performance |
|
|
Term
|
Definition
| A document that includes detailed information about each WBS item. |
|
|
Term
| Work breakdown structure (WBS) |
|
Definition
| A deliverable-oriented grouping of the work involved in a project that defines its total scope. |
|
|
Term
|
Definition
| A task at the lowest level of the WBS. |
|
|
