Project Management Basics: Roles, Process and Key Terms
In plain English, project management is how a team turns a defined goal into a delivered result without losing track of time, scope or budget. Formally, PMI defines it as the use of specific knowledge, skills, tools, and techniques to deliver something of value to people. This guide explains what a project is, what a project manager does, a simple three-phase process, the benefits of having someone own coordination, and the vocabulary you need to read a plan or status report with confidence.
What counts as a project?
A project is a one-off effort with a clear start and finish, a stated goal, a defined scope and allocated resources. Work examples include building software to raise productivity, constructing a venue for community events, or redesigning a website to cut support calls. Personal efforts such as planning a trip or cooking a meal share the same structure, but business projects usually involve several specialists — for example a designer, developer and copywriter on a website — whose work must be sequenced and integrated.
What a project manager does
Project managers sit close to the work and protect the team, client and project from confusion, missed dates, expanding scope and other setbacks. They appear across construction, agencies, marketing, manufacturing, HR, software, engineering and events. Their core duties include choosing a management approach, defining scope, setting expectations, designing the process, building the plan, managing tasks, allocating resources, estimating time and cost, handling risks and issues, reporting status, leading the team, shaping strategy, and running communication and meetings. Much of this is influence rather than direct command, so credibility with the team and support from senior leaders are essential.
A three-phase process you can adapt
No single process fits every organisation, because goals, staff, skills and technology change. A practical framework has three stages. First, research and plan: test whether the idea is valid through market, user or competitor work, agree goals and requirements, and decide how the team will work together. Second, execute: collaborate, create, review and revise with stakeholders, using Waterfall, Agile or a hybrid style; this is when the project manager is busiest because change and delay are most likely. Third, test, measure and iterate: check performance against goals after launch, learn what works, and adjust. Document the chosen process, review it with the team, and change it when it no longer fits.
Why dedicated coordination helps
Dedicated coordination makes teams more efficient because someone watches timing and workflow while specialists focus on their craft. Clear communication and reliable delivery leave teams and clients happier. Plans, responsibility charts and regular reporting improve organisation, transparency and accountability, and make risks, issues and changes visible early enough to plan around them. Freeing specialists from logistics also supports growth, higher quality and greater output. A small team may not need a full-time project manager, but it still needs someone to own logistics and communication — that person could be a producer, account manager, designer or developer.
Scope, change and people
Scope states what will and will not be delivered, in a formal document, brief or even an email. Constraints such as scope, budget and timeline limit what is possible. Assumptions should be surfaced and turned into agreed facts because they shape goals and deliverables. When requirements change, effort, cost and deadlines may no longer hold, so a change request formalises the change and its impact. A sponsor is the ultimate decision-maker who funds the work, resolves scope disputes, approves deliverables and champions the project. Stakeholders are anyone with a stake in the outcome, inside or outside the project, and they need timely updates and a voice in key decisions. A client is the buyer who commissions the work and gives approvals, while end users or customers are the people who will actually use the product — the two groups can have different needs. A goal or objective is a documented statement of intended outcome; when the project reaches a crossroads or scope creep threatens, the goal is the criterion for deciding what success looks like. Requirements define how the product should act, appear and function within those goals, often captured in a detailed scope of work.
Plans, schedules and control terms
A project plan shows phases, deliverables and tasks with owners, start and finish dates and notes; it is both a roadmap and a communication tool. A Gantt chart displays work as horizontal bars over time so progress can be compared with the plan. A milestone is a zero-duration marker that significant work is complete. A dependency means a task cannot begin until its predecessor ends. The critical path is the sequence determining the shortest possible duration, separating critical from non-critical tasks to prevent bottlenecks. A risk is a possible future problem, judged by likelihood and impact, while an issue is already impeding progress; both belong in a risk register reviewed in status reports. Resources are the people doing the work, and a resourcing plan checks that assignments are balanced rather than over- or under-used. A program groups connected projects under shared goals and central coordination, and a program manager oversees that wider strategy. A project phase is a grouped set of tasks or deliverables that keeps work organised — on a website redesign, for example, phases might be definition, design, development and deployment. The project team is the group responsible for conducting tasks and completing deliverables, recruited for the expertise the work requires. Methodology is the formal approach chosen for managing the work; categories include traditional, Agile, change management and process-based methodologies, and the right choice depends on the project and team.
Decide what fits your team
Use these questions to decide what your team needs: Does formal project management fit your organisation? Which tasks would a project manager take on, and what benefit would follow? Is your current process right, and if not, what alternatives should you explore? What else do you still need to learn? Talking to an experienced project manager can help you choose a path that matches your goals, people and constraints.
| Phase | Main work | Typical output |
|---|---|---|
| Research and planning | Validate the idea, agree goals, requirements and ways of working | Defined scope, plan and execution approach |
| Execution | Collaborate, create, review and revise with stakeholders | Agreed deliverables and final product |
| Testing and iteration | Measure results against goals and adjust the product | Evidence of what works and follow-up improvements |
Simplified framework; names and deliverables vary by organisation and methodology.
| Term | Plain-English meaning |
|---|---|
| Agile | Iterative, collaborative delivery by self-organising teams |
| Waterfall | Sequential stages, each handed to the next after completion |
| Deliverable | Tangible output produced during or at the end of a project |
| Milestone | Zero-duration marker of a significant completed stage |
| Dependency | A task that cannot start until its predecessor finishes |
| Critical path | Sequence setting the minimum time needed to complete the work |
| Risk / issue | Possible future problem / current problem impeding progress |
| Scope | What the project will and will not deliver |
| Client / end user | Buyer who commissions and approves the work / person who will use the product |
| Goal / objective | Documented intended outcome used to judge decisions and success |
| Methodology | Formal management approach: traditional, Agile, change management or process-based |
| Project phase | Grouped tasks or deliverables, e.g. definition, design, development, deployment |
| Project team | People responsible for tasks and deliverables, recruited for needed expertise |
| Requirements | How the product should act, appear and function, often in a scope of work |
Definitions summarised for general use; formal usage varies by methodology.
Frequently asked questions
What is project management in simple terms?
It is the coordinated work of planning, tracking and communicating so a defined effort reaches its goal within time, scope and budget limits. Documentation, scheduling and regular updates are the practical tools for that coordination.
What does a project manager actually do day to day?
The person typically defines scope, builds the plan, assigns resources, estimates time and cost, tracks risks and issues, reports status, leads the team and keeps communication moving. They often influence outcomes without direct authority over the specialists doing the work, so trust and senior backing matter.
What are the three broad phases of a project?
A useful starting framework is research and planning, execution, then testing and iteration. Research checks whether the effort is worthwhile and sets goals and requirements. Execution is where collaboration, creation, review and feedback happen. After launch, results are measured and the product is adjusted — in Agile work that may mean iterating on an early release, while in Waterfall work a further phase may be needed.
How do Agile and Waterfall differ?
Agile emphasises self-organising teams delivering value through iteration and collaboration, valuing people and interaction, working software, customer collaboration and responding to change. Waterfall completes one stage and hands it to the next, so thorough planning and requirements work up front is essential because later changes can alter scope.
What is the difference between a milestone, a deliverable and a dependency?
A milestone marks a significant stage with no duration or effort of its own. A deliverable is a tangible output, produced during the work or at the end. A dependency means one task cannot start until its predecessor finishes. The critical path is the sequence that sets the minimum time needed and helps surface bottlenecks.