Dictionary Wiki
Project teams use a lot of shared shorthand. Some of it describes how work is planned, some explains who makes decisions, and some helps people spot trouble before it derails the schedule. Whether a team follows Agile, Scrum, Waterfall, or a hybrid approach, the same core language shows up in meetings, reports, contracts, and planning documents. This guide explains the project management terms you are most likely to hear and use.
Contents at a Glance
- 1. Core Project Management Ideas
- 2. Stages in a Project’s Life
- 3. Language Used in Agile
- 4. Terms from the Scrum Framework
- 5. Traditional and Waterfall Language
- 6. Requirements and Project Boundaries
- 7. Time, Schedules, and Tracking
- 8. Vocabulary for Managing Risk
- 9. Communication and Stakeholder Terms
- 10. Building Fluency in PM Terms
1. Core Project Management Ideas
Before a team can manage work well, everyone needs the same basic understanding of what a project is, who is involved, and what limits the work must stay within.
Project — A temporary effort created to produce a distinct product, service, or outcome, with a clear start and finish, defined goals, and limits on scope, time, and resources.
Project manager — The person accountable for organizing, guiding, and closing the project while coordinating people and resources so the agreed objectives are achieved within set constraints.
Triple constraint — The three major pressures that compete on nearly every project: scope, or what must be delivered; time, or when it is due; and cost, or the available budget. It is also called the project management triangle.
Deliverable — A concrete or intangible output created through project work and provided to meet project goals, stakeholder expectations, or contractual requirements.
Stakeholder — A person, group, or organization that can influence a project, be influenced by it, or believe they are affected by it, such as sponsors, customers, team members, and end users.
These terms give project teams and organizations a shared vocabulary for discussing responsibilities, goals, constraints, and results without confusion.
2. Stages in a Project’s Life
Projects move from an initial idea to formal completion through recognizable phases. Knowing the phase helps teams understand the kind of work, decisions, and documentation needed next.
Initiation — The opening phase, when the project is described at a high level, feasibility is considered, and approval to continue is usually granted through a project charter.
Planning — The stage where detailed plans are built, including scope definition, scheduling, budget estimates, resource assignments, and identification of possible risks.
Execution — The phase in which the plan becomes active work, with team members completing tasks needed to create deliverables and meet project objectives.
Monitoring and controlling — The continuing work of measuring progress, comparing real performance with the approved plan, and making adjustments when the project moves off course.
Closing — The final stage, when deliverables are transferred, records are completed, lessons learned are documented, and the project is officially ended.
Lifecycle terms help people see where a project stands and what kinds of management activities are expected at each point.
3. Language Used in Agile
Agile manages work through repeated cycles, close collaboration, and frequent delivery of usable results rather than relying only on a large upfront plan.
Agile — A project management philosophy built on iterative development, where requirements and solutions develop through cooperation among self-organizing, cross-functional teams.
Sprint — A fixed work period, often lasting one to four weeks, during which an Agile team completes selected tasks and aims to deliver a potentially shippable product increment.
User story — A short, informal description of a feature from an end user’s point of view, commonly written as "As a [user], I want [feature] so that [benefit]."
Backlog — An ordered list of work items, features, and requirements still to be done, maintained by the product owner and used as the team’s central source for planned work.
Velocity — The amount of work an Agile team finishes in a sprint, usually counted in story points and used to help plan and forecast future capacity.
Agile terminology reflects an approach built around adaptation, feedback, and steady improvement, especially when requirements are complex or likely to change.
4. Terms from the Scrum Framework
Scrum is one of the best-known Agile frameworks. It gives teams defined roles, recurring events, and artifacts that organize how product work is planned and reviewed.
Scrum master — The team member who helps the group follow Scrum, facilitates ceremonies, removes impediments, and coaches the team in Agile ways of working.
Product owner — The person who works to maximize product value by managing the product backlog, setting priorities, and making sure the team understands the requirements.
Daily standup — A short daily team meeting, usually about 15 minutes, where members explain what they finished, what they will work on next, and what is blocking them.
Sprint review — A session at the end of a sprint where the team shows completed work to stakeholders, collects feedback, and talks about possible next steps.
Retrospective — A meeting after a sprint in which the team discusses what worked, what did not, and which concrete improvements they will try next.
Scrum terms are especially common in software development, but the framework’s language also appears in product, operations, marketing, and other project-based teams.
5. Traditional and Waterfall Language
Waterfall follows a sequence in which one phase is completed before the next begins. It often fits projects where requirements are stable and well understood early.
Waterfall — A linear project management method where work moves through defined stages such as requirements, design, implementation, testing, deployment, and maintenance.
Gantt chart — A visual scheduling tool that places tasks as horizontal bars on a timeline, showing start dates, finish dates, dependencies, and progress.
Work breakdown structure (WBS) — A hierarchical breakdown of the full project scope into smaller work packages, arranging deliverables in a structured format.
Critical path — The longest chain of dependent activities that sets the shortest possible project duration; delays on this path directly delay the completion date.
Baseline — The approved project plan for scope, schedule, and cost, used as the reference point for measuring actual performance and tracking variances.
Traditional project management vocabulary still matters, even on Agile teams, because many industries and project types continue to depend on sequential planning and formal controls.
6. Requirements and Project Boundaries
Scope management keeps the team focused on the work that was agreed to deliver. These terms describe how boundaries are set, protected, and changed when necessary.
Scope — The complete set of products, services, and results a project is expected to provide, defining what is included and what falls outside the work.
Scope creep — Uncontrolled growth in project scope without matching changes to time, budget, or resources, often caused by weak handling of change requests.
Requirements — Documented conditions, features, capabilities, or characteristics that a deliverable must meet to satisfy stakeholder needs and expectations.
Change request — A formal request to alter scope, schedule, cost, or another controlled part of the project, reviewed through the project’s change management process.
Acceptance criteria — The specific standards or conditions a deliverable must meet before a stakeholder or customer accepts it as complete.
Clear scope language helps prevent one of the most familiar project problems: boundaries expanding beyond the original agreement without proper approval or support.
7. Time, Schedules, and Tracking
Schedule management helps teams finish work within the planned timeframe. The following terms explain how timelines are designed, adjusted, and monitored.
Tools Used to Build the Plan
Dependencies show how tasks relate to one another and identify which activities must finish before others can start. Milestones mark important points on the timeline, such as a major deliverable being completed or a project phase changing. Buffer time adds schedule padding so small delays do not automatically affect the final deadline. Resource leveling changes the schedule to address overallocated team members or equipment.
Ways Teams Measure Progress
Status reports share progress, risks, and issues with stakeholders. Burndown charts show how much work remains in a sprint or project over time. Earned value management (EVM) combines scope, schedule, and cost information to evaluate performance and progress more objectively. Percent complete indicates how much of a task or project has been finished compared with the total planned work.
8. Vocabulary for Managing Risk
Risk management deals with uncertainties that may affect project results. A risk register records known risks along with their probability, impact, and planned responses. Risk assessment considers how likely each risk is and how serious its effect could be. Contingency plans spell out what the team will do if a known risk actually happens. Mitigation strategies lower the chance or impact of negative risks. Risk tolerance describes how much uncertainty an organization is prepared to accept. When teams use risk terms clearly, they can talk about threats openly and prepare before problems become emergencies.
9. Communication and Stakeholder Terms
Strong communication and stakeholder management support project success from start to finish. Communication plans define what information will be shared, who will receive it, how often it will be sent, and which channels will be used. A RACI matrix identifies who is Responsible, Accountable, Consulted, and Informed for each task. Escalation procedures explain how unresolved issues move to higher authority. Status meetings give stakeholders regular updates. Good stakeholder communication builds trust, keeps expectations realistic, and helps everyone stay aligned throughout the project lifecycle.
10. Building Fluency in PM Terms
Project management language keeps changing as teams adopt new methods, tools, and certifications. You can strengthen your command of these terms by using them in project documents, daily conversations, reports, and team planning sessions. Professional credentials such as PMP (Project Management Professional) or CSM (Certified ScrumMaster) can also deepen your understanding. Reading material from the Project Management Institute (PMI) and Agile Alliance is another useful habit. With the vocabulary in this guide, you have a solid base for discussing projects clearly, leading teams, managing deadlines, and delivering results that meet stakeholder expectations.
Look Up Any Word Instantly on Dictionary Wiki
Get definitions, pronunciation, etymology, synonyms & examples for 1,200,000+ words.
Search the Dictionary