Accept: The act of formally receiving or acknowledging something and regarding it as being true, sound, suitable, or complete
Acceptance: The formal process of accepting delivery of a product or a deliverable.
Acceptance Criteria: Those criteria, including performance requirements and essential conditions, which must be met before project deliverables are accepted.
Acceptance Test: Formal, pre-defined test conducted to determine the compliance of the deliverable item(s) with the acceptance criteria.
Accrued Costs: Costs that are earmarked for the project and for which payment is due, but has not been made.
Acquire Project Team [process]: The process of obtaining the human resources needed to complete the project.
Accountability Matrix: See responsibility assignment matrix.
Accrued Costs: Earmarked for the project and for which payment is due, but has not been made.
Acquisition strategy: Determining the most appropriate means of procuring the component parts or services of a project
Action Item: Something agreed to be done by a person as a result of a discussion at a meeting and usually recorded in the minutes or log of the meeting.
Active: Project status describing an approved initiative or project with applied resource and management activities.
Activity: 1- A component of work performed during the course of a project. See also schedule activity 2- Task, job, operation or process consuming time and possibly other resources.
Activity Attributes [output/input]: Multiple attributes associated with each schedule activity that can be included within the activity list. Activity attributes include activity codes, predecessor activities, successor activities, logical relationship, leads and lags, resource requirements, imposed dates, constraints and assumptions
Activity Code: One or more numerical or text values that identify characteristics of the work or in some way categorize the schedule activity that allows filtering and ordering of activities within reports.
Activity Definition [process]: The process of identifying the specific schedule activities that need to be performed to produce the various project deliverables.
Activity Description (AD) : A short phrase or label for each schedule activity used in conjunction with an activity identifier to differentiate that the project schedule activity from other schedule activities. The activity description normally describes the scope of work of the schedule activity.
Activity Duration: 1- The time in calendar units between the start and finish of a schedule activity. See also actual duration, original duration, and remaining duration. 2- Specifies the length of time (hours, days, weeks, months) that it takes to complete an schedule activity.
Activity Duration Estimating [process] : 1- Estimating the number of work periods which will be needed to complete individual activities. 2- The process of estimating the number of work periods that will be needed to complete individual schedule activities
Activity File: See activity list.
Activity Identifier/ID: A short unique numeric or text identification assigned to each schedule activity to differentiate that project activity from other activities. Typically unique within any one project schedule network diagram.
Activity List [input/output]: A documented tabulation of schedule activities that shows the activity description, activity identifier, and a sufficient detailed scope of work description so project team members understand what work is to be performed.
Activity-on-Arrow (AOA): See arrow diagramming method
Activity-on-Node (AON): See precedence diagramming method
Activity Resource Estimating [process]: The process of estimating the time and quantities of resources required to perform each schedule activity
Actual Cost : Incurred costs that are charged to the project budget and for which payment has been made, or accrued.
Activity Sequencing [process]: The process of identifying and documenting dependencies among schedule activities
Actual Cost (AC): Total costs actually incurred and recorded in accomplishing work performed during a given time period for a schedule activity or work breakdown structure component. Actual cost can sometimes be direct labor hours alone, direct cost alone, or all costs including indirect costs. Also referred to as the actual cost of work performed (ACWP).
Actual Cost of Work Performed: See actual cost
Acceptance: The formal process of accepting delivery of a product or a deliverable.
Acceptance Criteria: Those criteria, including performance requirements and essential conditions, which must be met before project deliverables are accepted.
Acceptance Test: Formal, pre-defined test conducted to determine the compliance of the deliverable item(s) with the acceptance criteria.
Accrued Costs: Costs that are earmarked for the project and for which payment is due, but has not been made.
Acquire Project Team [process]: The process of obtaining the human resources needed to complete the project.
Accountability Matrix: See responsibility assignment matrix.
Accrued Costs: Earmarked for the project and for which payment is due, but has not been made.
Acquisition strategy: Determining the most appropriate means of procuring the component parts or services of a project
Action Item: Something agreed to be done by a person as a result of a discussion at a meeting and usually recorded in the minutes or log of the meeting.
Active: Project status describing an approved initiative or project with applied resource and management activities.
Activity: 1- A component of work performed during the course of a project. See also schedule activity 2- Task, job, operation or process consuming time and possibly other resources.
Activity Attributes [output/input]: Multiple attributes associated with each schedule activity that can be included within the activity list. Activity attributes include activity codes, predecessor activities, successor activities, logical relationship, leads and lags, resource requirements, imposed dates, constraints and assumptions
Activity Code: One or more numerical or text values that identify characteristics of the work or in some way categorize the schedule activity that allows filtering and ordering of activities within reports.
Activity Definition [process]: The process of identifying the specific schedule activities that need to be performed to produce the various project deliverables.
Activity Description (AD) : A short phrase or label for each schedule activity used in conjunction with an activity identifier to differentiate that the project schedule activity from other schedule activities. The activity description normally describes the scope of work of the schedule activity.
Activity Duration: 1- The time in calendar units between the start and finish of a schedule activity. See also actual duration, original duration, and remaining duration. 2- Specifies the length of time (hours, days, weeks, months) that it takes to complete an schedule activity.
Activity Duration Estimating [process] : 1- Estimating the number of work periods which will be needed to complete individual activities. 2- The process of estimating the number of work periods that will be needed to complete individual schedule activities
Activity File: See activity list.
Activity Identifier/ID: A short unique numeric or text identification assigned to each schedule activity to differentiate that project activity from other activities. Typically unique within any one project schedule network diagram.
Activity List [input/output]: A documented tabulation of schedule activities that shows the activity description, activity identifier, and a sufficient detailed scope of work description so project team members understand what work is to be performed.
Activity-on-Arrow (AOA): See arrow diagramming method
Activity-on-Node (AON): See precedence diagramming method
Activity Resource Estimating [process]: The process of estimating the time and quantities of resources required to perform each schedule activity
Actual Cost : Incurred costs that are charged to the project budget and for which payment has been made, or accrued.
Activity Sequencing [process]: The process of identifying and documenting dependencies among schedule activities
Actual Cost (AC): Total costs actually incurred and recorded in accomplishing work performed during a given time period for a schedule activity or work breakdown structure component. Actual cost can sometimes be direct labor hours alone, direct cost alone, or all costs including indirect costs. Also referred to as the actual cost of work performed (ACWP).
Actual Cost of Work Performed: See actual cost
PMP Preparation Books on Amazon
Actual Duration: The time in calendar units between the actual start date of the schedule activity and either the data date of the project schedule if the project schedule is in progress or the actual finish date if the schedule activity is complete.
Actual Finish Date (AF): The point in time that work actually ended on a schedule activity. (Note: in some application areas, the activity is considered "finished" when work is "substantially complete.")
Actual Start Date (AS): The point in time that work actually started on an schedule activity
Administrative Closure: Generating, gathering, and disseminating information to formalize project completion.
APIs: Application Programming Interface
Analogous Estimating [technique]: An estimating technique that uses the values of parameters, such as scope, cost, budget, and duration or measures of scale such as size, weight and complexity from a previous, similar activity as the basis for estimating the same parameter or measure for a future activity. It is frequently used to estimate a parameter when there is a limited amount of detailed information about the project (e.g. in the early phases). Analogous estimating is a form of expert judgment. Analogous estimating is most reliable when the previous activities are similar in fact and not just in appearance, and the project team members preparing the estimates have the needed expertise.
Application Area: A category of projects that have common components significant in such projects, but are not needed or present in all projects. Application areas usually defined in terms of either the product (i.e., by similar technologies or production methods) or the type of customer (i.e., internal versus external, government versus commercial) or industry sector (i.e., utilities, automotive, aerospace, information technologies). Application areas can overlap.
Apportioned Effort (AE): Effort applied to project work that is not readily divisible into discrete efforts for that work, but which is related in direct proportion to measurable discrete work efforts. Contrast with discrete effort
Approval: See approve
Approve: The act of formally confirming, sanctioning, ratifying, or agreeing to something
Approved Change Request [input/output]: A change request that has been processed through the integrated change control process and approved. Contrast with requested change.
Arrow: The graphic presentation of a schedule activity in the arrow diagramming method or a logical relationship between schedule activities in the precedence diagramming method.
Arrow Diagramming Method (ADM) [technique]: A schedule network diagramming technique in which schedule activities are represented by arrows. The tail of the arrow represents the start, and the head represents the finish of the schedule activity. (The length of the arrow does not represent the finish of the schedule activity.) Schedule activities are connected at points called nodes (usually drawn as small as circles) to illustrate the sequence in which the schedule activities are expected to be performed. See also precedence diagramming method.
As-of Date: See data date.
Assumptions [input/output]: Assumptions are factors that, for planning purposes, are considered to be true, real or certain without proof or demonstration. Assumptions affect all aspects of project planning, and are part of the progressive elaboration of the project. Project teams frequently identify, document, and validate assumptions as part of their planning process. Assumptions generally involve a degree of risk.
Assumptions Analysis [technique]: A technique that explores the accuracy of assumptions and identifies risks to the project from inaccuracy, inconsistency, or incompleteness of assumptions.
Authority: The right to apply project resources*, expend funds, make decisions, or give approvals.
As Late As Possible (ALAP) : An schedule activity for which the early start date is set as late as possible without delaying the early dates of any successor.
Associated Revenue: That part of a project cost that is of a revenue nature and therefore charged as incurred to the profit and loss account. Note: associated revenue differs from the capital element of the project in that the capital element is taken as an asset to the balance sheet and depreciated over future accounting periods.
As Soon As Possible (ASAP): An activity for which the early start date is set to be as soon as possible. This is the default activity type in most project management systems.
Audit: Systematic retrospective examination of the whole, or part, of a project or function to measure conformance with predetermined standards. Note: audit is usually qualified, for example financial audit, quality audit, design audit, project audit, health and safety audit.
Authorization: The decision that triggers the allocation of funding needed to carry on the project
Authorized Un-priced Work (AUW): Any scope change for which authorization to proceed has been given, but for which the estimated costs are not yet settled.
Authorized Work: The effort which has been defined, plus that work for which authorization has been given, but for which defined contract costs have not been agreed upon.
Automatic Decision Event: Decision event where the decision depends only on the outcome of the preceding activities and that can be programmed or made automatic.
Actual Finish Date (AF): The point in time that work actually ended on a schedule activity. (Note: in some application areas, the activity is considered "finished" when work is "substantially complete.")
Actual Start Date (AS): The point in time that work actually started on an schedule activity
Administrative Closure: Generating, gathering, and disseminating information to formalize project completion.
APIs: Application Programming Interface
Analogous Estimating [technique]: An estimating technique that uses the values of parameters, such as scope, cost, budget, and duration or measures of scale such as size, weight and complexity from a previous, similar activity as the basis for estimating the same parameter or measure for a future activity. It is frequently used to estimate a parameter when there is a limited amount of detailed information about the project (e.g. in the early phases). Analogous estimating is a form of expert judgment. Analogous estimating is most reliable when the previous activities are similar in fact and not just in appearance, and the project team members preparing the estimates have the needed expertise.
Application Area: A category of projects that have common components significant in such projects, but are not needed or present in all projects. Application areas usually defined in terms of either the product (i.e., by similar technologies or production methods) or the type of customer (i.e., internal versus external, government versus commercial) or industry sector (i.e., utilities, automotive, aerospace, information technologies). Application areas can overlap.
Apportioned Effort (AE): Effort applied to project work that is not readily divisible into discrete efforts for that work, but which is related in direct proportion to measurable discrete work efforts. Contrast with discrete effort
Approval: See approve
Approve: The act of formally confirming, sanctioning, ratifying, or agreeing to something
Approved Change Request [input/output]: A change request that has been processed through the integrated change control process and approved. Contrast with requested change.
Arrow: The graphic presentation of a schedule activity in the arrow diagramming method or a logical relationship between schedule activities in the precedence diagramming method.
Arrow Diagramming Method (ADM) [technique]: A schedule network diagramming technique in which schedule activities are represented by arrows. The tail of the arrow represents the start, and the head represents the finish of the schedule activity. (The length of the arrow does not represent the finish of the schedule activity.) Schedule activities are connected at points called nodes (usually drawn as small as circles) to illustrate the sequence in which the schedule activities are expected to be performed. See also precedence diagramming method.
As-of Date: See data date.
Assumptions [input/output]: Assumptions are factors that, for planning purposes, are considered to be true, real or certain without proof or demonstration. Assumptions affect all aspects of project planning, and are part of the progressive elaboration of the project. Project teams frequently identify, document, and validate assumptions as part of their planning process. Assumptions generally involve a degree of risk.
Assumptions Analysis [technique]: A technique that explores the accuracy of assumptions and identifies risks to the project from inaccuracy, inconsistency, or incompleteness of assumptions.
Authority: The right to apply project resources*, expend funds, make decisions, or give approvals.
As Late As Possible (ALAP) : An schedule activity for which the early start date is set as late as possible without delaying the early dates of any successor.
Associated Revenue: That part of a project cost that is of a revenue nature and therefore charged as incurred to the profit and loss account. Note: associated revenue differs from the capital element of the project in that the capital element is taken as an asset to the balance sheet and depreciated over future accounting periods.
As Soon As Possible (ASAP): An activity for which the early start date is set to be as soon as possible. This is the default activity type in most project management systems.
Audit: Systematic retrospective examination of the whole, or part, of a project or function to measure conformance with predetermined standards. Note: audit is usually qualified, for example financial audit, quality audit, design audit, project audit, health and safety audit.
Authorization: The decision that triggers the allocation of funding needed to carry on the project
Authorized Un-priced Work (AUW): Any scope change for which authorization to proceed has been given, but for which the estimated costs are not yet settled.
Authorized Work: The effort which has been defined, plus that work for which authorization has been given, but for which defined contract costs have not been agreed upon.
Automatic Decision Event: Decision event where the decision depends only on the outcome of the preceding activities and that can be programmed or made automatic.
What is Project Management?
Project Management is the discipline of planning, organizing, and managing resources to bring about the successful completion of specific project goals and objectives. A project is a finite endeavor-having specific start and completion dates-undertaken to create a unique product or service which brings about beneficial change or added value. This finite characteristic of projects stands in sharp contrast to processes, or operations, which are permanent or semi-permanent functional work to repetitively produce the same product or service. In practice, the management of these two systems is often found to be quite different, and as such requires the development of distinct technical skills and the adoption of separate management philosophy, which is the subject of this article.
For more information about project management please visit "What is project management?" lens.
For more information about project management please visit "What is project management?" lens.
References and External Links
Business Related Lenses
-
In the Course of Managing an ERP Implementation Project
-
The meeting was attended by the entire senior management, members of the ERP implementation team and the project managers from both the customer and the vendor. In fact, since all top level management were also members of the ERP implementation team,...
