Expect More. Achieve More.
Banner Project Management Glossary of Terms
A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
Q
R
S
T
U
V
W
X
Y
Z
- A -
Activity - an individual task needed for the completion of a project. It is the smallest, discreet block of time accounted for in the WBS.
- B -
Baseline Schedule - a fixed project schedule. It is the standard by which project performance is measured. Once the baseline is set, it should not be changed unless there is a major change in the scope of the project.
Benchmark - a standard measure of output or production.
Big picture - the overall goals and results wanted from the entire project not just individual components of the project.
Business Assessment - the first phase of the project cycle. The business problem is defined, possible solutions and associated cost/benefits are outlined and recommendations are made.
- C -
Change Management - process for ensuring client satisfaction in handling their request for processing scope changes. Includes assessing the impact on costs and schedules, providing alternative solutions, obtaining sign-offs and updating the project plan.
Checkpoint Meeting - a meeting usually held quarterly with senior executives to discuss the project to date and make any recommendations as necessary.
Communications Approach - a deliverable developed during the design requirements phase and the communication design work segment. It defines internal and external audiences that require notification, the timing, a brief outline and the approval process.
Communications Design - work segment that targets the internal and external audience who needs to know about the new system/procedures and the best way to disseminate the information.
Conceptual Design - see design requirements
Constraint - Any external, management, or other factor that may confine an organization from meeting its goals or objectives.
Contingency Plan - a deliverable developed during the Detail Design Phase and the Conversion Preparation work segment. It defines alternative plans should serious problems occur during the Implementation Phase. It is often referred to as "Plan B."
Conversion - involves updating an existing system that may or may not use the same hardware. The main components that change in a conversion are the software and the data.
Conversion Approach - a deliverable that is crated during the Design Requirements Phase. It illustrates timing, identifies areas to be affected and the areas of risk associated with an implementation. It includes data scrubbing requirements.
Conversion Plan Document - A deliverable from the Conversion Planning work segment. It details all the activities associated with the conversion to the new system.
Conversion Planning - a work segment within the Detail Design Phase. It involves planning and coordinating all activities in preparation for the conversion to the new system.
Conversion Program - a program that is developed to convert information in a data base from an existing format to a new one.
Critical Activity - an activity that has zero or negative float. This activity must finish on time or the entire project will fall behind schedule.
Critical Path - the path or sequence of activities which represent the longest total time required to complete the project. A delay in any activity in the critical path causes a delay in the completion of the project.
Critical Success Factor - any business event, dependency, deliverable or other factor which, if not attained would seriously impair the likelihood of achieving a business objective.
- D -
Deliverable - documents expected to be developed in a given work segment of a project. They are delivered to specified person(s) or organization(s).
Design Requirements - The second phase of the project cycle. During this phase solutions are narrowed to a preferred choice and the approach for implementing that choice is finalized. Also known as conceptual design.
Design Requirements Document - a comprehensive document that is intended for project members. It should reflect the work products of the Design Requirements Phase.
Detail Design - the fourth phase of the project cycle. It irons out the specific steps and information needed to carry out implementation of the system.
Downstream Programs - applications or interface programs that are processed after the current program is completed.
Dress Rehearsal - simulation of a conversion event under realistic conditions so that issues can be identified and resolved prior to live implementation.
Duration - the length of time needed to complete an activity.
- E -
Elapsed Time - the total number of calendar days (excluding non-work days such as weekends and holidays) needed to complete an activity.
- F -
Float - the amount of time that an activity can slip past its duration without delaying the rest of the project.
Function - action that describes what a department, business unit, or organization is required to do.
Functional Map - deliverable developed during the Design Requirements Phase that lists all of the functions of an old system and the corresponding functions of the new system being developed.
Functional Specifications - definition of the system requirements as identified by the users who will ultimately use the system.
- G -
Gantt Chart - a graphic display of activity durations. It is also referred to as a bar chart. Activity durations are shown in the form of horizontal bars.
Green Issues - issues that can be resolved within the boundaries of the project team. The impact of the problem is limited to a small part of the project. Many of these issues stay within the team.
GUI - Graphical User Interface. pronounced as "gooey"
- H -
Hand-Off Document - document whose purpose is to maintain documentation of all incidents from conversion and implementation phases of the project. It is to signify the end of the project team's responsibility for the system. The responsibility is transferred to the functional unit.
Hardware - physical equipment used in a computer system.
- I -
Implementation - the basic objective of the project. Implementation implies that not only has the system been installed, tested, and rolled out; it also means that users have been trained and sign-off is complete.
Implementation Phase - The sixth and final phase of the project cycle. It is during this phase that the planning is complete and the system is actually moved into full production.
Input - refers to screens, procedures, and forms used to collect information or provide direction.
Installation - the act of actually placing the system onto the hardware environment. This does not mean that the system is configured or tested. It simply means that it "glows" on a screen.
Installation Phase - the third phase of the project cycle. During this phase the software is installed onto the hardware environment.
Integration Testing - part of the SIT work segment. It is to verify that the system is working properly with other up-stream and down-stream systems. Its primary purpose is to test interfaces.
Interface Requirements - the necessary outputs that one component must set up and initialize prior to establishing and calling a second component of an integrated system.
Interfaces - programs that connect to applications.
Issue Log - form that documents all concerns and issues raised during the course of a project. The list identifies person(s) or organization(s) responsible for resolving the issue and the date by which the issue should be resolved.
- J -
- K -
Kick-off Meeting - meeting held at the beginning of a project where the team members are introduced, the project's purpose is discussed and administrative issues are taken care of.
- L -
- M -
Methodology - a systematic approach designed to serve as a guideline for project work.
Microsoft Project - the standard tool for creating and maintaining work plans.
Migration - involves going from an existing system to a new system that does not use the same hardware.
Milestone - an activity with zero duration (usually marking the end of a period.)
- N -
- O -
Objectives - defines the purpose for doing something.
Output - where the information from a system is stored or printed. These items include reports, screens, files, etc.
- P -
Parallel - time at the end of the project where the old system is running concurrently with the new system and they are balanced against each other. May not be used in all projects.
Parallel Testing - test in which the new system and the concurrent systems are run simultaneously.
Phase - The six major components of a project.; Business Assessment, Design Requirements, Installation, Detail Design/Development, Testing, and Implementation.
Predecessor - an activity that must be completed (or be partially completed) before a specified activity can begin.
Preliminary Issues List - a management tool used to track problems and concerns on a project. It evolves into the Issue Log, a very important working document for the entire project team to use.
Procedures Requirements - deliverable from the Design Requirements Phase. It outlines the expected procedure differences and/or additions.
Production System - system that is actually in place and functioning in the operations environment.
Project - a one-time effort to accomplish an explicit objective by a specific time.
Project Life Cycle - the progression of phases that a project follows as it is conducted.
Project Management - a disciplined approach to planning, organizing, directing, controlling and tracking the resources required to complete a project successfully.
Project Manager - person responsible for guiding and directing the work of a project.
Project Notebook - repository of hard copies of all project related data.
Project Organization Chart - visual illustration of the project's reporting structure.
Project Plan - a generic term for the set of project control methods, including work breakdown structure, resource assignments and schedules.
- Q -
- R -
Real Time - processing data with the results available immediately.
Red Issues - also referred to as "show stoppers," these issues are critical to the success of the project as a whole. They could halt the project or seriously delay it and require the immediate attention of senior management.
Resource - anything that is assigned to an activity or needed to complete an activity. This may include equipment, people, buildings, etc. Generally, it is the individual staff members of whom the project team is composed and to whom tasks are assigned.
Risk Assessment - a document describing the perceived risks associated with a given project or set of project tasks.
Roll Out - refers to the publication of a schedule or timetable for a series of related activities.
- S -
Scheduling - the process of determining when project activities will take place depending on defined durations and precedent activities.
Scope - the project's parameters. An item is said to be either in scope or out of scope.
Sequence - the order in which activities occur with respect to one another. This establishes priority and dependencies between activities. Successor and predecessor relationships are developed in a network format. This allows those involved in the project to visualize the work flow.
SIT - System Integration Testing
Slippage - the amount of slack or float time used up by the current activity due to a delayed start. If an activity without float is delayed, the entire project will slip.
Status Meeting - usually held every week to update the team or team leaders on where the team currently stands on their deliverables due.
Status Report - progress report that lists the tasks completed to date, the tasks scheduled to be completed and any concerns and issues about the project.
Stress Test - system performance testing at high levels of volume or simultaneous transaction processing in order to test for malfunctions, processing time and response time.
Successor - an activity whose start or finish depends on the start or finish of a predecessor activity.
System Integration Testing - (SIT) the second work segment of the Testing Phase. It is made up of System Testing and Integration Testing. SIT is conducted primarily by the IT department. It does require input from the functional areas with regards to basic business functions.
System Testing - part of the SIT work segment. It is to verify that the system is working as planned and designed. It is specifically focused on the system's ability to interact with other modules in the system. Sometimes called "string testing."
Systems Architecture - the hardware, software and network structure that will confine and facilitate automated business functions and inter-company and intra-company data flows.
- T -
Task - the lowest level of detail in a work plan, tasks are the detail steps necessary to complete an activity.
Team Leader - person responsible for guiding a team through various stages of a project. Usually reports to the project manager.
Test Conditions - tests of application specific and program specific conditions designed to produce differing outputs.
Test Cycle - test cases oriented around verifying outputs that occur in differing time periods or cycles.
Test Scenarios - formalized tests that are conducted on system components or the system as a whole. They are conducted before final approval of the system. Test scenarios can be manual or automated step-by-step procedures that test the system's features, functionality, and/or throughput.
Test Script - what is to be tested and when it is to be tested during UAT.
Test System - the system to be used entirely during the testing phase of the project.
Testing Phase - the fifth phase of the project cycle. It is designed to fully prove the system will function as designed. It is made up of 4 work segments; Unit Testing, System Integration Testing, User Acceptance Testing, and Dress Rehearsal.
Training Approach - a self-contained design document developed during the Design Requirements Phase. It outlines what users can expect in terms of the type and amount of training needed to prepare them to use a new system.
- U -
UAT - User Acceptance Testing
User Acceptance Testing - (UAT) a work segment in the Testing Phase. It is the most comprehensive of all the testing work segments. It tests business functions and verifies the functional accuracy of programs, forms and procedures. It is planned and executed by a test team composed of project team members and functional area representatives.
- V -
- W -
War Room - a room or space where the project's "headquarters" exists and the team members work together usually in a constant state of activity.
WBS - Work Breakdown Structure
Work Breakdown Structure - a tool for defining the hierarchical breakdown of responsibilities and work in a project. It is a checklist of every activity that must be completed to create the end product.
Work Plan - the road map of a project. This document maps out all the tasks which will be performed, who is responsible for the task and expected completion date.