What is project management: the complete guide, with real-world examples.

Project management is the practice of organizing work that has a beginning, middle, and end so that it's delivered on the agreed date, within budget, and at the quality the client expected. Renovating a store, launching a website, closing a client's audit, rolling out a system: all of these are projects, and they all go wrong for the same reasons when nobody manages them.

The most common mistake is thinking project management is for big companies, with a PMO room and certifications. It isn't. A six-person agency in Florianópolis that delivers a client's website in eight weeks is already managing a project, well or badly. The difference is doing it on purpose, with a simple method that's visible to everyone.

What project management is (and what it isn't)

A project has three characteristics that set it apart from routine work:

• It's temporary. It has a start date and an end date. When it ends, the team moves on to something else.
• It's unique. It produces a specific deliverable that isn't the same as the last one: this building, this campaign, this system.
• It has a measurable goal. At the end, you can say whether it was delivered or not.

A process, on the other hand, is repetitive and ongoing. Closing payroll every month, handling support tickets, publishing three posts a week: that's operations. An accounting firm in Belo Horizonte has processes (each client's monthly close) and projects (migrating the entire client base to a new accounting system by December). Managing one by the rules of the other is a recipe for frustration.

Project management is also not a synonym for bureaucracy, for a specific tool, or for a job title. On a small team, whoever manages the project is the agency owner, the firm's partner, or the tech lead, alongside the rest of their work. What matters is that someone answers three questions every week: what's moving, what's stuck, and whether the delivery date still holds.

The five phases of the project life cycle

Almost every methodology describes a project in five phases. The names vary, but the logic is the same, and it's worth seeing the cycle before choosing any tool.

1. Initiation: deciding whether it's worth it

This is where the project is born. You answer why it exists, who the client or sponsor is, what the expected result is, and who will lead it. The classic document of this phase is the project charter (or brief, in the creative industry): one or two pages with the goal, initial scope, estimated timeline, and who decides.

Example: a construction company in Curitiba gets a request to renovate a condominium's facade. Before opening the project, it confirms the available budget, the deadline the owners' meeting approved, and who signs off on approvals. Without that, the work starts and the argument about what was agreed starts right along with it.

2. Planning: breaking down the work and setting dates

This is the most underrated phase. Here you define the scope in detail, break it into tasks, estimate effort, build the schedule, assign owners, and identify risks. The tools of this phase (WBS, schedule, RACI matrix) appear later in this guide.

Planning isn't predicting the future precisely. It's making explicit what you're assuming, so that when reality diverges, the divergence shows up early and not on the delivery date.

3. Execution: doing the work

The team works, the manager removes obstacles, and communication flows. This is the longest phase and the one that consumes the most budget. The risk here is execution drifting from the plan without anyone noticing: scope creeps up bit by bit, tasks quietly pass their deadlines, and the client asks for "just one more little thing."

4. Monitoring and control: comparing actual to planned

It happens in parallel with execution, not after it. Each week you compare what was planned with what happened, adjust the plan, and communicate the result. This is where the weekly status report, the risk review, and scope change control come in.

5. Closing: delivering, formalizing, and learning

Many teams skip this phase, and lose the most valuable thing it offers. Closing means getting the client's acceptance, wrapping up open items and costs, archiving the documentation, and holding a short retrospective: what worked, what cost more than it should have, what to do differently next time. A delivery acceptance form prevents the classic dispute of "I thought it was already finished."

Who does what: roles in a project

The names change from company to company, but the responsibilities repeat:

The classic tool for making this explicit is the RACI matrix, which says, for each deliverable, who does the work, who answers for the result, who is consulted, and who only needs to be informed. There's a RACI matrix template ready to fill in.

The project triangle: scope, time, cost, and quality

Every project lives on a balance. Scope is what will be delivered, time is when, cost is how much will be spent, and quality is the expected level of finish. Moving one of these points puts pressure on the others.

• Scope grows, time and cost go up with it. When the agency's client asks for three more pages on the website mid-project, someone needs to say what that costs in days and in reais.
• Time shrinks, something gives. Either more people join (cost), or part of the scope goes, or quality drops. There's no shorter deadline for free.
• Quality that isn't negotiated turns into rework. A deliverable without agreed acceptance criteria gets redone until the client gets tired or the team burns out.

The manager's role is to make this trade-off visible. When the client asks for a change, the mature answer is never "no" or "sure, no problem": it's "we can, and that pushes delivery back four days and adds this amount. Are you in?" This is called change control, and it's the cheapest defense against the project that never ends.

Methodologies: waterfall, agile, and hybrid

