Term
|
Definition
| Requirements that are defined to be completed before the work can be accepted. |
|
|
Term
|
Definition
| The process of breaking down the work of the project into smaller more controllable pieces. |
|
|
Term
|
Definition
| A major point in the project; typically beginning or completing a major piece of the work of the project. |
|
|
Term
|
Definition
| The measurable, definable work of the project. |
|
|
Term
|
Definition
| Processes associated with determining and controlling what a project includes or does not include. |
|
|
Term
|
Definition
| Document that develops and helps attain buy-in on a common interpretation of project scope. |
|
|
Term
|
Definition
| A need that must be completed to attain the project goals, could be business or technical. |
|
|
Term
|
Definition
| The desired outcome of the project, the work that will be encompassed in the project and the final product. |
|
|
Term
|
Definition
| Original (or approved revised) definition of the scope the project should create, can include project scope statement,work breakdown structure (WBS), and WBS dictionary. |
|
|
Term
|
Definition
| The process of controlling the scope of the project. |
|
|
Term
|
Definition
| The process of developing a project scope statement. |
|
|
Term
|
Definition
| The point at which a WBS is created with the major (or bigger)pieces, then they are broken down into the smaller pieces. |
|
|
Term
|
Definition
| A tool that works with the WBS to ensure that the right work happens in the right order by the correct resources, helps improve the quality of work by verifying that the needed conditions have been met before future work begins. |
|
|
Term
|
Definition
| An organized breakdown of the total work scope of the project. Each level of descent provides a greater level of detail with the deliverable being a key focus. |
|
|
Term
|
Definition
| A deliverable at the smallest level of the WBS, represents the completed piece of the project from the culmination of a series of activities being completed. |
|
|
Term
|
Definition
| The process of formally receiving the work of the project. The work should be complete and fulfill the needs for which it was created. |
|
|
Term
|
Definition
| An approach in which a previous project similar characteristics is used to obtain the values (duration, resources, budget, etc.) for the current project being planned. |
|
|
Term
|
Definition
An approach in which the team or at least the
Project Manager is involved in deciding on and estimating the individual pieces of the project to create the summary. |
|
|
Term
| Deliverable (Output/Input) |
|
Definition
| A key piece of work for the project, can be physical work, a process, a document , or other measurable result of work. |
|
|
Term
|
Definition
| A technique to obtain consensus within a group of experts, typically used to gain vision about future direction or development. |
|
|
Term
|
Definition
| An approved change to the scope of the project. |
|
|
Term
|
Definition
| Unauthorized request for change that usually occurs in a project as time evolves. |
|
|
Term
|
Definition
| Determining documentation needs associated with how the scope of the project will be managed; can include approaches for project decomposition and verification. |
|
|
Term
|
Definition
| Gaining approval of the project scope. |
|
|
Term
|
Definition
| The person, division, or company that will be the user or owner of the product when the project is complete. |
|
|
Term
|
Definition
| The process of evaluating something that was created in the project to ensure that it meets the needed requirements for formal acceptance. |
|
|
Term
|
Definition
| The process of evaluating something that was created in the project to ensure that it meets specified conditions. |
|
|
