Project Management Glossary

An iterative approach to project management and software development that delivers work in small increments, emphasizing collaboration and adaptability.

The approved version of the project plan (scope, schedule, or cost) used as a reference point for measuring performance and managing changes.

A systematic process for managing all changes to the project scope, schedule, or cost, ensuring each change is formally evaluated and approved.

The longest sequence of dependent activities that determines the shortest possible project duration.

Any unique and verifiable product, result, or capability produced to complete a process, phase, or project.

The measure of work performed expressed in terms of the budget authorized for that work. A core component of Earned Value Management.

The amount of time an activity can be delayed without delaying the project completion date or violating a schedule constraint.

A type of bar chart that illustrates a project schedule, showing task durations, start and end dates, dependencies, and progress.

A time-boxed cycle of development in which a set of features is designed, built, and tested, producing a working increment.

A visual workflow management method that uses boards and cards to represent work items, with explicit limits on work in progress.

A meeting held at the start of a project or phase to align stakeholders on objectives, scope, roles, responsibilities, and communication protocols.

A significant point or event in the project timeline, often marking the completion of a major deliverable or decision point. Has zero duration.

The Project Management Body of Knowledge published by PMI, providing standard terminology, processes, and guidelines for project management.

An ordered list of all features, fixes, and technical work needed in a product, managed by the Product Owner in Scrum.

A group of related projects, subsidiary programs, and program activities managed in a coordinated manner to obtain benefits not available from managing them individually.

The process of auditing quality requirements and the results from quality control measurements to ensure appropriate quality standards are used.

The process of identifying and assigning available resources (people, equipment, budget) to project activities in the most efficient manner.

An uncertain event or condition that, if it occurs, has a positive or negative effect on one or more project objectives.

The sum of all products, services, and results to be provided by a project, including all the work required to deliver them.

An agile framework that uses fixed-length iterations (sprints), defined roles (Product Owner, Scrum Master, Development Team), and ceremonies to deliver increments.

A time-boxed period in Scrum (typically 2-4 weeks) during which a specific set of work must be completed and made ready for review.

Any individual, group, or organization that can affect, be affected by, or perceive itself to be affected by a project.

A sequential, linear project management approach where each phase must be completed before the next begins, with little room for iteration.

A hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives.

The lowest level of the WBS, representing a discrete piece of work that can be estimated, scheduled, monitored, and controlled.