Glossary Framework
Term | Definition |
---|---|
Artifact | Something made by the team for the project, especially something that may be reused |
Controlling PMO | A project management office that provides support and requires compliance in the form of an adoption of mandated project management frameworks, governance frameworks, and/or tools and documentation. |
Cost Benefit Analysis | A financial analysis approach that compares the project's benefits (revenue) to its costs. (Sometimes called a benefit cost analysis.) |
Dashboard | An information radiator that contains graphical representations depicting progress, trends, and identification of potential issues |
Directive PMO | A project management office that directly manages projects. |
Enterprise | A company, business, or other formal structure that encompasses a business function |
Functional Organization | An entity that is arranged by department or purpose and focuses on operational work rather than project work |
Goverance | A framework for policies, practices, and documentation that an organization applies to projects and operations. |
Impact Mapping | A strategic planning method that results in a visual roadmap for the organization while doing product development. |
Log | Documentation of selected items that occur during a project, typically modified to reflect the condition of the item (issue, quality control item, action, or defect) |
Matrix Organization | An organizational framework that mandates the sharing of responsibility for the assignment of resources and priorities between the project manager and the functional manager |
Method | An approach to produce an outcome, output, result, or project deliverable. |
Methodology | A body of rules, practices, processes, and techniques employed within a field |
Operations | The day-to-day repeatable activities that a company performs |
Organizational Process Assets | The process-related assets of the performing organization including, but not limited to, procedures, processes, policies, knowledge bases, templates, documentation, and plans |
Policy | A course of action adopted by an organization to facilitate operational and project work |
Portfolio | The projects, programs, and other work that comprise the portfolio and are managed in a coordinated manner to accomplish strategic goals |
Portfolio Management | The coordinated management of the projects, programs, and other work that comprise the portfolio for the purpose of accomplishing strategic goals |
Product Management | The application of people, processes, data, and systems to create, maintain and update a product or service through its life cycle. |
Program | A group of related projects, subprograms, and program activities administered in a coordinated manner in order to realize benefits that would not be available if administered separately |
Program Management | The exercise of knowledge, expertise, tools, and techniques to meet program requirements and realize benefits and control unavailable when component projects are administered individually |
Project | A temporary undertaking to produce a unique product, service, or result |
Project Archives | A set of records that correctly describe and document the history of the project |
Project Artifact | Any project management document. |
Project Governance | The alignment of project goals with the strategy established by the organization, the project sponsor, and team; must fit within the organizational governance, but is separate from that organizational governance |
Project Management | The exercise of knowledge, expertise, tools, and techniques to meet project requirements |
Project Management Body of Knowledge | The total knowledge contained within the project management profession including its practices, both customary and groundbreaking, whether published and non published |
Project Management Information System (PMIS) | A system, either manual or automated, comprised of the tools and techniques used to amass, incorporate, and disseminate the results of project management processes in order to reinforce all facets of the project |
Project Management Office (PMO) | An organization area responsible for standardizing governance processes for projects and for making available resources, methodologies, tools and techniques |
Project Management Software | An application that can assist in planning, estimating, organizing, and managing resources. |
Projectized Organization | An organizational framework that provides the project manager with the authority to establish priorities, assign resources, and direct the work of the project team |
Register | A documented record of evolving project entries such as issues, risks, stakeholders, or defects. |
Regulation | A requirement of local, state, or federal government that can mandate product, process, or service characteristics including any applicable administrative provisions |
Result | The consequence of completing a series of activities or process; examples include outcomes and documents |
Standard | An established norm or requirement |
Strategic Planning | Long-term planning by a company (usually three to five years in the future) |
Strategy Artifact | Documents started before or early into the project covering strategic, business and any other high-level information related to the project. |
System | Software, hardware, middleware, documentation, and installation and operational procedures |
Templates | A partially completed instrument that provides the desired format for the assemblage, ordering, and presentation of data and information |
Triple Bottom Line | A framework for looking at the full cost of business, with a focus on profit, people, and the planet. |
Value | Something that is viewed to be useful, have worth, or importance. |
Value Delivery Office (VDO) | A project delivery support group that focuses on coaching teams, building agile skills and capabilities through the organization. This also includes helping sponsors and product owners maximize their effectiveness to the organization. |