There's no right methodology in the abstract. There's the one that fits the type of work. The three most-used families:

Traditional (waterfall)

Everything is planned up front, and execution follows the plan in phases: discovery, design, execution, delivery. It works when the scope is known from the start, change is expensive, and delivery has a contractual date. That's the case for construction, infrastructure installation, and system rollouts with contracted deadlines. Its signature tool is the Gantt chart.

The weak point: if the initial assumption was wrong, you only find out late, when a lot has already been spent.

Agile

Instead of planning everything, the team plans a short chunk, delivers, gets feedback, and adjusts. It works when the scope is uncertain and you can deliver in parts: software, marketing campaigns, new products. The two most widespread agile practices:

• Scrum: work in fixed cycles (sprints) of one to four weeks, with a prioritized backlog, a planning meeting, short daily meetings, and a retrospective at the end. See the Scrum guide and the sprints feature.
• Kanban: continuous flow on a board with columns, limiting work in progress. Great for support, maintenance, and demand that arrives nonstop. See the Kanban guide.

The weak point of pure agile: without care, it doesn't answer "when does the whole project finish," and the client almost always wants to know.

Hybrid

Mixes the two, and it's what most Brazilian teams outside IT do without even calling it that. It uses a schedule for the whole journey (milestones, delivery dates, dependencies between stages) and a board or short cycles for the day to day. An agency, for example, keeps the campaign schedule with the client and runs the week's work on a board.

How to choose

There's a short comparison, focused only on the two most-used views, in Kanban or Gantt?.

The most-used planning tools

Method is the idea; a tool is the instrument. These are the ones that show up in almost every project, and each has a ready-made template to get you started:

WBS (work breakdown structure)

It's the hierarchical breakdown of scope: from the big deliverable down to work packages small enough to estimate. A WBS answers "what needs to be done" before "when." If it's incomplete, the schedule is born full of holes. See the WBS template.

Schedule and Gantt

It takes the WBS tasks, estimates duration, links the dependencies, and shows when everything ends. The Gantt chart guide explains the format and the critical path, and the project schedule template gives you a starting point.

Kanban board

A view of work in progress by columns (to do, in progress, in review, done). It answers "where do things stand," and it's the preferred tool for the day to day.

RACI matrix

Defines who is responsible, who answers for the delivery, who is consulted, and who is informed. It ends the "I thought it was you."

5W2H

An action plan in seven questions (what, why, where, when, who, how, how much). It's the fastest way to turn a meeting decision into an action with an owner and a deadline. See the 5W2H guide and the 5W2H template.

Status report

One page, once a week, for the client or leadership: what was delivered, what's next, what's at risk, and what you need from them. Simpler than it sounds, and the thing that cuts the most meetings. There's a weekly status report template.

A project from start to finish: an agency in Florianópolis

To see the cycle at work, imagine an eight-person agency in Florianópolis that wins the website redesign for a chain of clinics, with delivery in ten weeks.

• Initiation. The account partner writes the brief on one page: goal (increase appointment requests through the site), scope (12 pages and a blog), timeline (10 weeks), and who approves on the clinic's side (the marketing manager, one person).
• Planning. The tech lead breaks the scope into tasks, each with an owner. The designer estimates the layout, the developer estimates the pages. Milestones: layout approved in week 3, content received in week 5, launch in week 10. Copywriting depends on material from the clinic, so it gets extra buffer.
• Execution. The team works on the board. In the 15-minute Monday meeting, they look at what's stuck. A request for an extra "insurance plans" page arrives over WhatsApp and, instead of accepting it, the agency logs the change and states the impact: four days and an additional fee.
• Monitoring. Every Friday, a one-page status report goes to the clinic's manager. In week 6, the content still hasn't arrived, and the report already warns that the week 5 milestone slipped and asks for the material by Wednesday.
• Closing. At launch, the clinic signs the acceptance, the agency closes out the hours and holds a half-hour retrospective. Lesson recorded: "client content is risk number one; ask for the material in week 1."

None of this requires special technology. It requires the plan to be in one place, each task to have an owner, and the report to go out every week, even when the news is bad. That's the gain: the problem shows up in week 6, not week 10.

Project management on a small team

Most of the literature is written for big companies and scares anyone with five people. The lean version fits in a short list of habits:

1. Every project has a one-page description with goal, scope, and date.
2. Every piece of work becomes a task with an assignee and a real date.
3. There's a short, fixed weekly meeting, looking at the board and the dates.
4. Every scope change is logged, with its impact on time and cost.
5. The client receives progress on a predictable rhythm, without having to ask.

