Project management is the discipline of organising and guiding a team to achieve a specific goal within a defined timeframe and budget. It matters for anyone studying for the CompTIA Project+ (PK0-005) exam because the entire exam is built around understanding how projects are started, planned, executed, monitored, and closed — and your ability to recognise the fundamental rules of project management is tested from the very first objective.
Jump to a section
A simple way to picture Project Management Fundamentals
A dinner party is a project. A dinner party has a clear start and a clear end: the guests arrive and the guests leave. It creates a unique product, service, or result — in this case, a memorable evening and a full stomach. It is not an ongoing, routine operation like washing the dishes every night.
The project manager is the host of the dinner party. The host does not cook every dish, set every place, or pour every drink. The host’s job is to make sure the chef, the cleaner, the bartender, and the guest-list coordinator all know what they are doing and when. The host manages the key constraints: the budget (how much to spend on food and wine), the schedule (when the starter must be served so the main course is not burnt), and the scope (are we having a three-course meal or a buffet?). If the budget is tight, the host might choose cheaper wine. If the schedule slips because the oven breaks, the host decides to skip the dessert. Every change affects the other constraints.
Successful hosts communicate clearly with their team and manage expectations. They know the difference between a project (the party) and a business-as-usual operation (weekly family dinners). They succeed when the guests are happy, the cost is under control, and the evening ends on time — without anyone in the kitchen crying.
A project is a temporary endeavour undertaken to create a unique product, service, or result. Temporary means it has a definite beginning and a definite end. Unique means the outcome is different in some way from what already exists. For example, building a mobile app for a new food-delivery service is a project: it starts when the idea is approved and ends when the app is released to the public. In contrast, the daily maintenance of that app after release is an operation — it is ongoing and repetitive.
Projects have a set of characteristics that define them. Every project is unique: even if you build a second mobile app for food delivery, it will have different features, a different design, and a different set of users. Every project is temporary: it has a start date and an end date. Every project requires resources: people, time, money, tools, and materials. And every project involves uncertainty: you never know exactly how long a task will take or whether a supplier will deliver on time.
Every project operates within constraints. The classic model is the triple constraint: scope, time, and cost. Scope is the work that needs to be done to deliver the project’s outcome. Time is the schedule — the deadline by which the project must be completed. Cost is the budget — the money available to pay for resources. These three constraints are linked: if you change one, at least one of the other two must change. For example, if the project sponsor asks for more features (increased scope), you either need more time (a later deadline) or more money (to hire extra staff). If you are told to finish earlier (reduced time), you might need to reduce scope (remove features) or increase cost (pay overtime).
The modern model adds a fourth constraint: quality. Quality is the degree to which the project’s deliverables meet the requirements. You can meet scope, time, and cost but still fail the project if the delivered product does not work properly. Quality is not directly traded like the other three — it is an outcome that is affected by decisions about scope, time, and cost.
A project manager is the person assigned by the performing organisation to lead the team and achieve the project objectives. The project manager’s role is not to do all the work themselves. Instead, they:
Plan the project: define scope, create a schedule, estimate costs, and identify risks.
Lead the team: assign tasks, motivate people, resolve conflicts, and ensure communication.
Monitor and control: track progress against the plan, manage changes, and report status to stakeholders.
Close the project: ensure all work is complete, hand over the deliverable, release team members, and document lessons learned.
Stakeholders are individuals or organisations who are actively involved in the project or whose interests may be positively or negatively affected by the project. Stakeholders include the project sponsor (who provides funding), the customer (who will use the result), the project team, suppliers, and even regulatory bodies. The project manager must identify stakeholders early, understand their expectations, and manage their influence throughout the project.
Operational work is the opposite of project work. Operations are ongoing, repetitive activities that keep an organisation running. For example, processing payroll every month is an operation. Projects and operations intersect at key points: a project might create a new payroll system (a project), and then that system is used for payroll processing (an operation). The handover from project to operations is called transition.
Why does this matter for the exam? CompTIA Project+ objective 1.1 expects you to identify whether a scenario describes a project or an operation, recognise which constraint is being affected when something changes, and understand what a project manager actually does versus what the team does. The exam will give you a short description and ask you to pick the correct term or role.
Identify the Project
Determine if the work is temporary and unique. If yes, it is a project. If ongoing and repetitive, it is an operation. This step sets the foundation for using the correct management approach.
Define the Triple Constraint Baseline
Document the agreed scope, time, and cost at the start. This baseline becomes the reference point for all future decisions. Any change to one constraint will require revisiting this baseline.
Assign the Project Manager
Designate a person responsible for achieving the project objectives. The project manager acts as the single point of accountability, coordinating the team and communicating with stakeholders.
Identify Stakeholders
List everyone who has an interest in the project, including sponsors, customers, team members, and suppliers. Early identification prevents surprises and ensures their expectations are managed from the start.
Manage Constraints Through Change Control
When a change is requested, evaluate its impact on scope, time, cost, and quality. Obtain approval from the sponsor before implementing any change. This keeps the project aligned with business goals and prevents scope creep.
Close the Project
Formally end the project by handing over the deliverable to operations, releasing team members, documenting lessons learned, and archiving project documents. Closure ensures a clean transition and captures knowledge for future projects.
Consider Sarah, a project manager for a mid-sized retail company. The company wants to launch a new online returns portal so customers can print return labels from home instead of going to the store. Sarah is assigned to lead this project.
First, Sarah meets with the project sponsor (the VP of Customer Experience) to define the scope. What exactly will the portal do? Will it integrate with the existing shipping carrier? Will customers be able to track the return? The sponsor wants a basic portal that prints a label and nothing else. Sarah writes this down as the project scope statement.
Next, Sarah creates a schedule. She lists all the tasks: design the portal, build the portal, test it with a small group of users, fix bugs, and launch. She estimates each task: design takes 2 weeks, build takes 6 weeks, testing takes 2 weeks, fixing takes 1 week, launch takes 1 week. Total: 12 weeks. The sponsor agrees to a 12-week deadline.
Sarah also prepares a budget. She needs one developer (who costs £50 per hour) and one tester (£40 per hour). She calculates the labour cost: 12 weeks x 40 hours per week x £90 per hour = £43,200. She adds £2,000 for software licenses and £1,000 for a temporary server. Total budget: £46,200. The sponsor approves this budget.
During the second week, the developer discovers that the company’s existing shipping carrier API (Application Programming Interface — a way for two systems to talk to each other) cannot handle the volume of labels the portal will generate. The developer says they need to upgrade the API, which will cost an extra £5,000 and add 3 weeks to the schedule.
Sarah now has a change request. She analyses the impact: if they upgrade the API, scope stays the same (the portal still works), but cost increases to £51,200 and time increases to 15 weeks. She presents this to the sponsor. The sponsor says: “We cannot spend more money. Can we cut scope instead?” Sarah suggests removing the tracking feature — the portal will still print labels, but customers will not see where their return is. This reduces the development time back to 12 weeks and avoids the extra cost. The sponsor agrees. Sarah updates the project plan, communicates the change to the team, and keeps working.
This scenario illustrates the project manager’s role in managing constraints, handling changes, and communicating with stakeholders. In a real IT environment, Sarah would use software like Microsoft Project or Jira to track tasks and timelines. She would hold weekly status meetings with the team and send a summary email to the sponsor. She would also create a risk register — a document that lists potential problems (like the API issue) before they happen, along with plans to avoid or minimise them.
At the end of the project, Sarah conducts a project closure meeting. She ensures the portal is handed over to the operations team (who will maintain it), archives all documents, and asks the team for lessons learned: what went well, what went wrong, and what to do differently next time. She then releases the team members back to their regular jobs or to new projects.
CompTIA PK0-005 objective 1.1 tests your ability to identify the fundamentals of project management. This is a multiple-choice topic, usually appearing as 3 to 5 questions in the exam. The questions are designed to see whether you can distinguish a project from an operation, recognise the triple constraint, and understand the project manager’s role.
Question types you will see:
Scenario-based: The exam gives you a short paragraph describing a situation, then asks “Is this a project or an operation?” or “Which constraint is affected?”.
Definition matching: You are given a term (e.g., scope) and must pick the correct definition from four options.
Role-based: You are asked “Which of the following is a primary responsibility of a project manager?” with options like “Writing code”, “Managing the budget”, or “Setting corporate strategy”.
Common traps the exam sets:
Trap 1: They describe something that seems temporary (like a one-time event that is actually part of routine operations). Example: “A company performs a monthly security audit.” That is a repetitive operation, not a project, even though each audit is a distinct event. The keyword is monthly — it is ongoing.
Trap 2: They change two constraints at once and ask which one is most affected. Example: “The sponsor asks the project to be completed three weeks earlier while keeping the same budget. What must be adjusted?” Correct answer: scope (you must remove features to finish earlier without spending more). Beginners often pick cost or time, but those are fixed in the question.
Trap 3: They confuse the project manager’s role with the team’s role. Example: “Who is responsible for designing the software?” The correct answer is a team member (developer or engineer), not the project manager. The project manager facilitates, not builds.
Key definitions to memorise:
Project: temporary, unique, progressive elaboration.
Operation: ongoing, repetitive, produces the same result each time.
Triple constraint: scope, time, cost.
Stakeholder: anyone with an interest in the project.
Project sponsor: the person who provides financial resources and championing.
Concepts they love to test:
The difference between a project and an operation.
The relationship between scope, time, and cost (triple constraint).
Examples of project constraints beyond the triple (quality, risk, resources).
The responsibilities of a project manager.
The definition of a stakeholder.
Study tip: create a mental checklist. When you read a scenario, ask yourself: is it temporary? Is it unique? Does it have a start and end? If yes to all three, it is a project. Then identify the constraint in the question: are they talking about deadlines (time), money (cost), or features (scope)? That is usually the answer. For the project manager role, remember: they plan, organise, lead, control, and close. They do not do the technical work.
A project is a temporary endeavour with a unique outcome, while an operation is ongoing and repetitive.
The triple constraint — scope, time, and cost — are interdependent: changing one forces a change in at least one other.
The project manager is responsible for planning, leading, monitoring, and closing the project, not for performing the technical work.
Stakeholders include anyone affected by the project, and the project manager must manage their expectations.
Quality is a separate dimension of project success that is impacted by decisions about scope, time, and cost.
Projects have a defined start and end; operations continue indefinitely after the project delivers its result.
Change is expected in projects and should be managed through a formal change control process, not ignored.
The role of the project sponsor is to provide funding and organisational support, not to manage the project day-to-day.
These come up on the exam all the time. Here's how to tell them apart.
Project
Temporary with a defined start and end
Creates a unique product, service, or result
Ends when objectives are met or project is terminated
Operation
Ongoing and repetitive
Produces the same result each time
Continues indefinitely as part of business-as-usual
Project Manager
Manages day-to-day activities
Responsible for achieving project objectives
Leads the team and communicates with stakeholders
Project Sponsor
Provides financial resources
Approves major changes and scope
Champions the project at executive level
Scope Constraint
Defines what work must be done
Measured in features, deliverables, and requirements
Can be reduced to save time or cost
Quality Constraint
Defines how well the deliverables work
Measured in defects, performance, and user satisfaction
Is affected by changes in scope, time, and cost but not directly traded
Mistake
A project is the same as an operation because both involve work being done by a team.
Correct
A project is temporary and produces a unique outcome. An operation is ongoing and produces the same outcome repeatedly. For example, building a new website is a project; updating the existing website with new blog posts every week is an operation.
Because people focus on the activity (work) rather than the lifecycle (temporary vs. ongoing). The exam tests this exact distinction.
Mistake
The project manager must be an expert in the technology or domain of the project.
Correct
The project manager’s job is to manage the project — plan, organise, communicate, and control. They do not need to be a subject-matter expert. They rely on the team for technical decisions. The project sponsor and team bring the expertise.
Many beginners think leadership requires technical depth. In reality, project management is a separate skill set focused on process and people, not on the specific deliverable.
Mistake
Scope, time, and cost can all be changed independently without affecting each other.
Correct
The triple constraint is interdependent. Changing scope (adding features) requires more time or more cost. Reducing time (shortening the deadline) requires reducing scope or increasing cost. You cannot change one without affecting at least one other.
Beginners treat constraints as independent variables. The exam uses scenarios where one constraint is fixed and asks which of the others must change, testing this interdependency.
Mistake
Once a project is planned, the plan cannot change.
Correct
Projects are dynamic. Changes happen due to new requirements, risks, or stakeholder requests. The project manager manages changes through a formal change control process. The plan is a baseline, but it can be updated with proper approval.
People think planning is a one-time activity. In reality, iterative planning and change management are core to project management. The exam expects you to know that change is normal and managed, not avoided.
Mistake
A project is successful if it is completed on time and within budget.
Correct
Success also depends on delivering the required quality and meeting stakeholder expectations. A project finished on time and under budget but with missing features or a broken product is a failure. The full definition includes scope, quality, and stakeholder satisfaction.
Beginners focus only on the triple constraint. The exam includes quality and stakeholder satisfaction as implicit success criteria, often tricking those who only memorise the triple constraint model.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
A project is temporary and creates a unique result, like building a new app. An operation is ongoing and produces the same result repeatedly, like processing payroll each month.
No. The project manager does not write code. They plan, communicate, and manage resources. The technical team members do the coding. You do need to understand enough to ask good questions and track progress.
The triple constraint is scope, time, and cost. They are linked: change one and at least one other must change. The exam tests your ability to identify which constraint is affected in a given scenario.
The project sponsor provides funding, approves major changes, and champions the project at the executive level. They do not manage the day-to-day work — that is the project manager’s role.
Yes. Changes are common due to new requirements, risks, or stakeholder requests. Changes go through a formal change control process where the impact is assessed and approved by the sponsor before updating the plan.
Not necessarily. Success is measured by meeting all constraints: scope, time, cost, and quality. If it is late and missing features, it is not fully successful, even if under budget. The exam considers all constraints.
You've finished Project Management Fundamentals. Continue through the PK0-005 study guide to build a complete picture of the exam.
Done with this chapter?