Project management basics come down to five moves: agree on what the project is for, break the work into estimated pieces, do the work, compare what is happening against those estimates, and close the project in a way that makes the next one easier. The guides we read on this topic mostly list these moves as definitions. This one follows a single small project, a 12 page website rebuild estimated at 250 hours, through every phase, so you can see the estimates, the budget, the overrun in week 4, the scope request from the sponsor, and the final numbers.
If someone has just handed you a project and you never applied to manage one, you are in good company. PMI even has a name for it: the accidental project manager. Project management for beginners does not require a certificate or special software, only a few habits that you can apply to your first project this week.
- What are project management basics?
- The example: a 12 page website rebuild
- The five phases, worked through
- How much process does your project need?
- Predictive, adaptive, or hybrid?
- Why guides disagree on the framework
- Five mistakes that derail a first project
- Tracking the basics in actiTIME
- Where to learn next
- FAQ
What are project management basics?
Project management basics are the small set of concepts and habits that let you deliver a defined result within agreed limits of time and money. PMI defines project management as “the application of knowledge, skills, tools, and techniques to project activities to meet project requirements.” The UK’s Association for Project Management adds the distinction that beginners need most: a project has a final deliverable and a finite timespan, whereas ordinary management carries on indefinitely.
Is your work actually a project?
The word gets applied to almost everything, so it helps to test it. Treat the work as a project if you can answer yes to these three questions:
- Does it have a definite end?
- Will it produce something that did not exist before?
- Can you say in advance what would count as finished?
Running payroll each month fails this test because it never ends. Moving payroll to a new provider by the start of the next quarter passes, even though the same people may do both.
The vocabulary you need
A handful of terms cover most of project management 101. The third column uses the example project described in the next section.
| Term | What it means | In the example |
|---|---|---|
| Scope | What the project includes and excludes | 12 pages on a new content system, no blog |
| Deliverable | Anything the project hands over | Approved designs, the live site |
| Milestone | A checkpoint that marks progress and takes no time itself | Designs approved at the end of week 3 |
| Sponsor | The person who funds the project and approves changes | The marketing director |
| Stakeholder | Anyone affected by the project or able to influence it | Sales, support, the legal reviewer |
| Baseline | The approved estimates and dates you measure against | 250 hours of work, 8 weeks |
| Contingency | A reserve held back for things you cannot foresee | 25 hours |
| Risk | Something that might happen and would affect the project | Legal review of the copy could run long |
The example: a 12 page website rebuild
Imagine you work in marketing at a midsize company, and the marketing director asks you to rebuild the 12 page company website on a new content system in time for a trade show 8 weeks away. You will coordinate the work alongside your normal job, helped by a designer, a developer, and a writer who all have other duties too. Nobody on this team has the words project manager in their title, which is typical.
The five phases, worked through
The basics of project management are usually taught as five phases: initiating, planning, executing, monitoring and controlling, and closing. They are not a strict sequence, because monitoring runs alongside the work from the first day. Our guide to the project life cycle covers each phase as theory, so here we simply use them.
Phase 1: Initiating
This phase answers two questions: why are we doing this, and who can say yes? Beginners often skip it because the request already feels clear, yet this is an early and inexpensive moment to discover that you and the sponsor picture different results.
Put the answers in a project charter. For a project this size, a single page is enough:
- Purpose: give sales an accurate site to point to at the trade show.
- Success test: all 12 pages live and approved by the end of week 8.
- In scope: 12 pages, new designs, new copy, and migration to the content system.
- Out of scope: a blog, translations, and new photography.
- Limits: the trade show date and a budget still to be confirmed.
- People: the marketing director as sponsor, you as project lead.
The success test matters more than it looks. In PMI’s 2025 project success research, based on 5,842 survey responses worldwide, projects with a clear vision of success scored 41 on its net success measure (the share of successful projects minus the share of failures), against minus 18 for those without one. That is a correlation rather than proof of cause, but the gap is wide, and writing one sentence costs nothing.
Want a starting point? Download our project charter template below.
Phase 2: Planning
Planning turns the charter into something you can check against later. Start with a work breakdown: split the project into pieces small enough that one person can estimate each piece, then ask the person doing the work for that estimate, because the number should come from them rather than from you.
| Work package | Owner | Estimate | Needs first |
|---|---|---|---|
| Discovery and sitemap | You | 24 h | Approved charter |
| Design | Designer | 60 h | Sitemap |
| Copy and legal review | Writer | 48 h | Sitemap |
| Build and migration | Developer | 90 h | Approved designs |
| Testing and launch | Everyone | 28 h | Finished build and copy |
The last column is your schedule logic. Build cannot begin until designs are approved, so a late design approval moves everything after it, and that makes it the date you protect. From these estimates you can work out the budget:
Small inputs move this figure quickly. A rate of $70 instead of $60 lifts the budget to $19,250, and a 20% contingency lifts it to $18,000. The contingency matters because first estimates tend to run low: in a 1994 study by Buehler, Griffin, and Ross, students expected to finish their theses in 33.9 days on average and took 55.5, and only about 30% finished in the time they predicted. The best correction is data from similar past work, which is why your first project’s actual hours are worth keeping.
Finish by listing the few risks that could really hurt, each with an owner and a response. Legal review might run long, so the writer sends the first pages for review by week 3. The developer might get pulled onto other work, so the sponsor agrees to protect those hours now. Someone might ask for extra pages, so you agree that every addition goes through the sponsor. For a small project, three lines like these are usually enough.
Phase 3: Executing
Execution is where most of the hours go, and your job shifts from deciding to keeping the path clear. For a team of four, a light rhythm works well:
- Give every task one named owner, because shared tasks tend to belong to nobody.
- Hold a 15 minute check in each week: what finished, what comes next, what is stuck.
- Have everyone log hours against the work packages, since the next phase depends on it.
- Send the sponsor a short status update on the same day each week.
If several groups need different levels of detail, a simple communication plan can save you from repeating yourself. Team roles and how to size a team are covered in our project team guide.
Phase 4: Monitoring and controlling
Monitoring means comparing what has happened with what you expected while there is still time to respond. At the end of week 4, discovery and design are finished and half the copy is done. Everything looks fine on the task board, but the logged hours tell a different story:
Nothing has failed yet, which is exactly why the check is useful. With half the schedule left, a $1,800 problem is a conversation, whereas in week 8 it would be a surprise. Had the team been running only 10% over, the forecast would be 275 hours, exactly the approved limit, and you would simply carry on. Our guide to tracking project progress goes further into methods and metrics.
The triple constraint, priced in dollars
That same week, the sponsor asks for a blog section, which the team estimates at 40 hours. Here the triple constraint becomes concrete: scope, time, and cost are linked, so changing one forces a change in another. APM describes the building blocks as time, cost, and quality instead, and the idea works either way. At about 33 hours a week, the team’s current pace, the request has four possible prices:
| Option | Scope | Time | Cost |
|---|---|---|---|
| Add it and bring in a freelancer at $90 an hour | Blog added | No change | +$3,600 |
| Add it and move the launch | Blog added | +1.2 weeks | +$2,400 |
| Swap it for other work | Blog in, about 4 pages out | No change | No change |
| Defer it to a second phase | No change for now | No change | $2,400 later |
Your job is to bring the options, and the sponsor’s job is to choose. The trade show date cannot move, so the sponsor defers the blog, drops one low priority page to save about 9 hours, and approves the remaining overrun in advance. PMI’s report points the same way: it links a willingness to flex time, cost, and scope in pursuit of greater value with better results. Requests like this one are how scope creep begins, and pricing each one in hours helps keep it in check.
Phase 5: Closing
The site launches on time in week 8, after the team puts in a few extra hours. Before anyone moves on, get formal approval from the sponsor, hand the site over to whoever will maintain it, and hold a short review with the numbers on the table:
| Work package | Estimated | Actual | Variance |
|---|---|---|---|
| Discovery and sitemap | 24 h | 30 h | +25% |
| Design | 60 h | 74 h | +23% |
| Copy and legal review | 48 h | 58 h | +21% |
| Build and migration | 90 h | 104 h | +16% |
| Testing and launch | 28 h | 30 h | +7% |
| Total | 250 h | 296 h | +18% |
The final cost is 296 x $60 = $17,760, which is $1,260 or 7.6% over the $16,500 budget. The project was still a success by its own test: all pages live, on the date that mattered, with a sponsor who knew about the overrun four weeks ahead. The table also tells you what to change. The early, judgment heavy work ran furthest over, so next time your first estimate for discovery and design should start about 25% higher, and that adjustment comes from your own data rather than from a rule of thumb.
How much process does your project need?
APM notes that relocating a small office and organizing the Olympics share many basic principles while presenting very different challenges. The principles scale, but the paperwork should not stay the same. The size bands below are our own rule of thumb rather than a published standard.
| Project size | Keep | Skip |
|---|---|---|
| Under 40 hours, one or two people | A one sentence goal, a task list with owners, a deadline | Charter, status reports, risk log |
| 40 to 500 hours, a small team | One page charter, estimates by work package, budget, weekly update, closing review | Formal change board, detailed communication plan |
| Over 500 hours, or several departments | Full charter, risk register, change log, communication plan, dependency schedule | Nothing here, and consider an experienced project manager |
Predictive, adaptive, or hybrid?
Our example was predictive, because the 12 pages were known at the start. PMI describes three main approaches, and the choice depends on how settled your requirements are:
- Predictive, often called waterfall, suits stable requirements, with each phase finished before the next begins.
- Adaptive, which includes agile, suits work likely to change, delivered in short cycles with regular feedback.
- Hybrid combines the two when some parts are fixed and others are still uncertain.
Under all three you still define success, estimate, track actual work, and review the results. When you are ready to compare named frameworks, see our guide to project management methodologies.
Why guides disagree on the framework
If you read several introductions, you will notice that many still list 10 knowledge areas while others talk about domains. Both come from PMI’s PMBOK Guide, a widely used reference, and the difference is simply the edition. The current one is the Eighth Edition, published in 2025.
| Edition | Core structure | Processes |
|---|---|---|
| Sixth (2017) | 5 process groups, 10 knowledge areas | 49 |
| Seventh (2021) | 12 principles, 8 performance domains | Not listed |
| Eighth (2025) | 6 principles, 7 performance domains, 5 focus areas | 40 |
PMI names the seven current domains as governance, scope, schedule, finance, stakeholders, resources, and risk. The five focus areas bring back the familiar flow from initiating to closing, so the phases in this article remain valid. None of this changes how you run a first project. It only matters if you are preparing for an exam, in which case check which edition your exam follows.
Five mistakes that derail a first project
Outright failure is less common than a compromised result. In PMI’s 2025 research, 50% of projects were rated successful, 37% a mix of success and failure, and 13% failures. These five habits, drawn from the example above, are common ways for a project to end up in that middle group. For the wider list, see our article on project management challenges.
-
Starting before anyone owns the decision.
If you cannot name the person who approves changes, every request becomes a negotiation with whoever asked last.
-
Treating an estimate as a promise.
An estimate is a forecast and a deadline is a commitment. When the two are merged, people pad their numbers or hide their overruns.
-
Absorbing small changes for free.
Each extra request looks trivial, and the cost only shows once ten of them have been added. Estimate every one, even at 2 hours.
-
Asking for percent complete.
Work can sit at 90% for weeks. Ask how many hours remain, then compare that figure with the estimate.
-
Skipping the closing review.
Without it, the team’s actual hours disappear and the next estimate starts from the same optimistic guess.
Tracking the basics in actiTIME
A spreadsheet will carry your first project, although the week 4 check depends on people logging real hours against each piece of work, and those hours are easy to lose in a spreadsheet. actiTIME is project time tracking software, and its features line up with the steps above:
- Work breakdown: organize work as customers, projects, and tasks, and give each task an estimate, a deadline, and a status. List and kanban views show progress.
- Logging hours: your team records time through a weekly timesheet, a calendar view, or the mobile app.
- The week 4 check: the Estimated vs. Actual Time Report shows the variance per task without manual arithmetic.
- Budgets: set time and cost budgets on a project or task, with a progress bar that turns red when a budget is exceeded.
- Client work: the Profit/Loss Report compares billable amounts with staff costs.
Task estimates and budgets are included in the paid versions and in the 30 day free trial, while the permanent free version covers basic tracking for teams of up to 3 users.
Now we can better predict future project requirements
Our company needed a simple way of tracking time used on multiple projects – and actiTIME fit the need. Its interface is simple and easy to maintain. We use the application for time management, task estimation and also to communicate deadline information to our team members. Now having actiTIME we can better predict future project requirements!
Where to learn next
Once you have run one project, these are sensible next steps, roughly in order of effort:
- A free course: PMI’s KICKOFF teaches the basics of project management in under an hour.
- Your weakest skill: our article on project management skills helps you see what to practice first.
- A longer course: our list of project management courses compares structured options.
- An entry certificate: PMI’s CAPM requires no project experience, only a secondary degree and 23 hours of project management education. The exam costs $225 for PMI members and $300 for others.
If this could become a career, the US Bureau of Labor Statistics reports a median wage of $102,320 for project management specialists in the United States (May 2025) and projects 7% job growth from 2025 to 2035. The day to day work is described in our guide to project manager responsibilities.
FAQ
What are the 5 P’s of project management?
There is no single agreed list. Training sites use different versions, and a common one is purpose, people, process, plan, and performance. It does not appear on PMI’s or APM’s introductory pages, so treat it as a memory aid rather than a formal framework.
How long does it take to learn project management basics?
You can learn the concepts in an afternoon, since PMI’s free course takes under an hour and this article covers the same ground with numbers. Real competence comes from running a project and comparing your estimates with your actual hours, so expect one or two small projects before the habits feel natural. That timing is our judgment rather than a measured figure.
What is 90% of a project manager’s job?
The usual answer is communication, although we could not trace the number to an original study. Our responsibilities guide looks at where the figure comes from and what a project manager’s week actually contains.
Start with one small project
Project management basics mostly rest on one repeating habit: write down what you expect, measure what happens, and act on the gap while you still can. The website rebuild finished 18% over its hour estimate and still succeeded, because the numbers surfaced in week 4 instead of week 8.
To see your own estimated and actual hours side by side, start a free trial of actiTIME. It runs for 30 days with every feature included, and afterward you can keep the permanent free version for teams of up to 3 users.
