Glossary of project management

Last updated

A glossary of terms relating to project management and consulting.

Contents

A

B

C

Capability maturity model. Capability Maturity Model.jpg
Capability maturity model.
PERT chart with two critical paths. Pert chart colored.svg
PERT chart with two critical paths.

D

E

Event chain diagram EventChain.jpg
Event chain diagram

F

G

A Gantt chart. GanttChartAnatomy.svg
A Gantt chart.

H

I

K

L

M

N

O

P

Project Management Triangle Project-triangle-en.svg
Project Management Triangle

Q

R

S

The systems development life cycle. CPT-SystemLifeSycle.svg
The systems development life cycle.

T

U

The Unified Process. UnifiedProcessProjectProfile20060708.png
The Unified Process.

V

W

A work breakdown structure. Product-oriented work breakdown structure of an aircraft system.png
A work breakdown structure.

Related Research Articles

Project management is the process of leading the work of a team to achieve all project goals within the given constraints. This information is usually described in project documentation, created at the beginning of the development process. The primary constraints are scope, time, and budget. The secondary challenge is to optimize the allocation of necessary inputs and apply them to meet pre-defined objectives.

<span class="mw-page-title-main">Work breakdown structure</span> A deliverable-orientated breakdown of a project into smaller components.

A work-breakdown structure (WBS) in project management and systems engineering is a deliverable-oriented breakdown of a project into smaller components. A work breakdown structure is a key project management element that organizes the team's work into manageable sections. The Project Management Body of Knowledge defines the work-breakdown structure as a "hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables."

Project management software (PMS) can help plan, organize, and manage resource tools and develop resource estimates. Depending on the sophistication of the software, it can manage estimation and planning, scheduling, cost control and budget management, resource allocation, collaboration software, communication, decision-making, quality management, time management and documentation or administration systems. Numerous PC and browser-based project management software and contract management software products and services are available.

The rational unified process (RUP) is an iterative software development process framework created by the Rational Software Corporation, a division of IBM since 2003. RUP is not a single concrete prescriptive process, but rather an adaptable process framework, intended to be tailored by the development organizations and software project teams that will select the elements of the process that are appropriate for their needs. RUP is a specific implementation of the Unified Process.

<span class="mw-page-title-main">Project manager</span> Professional in the field of project management

A project manager is a professional in the field of project management. Project managers have the responsibility of the planning, procurement and execution of a project, in any undertaking that has a defined scope, defined start and a defined finish; regardless of industry. Project managers are first point of contact for any issues or discrepancies arising from within the heads of various departments in an organization before the problem escalates to higher authorities, as project representative.

In project management, a schedule is a listing of a project's milestones, activities, and deliverables. Usually dependencies and resources are defined for each task, then start and finish dates are estimated from the resource allocation, budget, task duration, and scheduled events. A schedule is commonly used in the project planning and project portfolio management parts of project management. Elements on a schedule may be closely related to the work breakdown structure (WBS) terminal elements, the Statement of work, or a Contract Data Requirements List.

<span class="mw-page-title-main">Requirements analysis</span> Engineering process

In systems engineering and software engineering, requirements analysis focuses on the tasks that determine the needs or conditions to meet the new or altered product or project, taking account of the possibly conflicting requirements of the various stakeholders, analyzing, documenting, validating and managing software or system requirements.

<span class="mw-page-title-main">Systems development life cycle</span> Systems engineering terms

In systems engineering, information systems and software engineering, the systems development life cycle (SDLC), also referred to as the application development life cycle, is a process for planning, creating, testing, and deploying an information system. The SDLC concept applies to a range of hardware and software configurations, as a system can be composed of hardware only, software only, or a combination of both. There are usually six stages in this cycle: requirement analysis, design, development and testing, implementation, documentation, and evaluation.

<span class="mw-page-title-main">Product lifecycle</span> Duration of processing of products from inception, to engineering, design & manufacture

In industry, product lifecycle management (PLM) is the process of managing the entire lifecycle of a product from its inception through the engineering, design and manufacture, as well as the service and disposal of manufactured products. PLM integrates people, data, processes, and business systems and provides a product information backbone for companies and their extended enterprises.

ISO/IEC/IEEE 12207Systems and software engineering – Software life cycle processes is an international standard for software lifecycle processes. First introduced in 1995, it aims to be a primary standard that defines all the processes required for developing and maintaining software systems, including the outcomes and/or activities of each process.