If your team already does this, it's managing projects. The tool makes these habits cheaper to maintain, not to create them.

Metrics: how to tell if the project is healthy

You don't need thirty metrics. For most teams, six views are enough:

• Planned vs. actual progress. How many tasks or deliverables should be done today and how many are.
• Overdue tasks. How many, with whom, and for how long. Delay that grows every week is the clearest sign of a sick project.
• Hours spent vs. estimated. Shows whether estimates are realistic and where effort is leaking. For anyone billing by the hour, it's also revenue. See how Tasskee handles hours per project.
• Actual vs. budgeted cost. What's already been spent against what was planned for this point in the project.
• Workload per person. Who's overloaded and who has slack. A blown deadline is usually a distribution problem, not an effort problem.
• Open risks. What could get in the way, how likely it is, and who's handling it.

More important than the list is the routine. Looking at these metrics every week, with the same question ("what changed since last time?"), is worth more than a sophisticated dashboard nobody opens.

The most common mistakes (and how to avoid them)

1. Starting without a written scope. "A corporate website" means different things to different people. Write down what's in and, above all, what's out.
2. A task with no owner. A task assigned to "the team" belongs to nobody. One owner per task, always.
3. A deadline with no real date. "By the end of the month" is not a deadline. A date on the calendar, one the system can follow up on.
4. Optimistic estimates. Almost everyone estimates the best case. Ask for the estimate from whoever will do the work and add buffer to uncertain stages.
5. Informal scope changes. The request arrives over WhatsApp, nobody logs it, and the project gets fat. Log it and state the cost of the change.
6. Planning once and never updating. An outdated plan is worse than none, because it inspires confidence that doesn't exist. Review it every week, in 15 minutes.
7. Scattered information. Half in email, half in a spreadsheet, half in the WhatsApp group. The project needs one place.
8. Skipping the closing. Without formal acceptance and a retrospective, the project "ends" in an argument and the same mistake comes back on the next one.

How to choose project management software

The temptation is to start with the tool. Start with the questions, in this order:

1. What kind of work does the team do? If it's continuous flow, a board is enough. If it has delivery dates and chained stages, you need a schedule with dependencies.
2. How many people, and how many from outside? Clients and vendors who only follow along or approve shouldn't take up a paid seat.
3. In what currency and how do you pay? A tool billed in dollars goes up and down with the exchange rate, and doesn't always accept boleto or Pix.
4. Are the four views in the same place? List, board, calendar, and schedule should be views of the same tasks, without duplicating anything.
5. Can you start free and grow? Test with one real project before migrating all the others.

The article how to choose project management software details each criterion, and the alternatives page compares Tasskee, point by point, with the tools teams compare most. For anyone leaving spreadsheets and wanting to start without spending, it's also worth reading about free project management.

How to do it in Tasskee

Tasskee is a Brazilian project management platform, with pricing in reais. Here's how this guide's method looks in practice, following the same life cycle phases.

Initiation and planning

1. Create the project and give it a name, an owner, and a goal written in the description. The Free plan holds 3 projects; Start, 10; Pro, unlimited projects.
2. Break the scope into tasks. Each task has an assignee, date, priority, checklist, subtasks, tags, comments, and attachments. If the scope comes from meeting minutes or a document, you can import the text and turn it into tasks with AI.
3. Group by workstream when the project has parallel tracks (for example, "detailed design," "procurement," and "construction," at a construction company).

Execution and monitoring

1. Use the right views for each conversation. The Kanban board in the daily meeting, the list for individual work, the calendar for the week's deadlines, and the Gantt schedule (on the Pro plan) with dependencies, milestones, and critical path for the conversation with the client. They're views of the same tasks: changing one updates the others.
2. For short cycles, use sprints with backlog, burndown, and team velocity (Pro plan).
3. Log hours and track workload by project and by person, from the Start plan. The reports and dashboards show delays and progress without a parallel spreadsheet.
4. Automate the repetitive: alerts, status changes, and assignments following rules, on all plans, with a history of what the automation did and how to undo it. See the automations.

Client on board and closing

1. Invite the client through the guest portal. They follow the project, comment, and approve without taking up a user seat.
2. Formalize the acceptance through a form with a simple electronic signature (name, IP, date and time, and document hash; it's not an ICP-Brasil signature).
3. Close the hours for the client as PDF or CSV, when the project is billed by the hour.

To get started, the Free plan is free, with no expiration and no credit card: up to 3 users and 3 projects, with list, Kanban board, and daily planner. The 15-day trial unlocks all of Pro, also with no card. If you don't choose a plan at the end of the trial, the account becomes Free and nothing is deleted.