Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
103 Cards in this Set
- Front
- Back
Authority
|
The agreement to be able to assign project resources, make project decisions, and spend project funding.
|
|
Administrative Closure
|
The process of accumulating, finishing, and interpreting information to achieve completion of a phase or project.
|
|
Approved Change Request (Output/Input)
|
A request for a change on a project that has been approved via formal or informal change request.
|
|
Assumption
|
An educated, logical guess about a variable when its details are unknown on a project or program.
|
|
Assumption Analysis
|
A technique to determine if the project assumptions are accurate, consistent, and complete, and if not, the resultant risks to the project.
|
|
Benefit Measurement Model
|
This model takes into consideration: Comparative approach; scoring models; Benefit contribution; Economic model.
|
|
Change Control
|
The formal or informal process of reviewing changes associated with a project; will result in approval or rejection of changes.
|
|
Change Control Board (CCB)
|
A group of people formally recognized to approve or reject changes on a project.
|
|
Change Control System
|
A documented, formal process that manages changes associated with the project.
|
|
Change Management Plan
|
A plan that defines the project change management process.
|
|
Close Project or Phase
|
The process of finalizing all project activities to formally complete a project or phase.
|
|
Closing Processes
|
Activities during which formal acceptance and completion procedures are attained from either a phase or the project itself.
|
|
Co-location
|
A team-building technique in which team members are located together or as close to each other as possible.
|
|
Configuration Management
|
A process which verifies that the products of the project are complete and accurate.
|
|
Configuration Management Plan
|
A plan that defines the process for controlling change to configureable items that require formal change control.
|
|
Configuration Management System
|
A subsystem of the project management system that is used to ensure that the project creates what is intended from the details of the project management plan.
|
|
Control
|
Analyze variances between actual performance and planned performance to effect improvements.
|
|
Corrective Actions
|
Actions on a project that will correct a component of the project that is out of alignment with the baseline.
|
|
Criteria
|
Standards to which project variables are compared for acceptability.
|
|
Customer
|
The individual, group, or company that will own the work of the project when it is complete.
|
|
Develop Project Charter
|
The process of developing the project charter.
|
|
Develop Project Management Plan
|
The process of documenting the required actions to prepare and integrate the various management plans for the project.
|
|
Direct and Manage Project Execution
|
The process of performing the work defined in the project management plan.
|
|
Enterprise
|
A company, business, or other formal structure that encompasses a business function.
|
|
Enterprise Environmental Factors (Output/Input)
|
Any internal or external organization variables that can influence the project success Examples: company culture, the business market, technology, and personnel
|
|
Executing Processes
|
The coordination of personnel and additional resources to implement the project managment plan and create the deliverables of the project.
|
|
Formal Acceptance
|
Attaining signature for a piece of the project or the complete project, where the signature represents completion or closure of the project or the piece of the project.
|
|
Functional Manager
|
A manager of a department or unit in a functional organization.
|
|
Functional Organizational Structure
|
A structure within a company where people are grouped by similar skill set (e.g. accounting, marketing, engineering)
|
|
Goods
|
Projects that have been created and are available for purchase.
|
|
Historical Information
|
Information from previous projects that can be used to learn from success and failure.
|
|
Influencer
|
A person or organizaiton that is not necessarily directly related to the project but can influence the project in either a good or bad way.
|
|
Initiating Processes
|
The beginning processes in a project, which occur prior to Planning.
|
|
Initiation
|
Commitment from the sponsor and organization to start a project or to continure it to the next phase.
|
|
Initiator
|
An organization or individual authorized and capable of starting a project.
|
|
Kickoff Meeting
|
A meeting held to officially start the project.
|
|
Kill Point
|
The review of a phase to determine if it accomplished its requirements; it signals an opportunity to terminate the project if the project should not continue.
|
|
Lessons Learned
|
A process, meeting, or questionnaire (possible all) to discuss what worked and didn't work on the project, with the purpose of not repeating what didn't work and maximizing what did work correctly.
|
|
Lessons Learned Knowledge Base
|
A collection of historical information about previous projects.
|
|
Log
|
A document which tracks items that occur during a project.
|
|
Management by Projects
|
Performing day-to-day operations by a project management approach.
|
|
Matrix Organizational Structure
|
A structure within a company where people are organized by (and report to) a combination of Project and Functional Managers.
|
|
Methodology
|
A set of procedures used in project management.
|
|
Monitor and Control Project Work
|
The process of managing and controlling the Initiating, Planning, Executing, and Closing pieces of a project in accordance with the project management plan.
|
|
Monitoring and Controlling Processes
|
Actions to make sure the project objectives are completely successfully.
|
|
Operations
|
The dat-to-day repeatable activities that a company performs.
|
|
Organization
|
A group of people formed for the purpose of performing work within a company or enterprise.
|
|
Organizational Process Assets (Output/Input)
|
The various process-related assets from the organizations involved in the project work; can include templates, documentation, methods and procedures, and policies.
|
|
Payback Period
|
The amount of time needed to recover the investment in a project.
|
|
Perform Integrated Change Control
|
Apply the change control process as it relates to all project Knowledge Areas.
|
|
Performing Organization
|
The entity whose personnel are most directly involved in performing the work of the project.
|
|
Planning Processes
|
The processes required to develop the activities to attain an objective.
|
|
Portfolio
|
A gropu of programs or projects related and managed in a coordinated way to achieve specific strategic business goals.
|
|
Portfolio Management (Technique)
|
Managing various portfolios that include the projects and programs of which they consist; can include prioritization, authorization, and management.
|
|
Product Life Cycle
|
The generally sequential phases of a product.
|
|
Program
|
A group of related projects that are managed to obtain synergistic benefits and control.
|
|
Program Management
|
The management of projects in a coordinated way to achieve better results than if managed separately.
|
|
Progressive Elaboration (Technique)
|
The process of beginning a project and, as more information is discovered, adjusting the plan to reflect the information and progress.
|
|
Project
|
A temporary undertaking to create a unique product, service, or result.
|
|
Project Archives
|
A set of records that correctly describe and document the history of the project.
|
|
Project Initiation
|
The process that can result in the authorization of a project.
|
|
Project Integration Management
|
The processes used to manage all Knowledge Areas across the project life cycle; can include plan creation, execution, and change control.
|
|
Project Life Cycle
|
The process of completing work on a project. It is not the project management of the work, but rather the work processw such as the building process of creating a house. This life cycle typically coexists with the project management life cycle.
|
|
Project Management
|
An approach to meeting project objectives by utilizing defined methodology which included knowldge, skills, tools, and techniques.
|
|
Project Management Bocy of Knowledge
|
The knowledge within the profession of project management.
|
|
Project Management Information System (PMIS)
|
An information system which includes the tools and techniques used to support a project from interception through closure.
|
|
Project Management Knowledge Area
|
The nine project management knowldege areas are integreation, scope, time, cost, quality, human resources, communication, risk, and procurement.
|
|
Project Management Office
|
The central group of project management at a company; can be a centralized gropu of Project Managers or the office that standardizes policy or procedures.
|
|
Project Management Plan
|
(Formally called the project plan). A formal comprehensive document that describes how the plan of the project will be implemented and monitored; can include various management plans (from Knowldege Areas) and documents such as the work breakdown structure (WBS), project scope statement, and organizational chart.
|
|
Project Managemetn Process Groups
|
The group of processes that complete a project (Initiating, Planning, Executing, Monitoring and Controlling, and Closing.
|
|
Project Management System
|
The elements needed to manage a project: processes, tools, methods, etc.
|
|
Project Manager (PM)
|
The person responsible for ensureing the project objectives are met.
|
|
Project or Program Charter
|
The foundational document which states the main details of the project or program; typically includes the following: Scope of the project or program, any constraints and assumptions including time and cost goals, why the project or program is being done, description of project or program manager authority.
|
|
Project Phase
|
A group of project activities making up a piece of the project that interrelates with other pieces to make up the project.
|
|
Projectized Organization
|
An organization which authorizes the project manager to assign resources to the project, to establish priorityes, and to direct the work of the project.
|
|
Regulation
|
A requirement developed by a government organization.
|
|
Requested Change
|
A formal request for a change to the project that is submitted for approval via the Perform Integrated Chage Control process.
|
|
Return on Investment
|
The amount of income from a investment; income divided by the investment.
|
|
Role
|
A specific function performed by a memeber of a project team with defined behaviors and activities.
|
|
Service
|
Work performed without resulting in a physical product.
|
|
Skill
|
The capability to execute project-related activities based on individual subject matter, expertise, and abilities.
|
|
Sponsor
|
Person or group who provides the financial resources for the project.
|
|
Stakeholder
|
Peronsl or entity whose interests are positively or negatively affected by the project, or whose influence can positively or negatively affect the project.
|
|
Stakeholder Analysis
|
The process of discoveing key needs, names, positions, focus, and influences on the project of all stakeholders.
|
|
Standard
|
An established norm or requirement.
|
|
Statement of Work (SOW)
|
A description of services, prodeucts, and work results to be accomplished on a project or other initiative.
|
|
Strategic Planning
|
Long-term planning by a company (usually three to five years in the future).
|
|
Subphase
|
A division of a phase or a project.
|
|
Subproject
|
A smaller piece of the project, as a result of decomposition; is usally created as a result of creating the work breakdown structure.
|
|
System
|
An integreated set of pieces used to achieve a specific project goal; could be an actual process or management process, or some mix of both approaches.
|
|
Technical Performance Measurement (Technique)
|
A measurement approach that compares what was technically created in the project compared to what the project management plan sows should have been created.
|
|
Technique
|
A procedure executed by a resource to complete activiteis on the project.
|
|
Template
|
A partially filled-out document that can serve as a shell for completion of project documents.
|
|
Tight Matrix
|
A phrase that describes a war room or close environment for the team; can also be used as a noise answer on organizational-related questions.
|
|
Tool
|
An item such as the template of a computer application used in a project to hlep complete project work.
|
|
Trend Analysis (Technique)
|
An approach that attempts to forecast future results based on historical information.
|
|
Variance Analysis (Technique)
|
An approach that measusres the variance associated with the scope, time, or cost of the project.
|
|
Virtual Team
|
A group of people with similar goals who form a team but spend little (if any) time together.
|
|
Voice of the Customer (VOC)
|
A Planning Process that considers the requirements the customer really needs when technical requirements are created.
|
|
War Room
|
A room shared by project personnel that can be used for planning and meetings, and display charts, graphs, and various other project information.
|
|
Weighted Scoring Model
|
A project-selection technique in which criteria are devined and a weight given to it. Each project is then measured on the sum of each of those components and selections made from the result.
|
|
Work Authorization
|
A technique hich ensures that the righ work is done at the right time in the right order.
|
|
Work Authorization System
|
A system in the project management approach that allows the right work to begin at the right time (or sequence) by the right people; can be something as informal as Project Manager approval to something as formal as documented predecessors and signoff before work can begin,
|