Within quality management systems (QMS) and information technology (IT) systems, change control is a process—either formal or informal—used to ensure that changes to a product or system are introduced in a controlled and coordinated manner. It reduces the possibility that unnecessary changes will be introduced to a system without forethought, introducing faults into the system or undoing changes made by other users of software. The goals of a change control procedure usually include minimal disruption to services, reduction in back-out activities, and cost-effective utilization of resources involved in implementing change. According to the Project Management Institute, change control is a "process whereby modifications to documents, deliverables, or baselines associated with the project are identified, documented, approved, or rejected."

In agile principles, timeboxing allocates a maximum unit of time to an activity, called a timebox, within which a planned activity takes place. It is used by agile principles-based project management approaches and for personal time management.

Construction management (CM) aims to control the quality of a project's scope, time, and cost to maximize the project owner's satisfaction. It uses project management techniques and software to oversee the planning, design, construction and closeout of a construction project safely, on time, on budget and within specifications.

Requirements management is the process of documenting, analyzing, tracing, prioritizing and agreeing on requirements and then controlling change and communicating to relevant stakeholders. It is a continuous process throughout a project. A requirement is a capability to which a project outcome should conform.

Software project management is the process of planning and leading software projects. It is a sub-discipline of project management in which software projects are planned, implemented, monitored and controlled.

Internet-Speed Development is an Agile Software Development development method using a combined spiral model/waterfall model with daily builds aimed at developing a product with high speed.

The following outline is provided as an overview of and topical guide to business management:

<span class="mw-page-title-main">Project management triangle</span> Model of the constraints of project management

The project management triangle is a model of the constraints of project management. While its origins are unclear, it has been used since at least the 1950s. It contends that:

  1. The quality of work is constrained by the project's budget, deadlines and scope (features).
  2. The project manager can trade between constraints.
  3. Changes in one constraint necessitate changes in others to compensate or quality will suffer.

In software engineering, a software development process or software development life cycle (SDLC) is a process of planning and managing software development. It typically involves dividing software development work into smaller, parallel, or sequential steps or sub-processes to improve design and/or product management. The methodology may include the pre-definition of specific deliverables and artifacts that are created and completed by a project team to develop or maintain an application.

The following outline is provided as an overview of and topical guide to project management:

References

  1. Peter Schuh (2005). Integrating Agile Development in the Real World. ebrary, Inc. p.2.
  2. AACE International's Recommended Practice 11R-88, Required Skills and Knowledge of Cost Engineering, provides some answers which are excerpted here. Beyond being a guiding document for AACE International’s education and certification developments, 11R-88 is an excellent reference for industry core competency and career model development.
  3. The PRINCE2 Guide - A to Z Archived 2007-09-27 at the Wayback Machine .
  4. Project Management Institute (2004). A Guide to the Project management body of knowledge: PMBOK Guide. 3rd Edition. Newtown Square, Pennsylvania, Project Management Institute, p. 5.
  5. DIN 69901
  6. "Archived copy" (PDF). Archived from the original (PDF) on 2007-03-22. Retrieved 2008-11-30.{{cite web}}: CS1 maint: archived copy as title (link)
  7. Project Management Body of Knowledge (PMBOK), 2000 Edition
  8. Harold Kerzner (2003). Project Management: A Systems Approach to Planning, Scheduling, and Controlling (8th ed.). Wiley. ISBN   0-471-22577-0.
  9. "Resource levelling". Archived from the original on February 4, 2015. Retrieved June 27, 2015.
  10. "IBM Spectrum Symphony Documentation". IBM .
  11. ATALI, OZHAN (31 March 2020). Data-Driven Project Management: Spreadsheets and Finance. USA: Wremia, Inc. p. 17. ISBN   9780578670300. LCCN   2020935979.
  12. "IEEE Standard Glossary of Software Engineering Terminology," IEEE std 610.12-1990, 1990, quoted at the beginning of Chapter 1: Introduction to the guide "Guide to the Software Engineering Body of Knowledge". February 6, 2004. Archived from the original on 2008-01-18. Retrieved 2008-02-21.
  13. A Guide to the Project Management Body of Knowledge (pmbok Guide), Fifth Edition. 5th ed. Newtown Square, Pa.: Project Management Institute, 2013.
  14. "Systems Development Life Cycle". In: Foldoc(2000-12-24)
  15. "Value Methodology Standard" (PDF). Archived from the original (PDF) on 2009-03-19. Retrieved 2008-12-01.