Glossary Delivery
| Term | Definition |
|---|---|
| Affinity Diagram | A tool used to gather ideas and organize them into groupings so they can be reviewed and analyzed; typically used for ideas generated from brainstorming sessions |
| Affinity Grouping | The process to group similar items into the same category. |
| Context Diagrams | A graphical representation of the scope of a business system that includes processes, equipment, and computer systems and indicates the manner in which people and other systems interact with the business system |
| Continuous Delivery | The approach to deliver features immediately to the customer in small increments of work and automation technology. |
| Data-flow diagram (DFD) | Graphical representation depicting the movement of data between processes, objects, and storage within the system |
| Data Gathering and Analysis Methods | A method used to collect, assess, and review data and information to better understand the situation. |
| Decomposition | The process of breaking down the work of the project into smaller, more controllable components |
| Deliverable | Any product, result, or service that must be generated to complete a process, phase, or project |
| Delivery Performance Domain | The performance domain that focuses on activities and functions to deliver project scope and quality. |
| Facilitated Workshop | A focused session involving cross-functional stakeholders and a designated leader that is conducted to achieve a specific goal, such as the creation of project requirements |
| Features | The characteristics that the user desires built into a product |
| Incentive Fee | An amount paid, in addition to the contract amount, for exceeding expectations, particularly in the areas of cost, schedule, or technical performance |
| Increment | Consecutive changes that increase the amount or value of something |
| Interviews | A focused session involving individual stakeholders and a designated leader that is conducted to elicit specific information |
| Issue | A disputed or unsettled condition |
| Issue Log | A project document that tracks elements which cause stakeholder concern or dissension |
| Just In Time (JIT) Development | The development of something when it’s needed and not before |
| Lead Time | The amount of time between a customer's request and delivery. |
| Lead Time Chart | A chart that shows trends over time and the average lead time of completed work items. |
| Learning Curve Theory | A theory which states that the more of something that is produced, the lower the unit cost of it becomes due to an improvement in efficiency |
| Mind-Mapping | A technique used to integrate ideas created through individual brainstorming sessions into a single map in order to highlight similarities and differences in understanding and generate new ideas. |
| Modeling | The process of evaluating counterfeit situations to determine their impact on the project |
| MoSCoW | A model for prioritization that categorizes features as Must Have, Should Have, Could Have, Won’t Have [we use KANO instead] |
| Negotiated Settlement | The resolution and finalization of any contract related issues, claims, and disputes |
| Nominal Group Technique | A technique, effected by a voting process, that is used to prioritize ideas by utility for further brainstorming |
| Observed Velocity | A technique used to estimate future velocity based on the velocity achieved during one, two, or three completed iterations |
| Outcome | An end result of a process or product. |
| PDCA (Plan Do Check Act) | An iterative, four step process used to improve quality |
| Planning Package | A WBS component that has no detailed scheduled activities even though it is known to have work content |
| Plurality | The votes of the largest block in a group when a majority is not required, typically used to denote agreement with a decision |
| Prioritization Matrices | A quality management tool used to identify issues and potential alternatives related to the establishment of implementation priorities |
| Product Scope | The features and functions of a project's product, service, or result |
| Project Requirements | The conditions or capabilities that a product, service, or outcome should preform when complete. |
| Project Scope | The work executed to deliver a product, service, or result that satisfies the specified features and functions |
| Project Scope Management | The processes required to ensure that all the work needed to complete the project, and only that work, is included in the project |
| Project Scope Statement | The document that describes the major deliverables, assumptions, constraints, and scope of the project |
| Proof of Concept (POC) | A model built to test a concept; a prototype |
| Prototype | A working model of the product created to obtain detailed stakeholder feedback |
| Quality Function Deployment (QFD) | A workshop approach used in manufacturing environments to establish requirements. |
| Quality Gate | A gate that occurs before a project phase. It is impacted by the previous phase. The quality gate is used to help document the transition between stages in the project life cycle as quality goals are met. |
| Quality Management Plan | The document, part of the project or program management plan, used to describe the execution of the organization's quality policies |
| Quality Policy | The organizational policies crafted to achieve quality goals. |
| Questionnaires | Written surveys designed to quickly gather information from a large number of respondents. |
| Requirement | A condition or capability that must be made available through a product, service, or result in order to fulfill a contract or formal specification |
| Requirements Documentation | A document that describes requirements for creating a product or a feature of the product |
| Requirements Management Plan | The document, part of the project or program management plan, used to describe the evaluation, recording, and administration of project requirements |
| Requirements Traceability Matrix | A graphical representation that illustrates the relationships between the origins of the product requirements to the deliverables that fulfill the requirements |
| Scope | The products, services, and results expected to be provided by the project |
| Scope Baseline | The authorized scope statement, WBS, and WBS dictionary that contain only those modifications authorized through a formal change control process; used as a basis for comparison |
| Scope Creep | The gradual increase in the scope of the project over time |
| Scope Management Plan | The document, part of the project or program management plan, used to the manner in which the project scope will be delineated, elaborated, monitored, controlled, and authenticated |
| Self-adapting | Modification of a process as quickly as needed to bring greater efficiency and effectiveness to the project |
| Service Level Agreement (SLA) | A contract between an internal or external service provider and the end user that delineates the level of service expected from the service provider. |
| Swarm | The assignment of all capable team members to a specific task with a high priority |
| Throughput | The rate at which items pass through a system |
| Throughput Chart | A chart that shows accepted deliverables over time on a project. |
| Traceability | The practice of defining the relationships between different artifacts (e.g., documents, models, and source code) |
| User interface (UI) | The part of the system with which the user will interact |
| Value Stream | The series of activities required to analyze, design, build, and deploy a product |
| Value Stream Map | A graphical display of the steps associated with a process, and the time with each step to identify potential waste. |
| Value Stream Mapping | The identification of the process steps to analyze, design, build, and deploy a product; tools are available to execute this process |
| Voice of the Customer (VOC) | The translation of customer requirements into requisite technical requirements in a manner that ensures the results of the project will meet the requirements of the customer |
| Warranty | A commitment from the organization providing it, that the product, service, or outcome will perform at a predefined standard. |
| Waste | Anything that does not add value for the customer |
| WBS Dictionary | A document that itemizes deliverable, activity, and scheduling information for each WBS component |
| Work Breakdown Structure (WBS) | A document used in traditional project management that itemizes the work decomposed from the project scope statement |
| Work in Progress (WIP) | Software that is in the process of development, but has not yet been deployed; calculated by multiplying throughput (rate at which items pass through the system) by lead time (time between two successive deliveries) |
| Work Package | The smallest level of WBS work for which cost and time can be assessed and administered |
