| A | B |
|---|
| analogy approach | Creating a WBS by using a similar project's 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 grouping them into higher level categories. |
| decomposition | Subdividing project deliverables into smaller pieces. |
| JAD - Joint Application Design | Using highly organized and intensive workshops to bring together project stakeholders - the sponsor, users, business analysts, programmers, and others to jointly define and design information systems. |
| Project Scope Management | The processes involved in defining and controlling what work is or is not included in a project. |
| Project Scope Statement | A document that includes, at minimum, a description of the project, including overal; objectives and justification, detailed descriptions of all project deliverables, and the characteristics and requirements of products and services produced as part of the project. |
| prototyping | Developing a working replica of the system or some aspect of the system to help define the 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. |
| RTM - Requirements Traceability Matrix | A table that lists requirements, various attributes of each requirement, and the status of the requirements to ensure that all the requirements are addressed. |
| scope | All the work involved in creating the products of the project and the processes used to create them. |
| scope baseline | The approved project scope statement and its associated WBS and WBS dictionary. |
| scope creep | The tendency for project scope to keep getting bigger. |
| top-down approach | creating a WBS by starting with the largest items of the project and breaking them 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 the planned and actual performance. |
| WBS Dictionary | A document that describes detailed information about each WBS item. |
| WBS - Work Breakdown Structure | 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. |
