Google Project Management key terms

A temporary effort with a defined start and end that produces a unique product, service, or result. Projects differ from ongoing operations because they conclude once their objectives have been met.

The application of knowledge, skills, tools, and techniques to plan, execute, and close work so that a project meets its goals on time, within budget, and at the required quality.

A group of related projects managed together to gain benefits that would not be achievable if each project were run separately. Programs often span several years and multiple teams.

The full collection of projects, programs, and other work an organization invests in, managed together so leaders can prioritize resources and align effort with strategic goals.

A tangible or intangible output that a project produces and hands over, such as a report, a software feature, or a finished building. Deliverables are usually tied to milestones and acceptance criteria.

The interdependent trio of scope, time, and cost that defines what a project can achieve. Changing one leg typically forces adjustments to the others, and quality sits at the center of the triangle.

A document that justifies starting a project by explaining the problem or opportunity, the expected benefits, the estimated costs, and the risk of taking no action at all.

A short, formal document that authorizes a project, names the project manager, and records the high-level goals, scope, key stakeholders, and initial risks. It gives the team authority to begin work.

The boundaries of what a project will and will not deliver, including the specific products, features, and work required. Clear scope protects the team from unplanned additions.

A one- or two-sentence summary of what the project will accomplish, expressed with measurable success criteria. Strong goal statements are specific, attainable, relevant, and time-bound.

The process of identifying everyone affected by or interested in a project and mapping their influence and interest, so the team can plan how to communicate with and engage each group.

Something a team believes to be true for planning purposes without yet having proof. Assumptions should be documented and validated, because if one proves false the plan may need to change.

A limitation that restricts the team's options, such as a fixed budget, a hard deadline, limited staff, or a regulatory requirement. Constraints shape which solutions are feasible.

The first gathering of the project team and key stakeholders, where the charter, goals, roles, timeline, and working agreements are shared so everyone starts with a common understanding.

A hierarchical breakdown of the total scope of a project into smaller, manageable pieces of work. Each branch ends in a work package that can be estimated, assigned, and tracked.

A significant point or event in the project timeline, marked by the completion of a major deliverable or an approval. Milestones have zero duration and help track progress.

A horizontal bar chart that shows tasks along a timeline, with bars representing start dates, durations, and dependencies. It gives a visual picture of the schedule.

The longest sequence of dependent tasks from project start to finish, which determines the shortest possible duration. Any delay on the critical path delays the whole project.

A relationship in which one task must wait for another before it can start or finish. Dependencies drive sequencing and are the basis for building a realistic schedule.

The amount of time a task can be delayed without pushing out the project's finish date. Tasks on the critical path have zero float; other tasks have slack to absorb delays.

A living log that records each identified risk along with its likelihood, impact, owner, and planned response, so the team can monitor and manage threats throughout the project.

A matrix that assigns each task or deliverable to people as Responsible, Accountable, Consulted, or Informed, clarifying who does the work and who makes the final call.

A document that defines who needs which information, in what format, how often, and through which channel, so stakeholders stay informed without being overwhelmed.

A regular update that summarizes progress against the plan, highlights completed work and upcoming tasks, and flags risks or issues that need attention from stakeholders.

A problem that has already happened and is currently affecting the project, as opposed to a risk, which is a possible future event. Issues need owners and resolution plans.

The formal process for requesting, reviewing, and approving or rejecting changes to scope, schedule, or budget, so modifications are documented and their impact is understood.

The practice of raising a problem to someone with more authority when the team cannot resolve it at its current level, following an agreed path and time frame.

A document created with the team that records shared values, working agreements, roles, and communication norms, helping members align on how they will collaborate.

The process of evaluating work processes to confirm they are capable of producing the required standard, preventing defects rather than catching them only after delivery.

An iterative approach to delivering work in small increments with frequent feedback, favoring collaboration, adaptability, and working results over rigid upfront plans.

A lightweight Agile framework in which a small, self-organizing team delivers work in fixed-length sprints, using defined roles, artifacts, and ceremonies to inspect and adapt.

A short, fixed time box, usually one to four weeks, during which a Scrum team completes a selected set of backlog items and produces a potentially shippable increment.

A prioritized list of everything that might be built into the product, maintained by the product owner and refined continuously so the team always works on the highest-value items.

A short, plain-language description of a feature written from the user's perspective, usually stating who wants it, what they want, and why, so the team keeps customer value in view.

A visual workflow method that limits work in progress and shows items moving through stages on a board, helping teams spot bottlenecks and deliver continuously.

A line graph showing the amount of work remaining in a sprint or project plotted against time, used to spot whether the team is on track to finish.

The final phase in which deliverables are accepted, contracts and budgets are settled, documentation is archived, and the team is released from the project.

Insights captured about what went well and what did not, recorded so future teams can repeat successes and avoid the same mistakes.

The structured transfer of a completed project's outputs, documentation, and knowledge to the group that will operate or maintain them after the project ends.