| Terms |
Definitions |
|
CPF
|
Cost-Plus-Fee
|
|
Controlling
|
See control.
|
|
AD
|
Activity Description
|
|
EV
|
Earned Value
|
|
Phase
|
See project phase.
|
|
PS
|
Planned Start date
|
|
EVM
|
Earned Value Management
|
|
TC
|
Target Completion date
|
|
outcome
|
n. result, effect
|
|
no
|
is scrum/SCRUM/Scrum an acronym?
|
|
opportunities
|
chances to improve the organization
|
|
Program
|
A group of interrelated Projects
|
|
Operations
|
An organizational function performing the ongoing execution of activities that produce the same product or provide a repetitive service. Examples are: production operations, manufacturing operations, and accounting operations.
|
|
Contingency
|
See reserve. Contingency Allowance. See reserve.
|
|
Project
|
Unique, one-time operations designed to accomplish an objective in a set time frame, usually with a set budget
|
|
Green Computing
|
Developing and using computer resources in an efficient way to improve economic viability, social responsibility, and environmental impact.
|
|
special demands on PM
|
*acquire adequate resources*acquire/motivate personnel*deal with obstacles*make trade offs*breadth of communication*negotiation
|
|
project proposals
|
-a project bid-requires detailed analysis of the project-can take weeks or months to complete-may result in not bidding on the project
|
|
timeboxing
|
separating a project into different time segments, each with its own deliverables, deadline and budget
|
|
Expected value
|
A statistical technique that calculates the average outcome when the future includes scenarios that may or may not happen.” A common use for this technique is with decision tree analysis.
|
|
Control [Technique]
|
Comparing actual performance with planned performance, analyzing variances, assessing trends to effect process improvements, evaluating possible alternatives, and recommending appropriate corrective action as needed.
|
|
Networking [Technique]
|
Developing relationships with persons who may be able to assist in the achievement of objectives and responsibilities.
|
|
Work
|
Sustained physical or mental effort, exertion, or exercise of skill to overcome obstacles and achieve an objective.
|
|
Network Diagram:
|
A schematic display that illustrates the various tasks in a project as well as their sequential relationship
|
|
Project management
|
The application of knowledge, skills, tools and techniques to project activities to meet project requirements
|
|
project selection and criteria of choice
|
*project selection:-evaluating-choosing-implementing*same process as other business decisions**Look at table 2-1 pg 44
|
|
accounting data
|
-cost and revenue are linear-cost revenue data derived using standard cost standardization revenue assumptions -costs may include overhead
|
|
Statement of Work
|
includes project objective, a description of the owrk of the project, concise specifications of the product or services required, and a project schedule.
|
|
Front loading (budget/resources)
|
Distributes more funding/resources at the start of an activity or project than toward the end
|
|
Process Related Mistakes
|
System development mistakes arising from insufficient planning, overly optimistic schedules, or planning to catch up later
|
|
Float
|
Also called slack. See total float and see also free float.
|
|
Performance Reports [Output/Input]
|
Documents and presentations that provide organized and summarized work performance information, earned value management parameters and calculations, and analyses of project work progress and status. Common formats for performance reports include bar charts, S-curves, histograms, tables, and project schedule network diagram showing current schedule status.
|
|
Estimate [Output/Input]
|
A quantitative assessment of the likely amount or outcome. Usually applied to project costs, resources, effort, and durations and is usually preceded by a modifier (i.e., preliminary, conceptual, feasibility, order-of-magnitude, definitive). It should always include some indication of accuracy (e.g., ±x percent).
|
|
Buyer
|
The acquirer of products, services, or results for an organization.
|
|
Project Team
|
All the project team members, including the project management team, the project manager and, for some projects, the project sponsor.
|
|
Project Phase
|
A collection of logically related project activities*, usually culminating in the completion of a major deliverable. Project phases (also called phases) are mainly completed sequentially, but can overlap in some project situations. Phases can be subdivided into subphases and then components, this hierarchy. if the project or portions of the project are divided into phases, is contained in the work breakdown structure. A project phase is a component of a project life cycle. A project phase is not a project management process group*.
|
|
Milestone Schedule [Tool]
|
A summary-level schedule that identifies the major schedule milestones. See also master schedule.
|
|
..., promotes a common lexicon for discussing, writing, and applying project management.
|
seldom
|
|
I.S. Planning:
|
An orderly means of assessing the information needs of an organization and defining the systems, databases, and technologies that will best satisfy those needs.
|
|
Bottom up Estimate:
|
An estimating technique in which complex activities are further decomposed to a point where more accurate estimates can be made
|
|
requirement
|
a condition or capability that must be met or possessed by a system, product, service, result, or component to satisfy a contract, standard, specification, or other formal document
|
|
systems approach
|
a holistic and analytical approach to solving complex problems that includes using a systems philosophy systems analysis and systems management
|
|
initiating processes
|
defining and authorizing a project or project phase
|
|
project buildup
|
*conflicts tend to be technical in nature*conflicts tend to be btwn project manager and line managers
|
|
How do you calculate Risk Reserve?
|
Risk Impact*Risk Probability
|
|
4 agile manifesto values
|
individuals and interactions over processes and toolsworking software over comprehensive documentationcustomer collaboration over contract negotiationresponding to change over following a plan
|
|
Organizational breakdown structure
(OBS)
|
A depiction of the project organization arranged so as to relate work deliverables to organizational units.
|
|
On-Demand Computing
|
Use of computing resources on the basis of users' needs, often on a pay-per-use basis. Also called utility computing.
|
|
Dogmatic Philosophy
|
a philosophy of project control that emphasizes strict adherence to the project plan, with little tolerance for deviations.
|
|
Initiating Processes [Process Group]
|
Those processes performed to authorize and define the scope of a new phase or project or that can result in the continuation of halted project work. A large number of the initiating processes are typically done outside the project's scope of control by the organization, program, or portfolio processes and those processes provide input to the project's initiating processes group.
|
|
Level of Effort (LOE)
|
Support-type activity (e.g., seller or customer liaison, project cost accounting, project management, etc.), which does not produce definitive end products. It is generally characterized by a uniform rate of work performance over a period of time determined by the activities supported.
|
|
Technical Performance Measurement [Technique]
|
A performance measurement technique that compares technical accomplishments during project execution to the project management plan's schedule of planned technical achievements. It may use key technical parameters of the product produced by the project as a quality metric. The achieved metric values are part of the work perfbrmance information.
|
|
Work Breakdown Structure (WBS) [Output/Input]
|
A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project. Each descending level represents an increasingly detailed definition of the project work. The WBS is decomposed into work packages. The deliverable orientation of the hierarchy includes both internal and external deliverables. See also work package, control account, contract work breakdown structure, and project summary work breakdown structure.
|
|
Role
|
A defined function to be performed by a project team member, such as testing, filing, inspecting, coding.
|
|
Retainage
|
A portion of a contract payment that is withheld until contract completion to ensure full performance of the contract terms.
|
|
The project team, as a working unit, seldom outlives the project.
|
adhere
|
|
One time Cost:
|
A cost associated with project start up and development or system start up
|
|
weighted scoring model
|
a technique that provides a systematic process for basing project selection on numerous criteria
|
|
project life cycle
|
A collection of projects phases such as concept, development, implementation, and close out
|
|
partnering, chartering, and change
|
*use of subcontractors*use of input from two or more functional units*mgmt of change
|
|
payback period
|
*the length of time until the original investment has been recouped by the project*a shorter payback period is better
|
|
critical path method/analysis
|
method that uses list of activities, duration of activities, and dependencies to determine longest path and prioritize activities
|
|
Responsibility assignment matrix
(RAM)
|
A structure that relates the project team members to the WBS to ensure that each element of the project’s scope of work is assigned to a responsible individual or role.
|
|
Requesting Seller Response
|
The process of obtaining responses to the procurement documents produced during plan contracting
|
|
Earned Value (EV)
|
The value of work performed expressed in terms of the approved budget assigned to that work for a schedule activity or work breakdown structure component. Also referred to as the budgeted cost of work performed (BCWP).
|
|
Pareto Chart [Tool]
|
A histogram, ordered by frequency of occurrence, that shows how many results were generated by each identified cause.
|
|
Remaining Duration (RD)
|
The time in calendar units, between the data date of the project schedule and the finish date of a schedule activity that has an actual start date. This represents the time needed to complete a schedule activity where the work is in progress.
|
|
Risk Breakdown Structure (RBS) [Tool]
|
A hierarchically organized depiction of the identified project risks* arranged by risk category and subcategory that identifies the various areas and causes of potential risks. The risk breakdown structure is often tailored to specific project types.
|
|
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 amlow does not represent the expected duration of the schedule activity.) Schedule activities are connected at points called nodes (usually drawn as small circles) to illustrate the sequence in which the schedule activities are expected to be performed. See also precedence diagramming method.
|
|
Specification Limits
|
The area, on either side of the centerline, or mean, of data plotted on a control chart that meets the customer's requirements for a product or service. This area may be greater than or less than the area defined by the control limits. See also control limits.
|
|
Flowcharting [Technique]
|
The depiction in a diagram format of the inputs, process actions, and outputs of one or more processes within a system.
|
|
FIVE PROCESS GROUPS PERFORMED DURING EACH PHASE OF THE PROJECT LIFE CYCLE.
|
INITIATING, PLANNING, EXECUTING, CONTROLLING, CLOSING
|
|
Project management tools and techniques
|
assist project managers and their teams in carrying out work in all nine knowledge areas
|
|
Tight Matrix
|
Collocating the team. Is not a form of organization
|
|
Float
|
The amount of time that a task in a project network can be delayed without causing a delay to subsequent tasks and or the project completion date.
|
|
Cost of Quality (COQ) [Technique]
|
Determining the costs incurred to ensure qualitt. Prevention and appraisal costs (cost of conformance) include costs for quality planning, quality control (QC), and quality assurance to ensure compliance to requirements (i.e., training, QC systems, etc.). Failure costs (cost of non-conformance) include costs to rework products, components, or processes that are non-compliant, costs of warranty work and waste, and loss of reputation.
|
|
Acquire Project Team [Process]
|
The process of obtaining the human resources needed to complete the project.
|
|
Resource Histogram
|
A bar chart showing the amount of time that a resource is scheduled to work over a series of time periods. Resource availability may be depicted as a line for comparison purposes. Contrasting bars may show actual amounts of resource used as the project progresses.
|
|
WHAT IS A SCOPE STATEMENT?
|
PROVIDES A DOCUMENTED BASIS FOR MAKING FUTURE PROJECT DECISIONS. IT IS A REFINEMENT OF PROJECT CHARTER.
|
|
How do you calculiate Variance at Completion (EVA)
|
First calculate CPI (EV/AC)Then calculate EAC(BAC/CPI)then calculate Variance @ Completion (BAC-EAC)
|
|
Contract Statement of Work (SOW) [Output/Input]
|
A narrative description of products, services, or results to be supplied under contract.
|
|
Duration (DU or DUR)
|
The total number of work periods (not including holidays or other nonworking periods) required to complete a schedule activity or work breakdown structure component. Usually expressed as workdays or workweeks. Sometimes incorrectly equated with elapsed time. Contrast with effort. See also original duration, remaining duration, and actual duration.
|
|
What is a Type X manager?
|
One who believes people should be closely managed
|
|
Budgeted Cost of Work Performed (BCWP)
|
See earned value (Elf). Budgeted Cost of Work Scheduled (BCWS). See planned value (P V). Buffer. See reserve.
|
|
What's the purpose of an issue log?
|
-to allocate a unique number to each project issue-to record the type of project issue-provide a summary, analysis and status of the issues encountered during the project.
|
