Business, Projects and Management
Business is the field every other field eventually reports to. Someone has to decide which work gets done, keep it moving, bring people along and make it pay, and each of those jobs has its own vocabulary and its own standards body. This hub splits the territory into twelve topics along the lines practitioners draw themselves, from running a single project to running a whole company, and shows which role and which credential sits behind each.
Three kinds of work share this silo. The first is running work: a project with a start, an end and a budget, or a product that keeps changing for as long as anyone uses it. The second is running people: hiring, delegating, giving feedback, keeping a team pointed at one goal. The third is running a business: choosing what to sell, to whom and at what margin, then finding the customers. Most jobs mix all three in different proportions. A project manager spends half the week on people problems; a founder spends Monday on strategy and Tuesday chasing an invoice. The topics below separate the strands so each can be learned on its own terms.
Four references, two sides of the house
The work side has three public references, and they differ more in tone than in substance. The Project Management Institute's PMBOK Guide describes project work as a set of performance domains; the seventh edition named eight, among them stakeholders, team, planning, delivery and uncertainty, and the eighth edition of 2025 regroups them into seven. PMI's outline for the PMP exam cuts the same ground into People, Process and Business Environment. The Scrum Guide takes the opposite approach: a short, free text that fixes the team's accountabilities, its events and its artefacts and leaves everything else to the people doing the work. BABOK, from the International Institute of Business Analysis, covers the analyst's six knowledge areas, from planning the analysis through elicitation and requirements to judging whether a delivered solution did its job.
The organisation side is mapped by SFIA, a skills framework used by employers and public bodies to describe digital jobs. Its change and transformation category holds project and programme management, business analysis and organisational change; people and skills holds performance management and workforce planning; strategic planning sits under strategy and architecture. None is a method to follow to the letter, and none is the answer. They are the vocabularies hiring managers and exam boards use, which makes them the quickest route to being understood.
Twelve topics, seven roles
Below, every topic is set against the role that spends most time in it and the credential, if any, that examines it. An empty cell is an honest one: large parts of this field have no exam anybody asks for.
| Topic | Role that lives there | Credential that tests it |
|---|---|---|
| Project management fundamentals | Project manager, project coordinator | CAPM, PRINCE2 Foundation, IPMA Level D; PMP with experience |
| Agile, Scrum and Kanban | Scrum master, delivery lead | PSM I; the adaptive half of the PMP |
| Business analysis and requirements | Business analyst | IIBA's own ladder; CAPM touches it |
| Product management | Product owner, product manager | PSPO I |
| Organisational change and transformation | Change manager | Several practitioner schemes, none dominant |
| Leadership and people management | Team lead, line manager | None standard; the PMP's People domain |
| Business strategy and planning | Founder, strategy analyst | None |
| Operations, Lean and Six Sigma | Operations manager, process owner | Six Sigma belts from several issuers |
| Entrepreneurship and small business | Founder | None |
| Sales and negotiation | Account executive, founder | None |
| Business communication and presenting | Every role | None |
| Freelancing and independent work | Freelancer, consultant | None |
The certificates sort into two kinds. Entry certificates test vocabulary: CAPM, PRINCE2 Foundation and IPMA Level D ask whether you know what a project charter is for and how a risk register is kept, not whether you have run anything. PSM I belongs with them, although its high pass mark makes it harder than its level suggests; what it proves is that the candidate has studied the guide word by word, which is rarer than it sounds. Google's project management certificate has no exam and works as an inexpensive trial of whether the job suits you. The PMP is the credential of the other kind. Its application demands documented time spent leading projects, and PMI can audit the claim, so a pass says something about experience as well as knowledge. Which one a CV needs depends on the market: North American adverts name the PMP most often, PRINCE2 is the common currency in the UK, and IPMA is run by national associations in Germany and elsewhere.
Where to start
The right door depends on what you do now.
- Newcomers with no project history begin with project management fundamentals and business communication, then sit an entry certificate once the vocabulary feels familiar. Choose the one local adverts mention.
- Specialists moving into management, the developer who becomes a team lead or the analyst who inherits a project, begin with leadership and people management. The technical skill that earned the promotion is now the least scarce thing on the team, and delegation is the first habit to build.
- People already on an agile team begin with the Scrum Guide itself, then agile and product management, before choosing between the Scrum Master and Product Owner papers.
- Founders and freelancers begin with entrepreneurship or independent work, then sales, because nothing else on this list matters until somebody is paying.
Some neighbouring ground has its home elsewhere. Reporting and dashboards belong to data visualisation and BI, service processes such as ITIL to IT service management, campaigns and brand to marketing, and online shops to e-commerce. The practical side of client work, from platforms to tools, sits in the freelance section, and the glossary explains each term used here, with a view on where practice goes wrong.
The field, part by part
Each topic says why it exists and what it rests on; the order is the order a newcomer would take.
- Project management fundamentalsCharter, scope, schedule, cost, risk and stakeholders: the predictive vocabulary of PMBOK 7's performance domains and the PMP ECO's Process domain, tested by CAPM, PMP, PRINCE2 and IPMA.
- Agile, Scrum and KanbanThree accountabilities, five events, three artefacts and the empirical pillars of the 2020 Scrum Guide; Kanban's flow; the PSM and PSPO exams and PMP's agile half.
- Business analysis and requirementsElicitation, requirements life cycle, strategy analysis, solution evaluation: BABOK v3's six knowledge areas, the discipline between the business and the build (SFIA Change analysis).
- Product managementDiscovery, roadmaps, prioritisation, metrics and the product owner's accountability: where business analysis, agile and strategy meet (Scrum Guide's Product Owner; SFIA Product management; PSPO).
- Organisational change and transformationMaking a change stick in an organisation is its own discipline (SFIA Change planning: organisational change management and enablement; PMBOK's stakeholder and uncertainty domains).
- Leadership and people managementRunning a team: delegation, feedback, performance, hiring, motivation (SFIA People management; PMP's People domain; Udemy's largest business shelf).
- Business strategy and planningBusiness models, competitive position, planning and the numbers behind a decision (SFIA Strategic planning; Udemy Strategy; the business model canvas).
- Operations, Lean and Six SigmaProcesses, quality and waste: Lean, Six Sigma's DMAIC and the belts, supply chain and operations management (SFIA Business process improvement; Udemy Operations).
- Entrepreneurship and small businessStarting and running a small business: idea to model, funding, legal basics, first customers (Udemy Entrepreneurship; the site's own small-business and freelance readership).
- Sales and negotiationProspecting, discovery, closing, key accounts and negotiating: the revenue side of every business (Udemy Sales; SFIA Selling).
- Business communication and presentingWriting, presenting, meetings and public speaking: the skill every other business skill is delivered through (Udemy Communication; SFIA Relationships and engagement).
- Freelancing and independent workBriefs, statements of work, day rates, retainers and scope creep: how independent work is scoped, priced and agreed (the site's freelancing concepts and the /freelance/ silo).
Concepts to know
Glossary entries of this field.
- Agile
Agile is a family of delivery approaches that build a product in short iterations, each producing something usable, so that plans are corrected by what was learned rather than defended against it.
- Change Control
Change control is the process by which a proposed change to a project's agreed baseline is recorded, assessed for its effect on scope, schedule, cost and risk, and then approved, rejected or deferred by a person holding the authority to do so.
- Brief
A client brief is the short written statement of what a piece of work has to achieve, for whom, and under which fixed constraints, agreed before either side commits to a solution.
- Critical Path
The critical path is the longest chain of dependent activities through a project's schedule, which sets the earliest possible finish date and on which any delay delays the whole project.
- Day rate
A day rate sells a bounded unit of a supplier's working time rather than a finished result, so the client rather than the supplier carries the risk that the job turns out bigger than it looked.
- Definition of Done
The definition of done is the shared, written standard that every piece of work must meet before it counts as complete, covering the quality, testing, documentation and release conditions that make an increment genuinely usable.
- EVM
Earned value management measures project performance by comparing the budgeted value of work actually completed with the value planned to be complete by now and with the cost actually incurred, producing variances and indices that forecast the final cost and date.
- Gantt Chart
A Gantt chart is a schedule drawn as horizontal bars against a calendar, one bar per activity, with dependencies drawn between them and progress shown along each bar.
- Incident Management
Incident management is the service-management practice of restoring a disrupted IT service to normal operation as quickly as possible, through a defined process of logging, categorising, prioritising, resolving and closing each incident, separate from the later work of finding and fixing its root cause.
- Kanban
Kanban is a method for managing knowledge work by making it visible on a board, limiting how much is in progress at each stage, and improving the flow of items from start to finish rather than working in fixed iterations.
- Product Backlog
A product backlog is the single ordered list of everything that might be done to improve a product, owned by one person who decides the order, refined continuously, and drawn from when each iteration is planned.
- Project Charter
A project charter is the short document that formally authorises a project, names its sponsor and manager, states its purpose, its intended outcomes and its boundaries, and gives the manager the authority to spend the organisation's resources on it.
- Project Scope
Project scope is the agreed description of what a project will deliver and what it will not, stated precisely enough that a change to it can be recognised as a change and decided rather than absorbed.
- Retainer
A retainer is a recurring fee that holds a supplier's time or availability open across a period, so what the client buys is first call on somebody's attention rather than any named artefact.
- Retrospective
A retrospective is a regular, structured meeting in which a team examines how it worked over the last period, decides what to change, and commits to one or two concrete improvements for the next one.
- Risk Register
A risk register is the project's living list of things that might happen and would matter, each with an estimate of likelihood and impact, a planned response, an owner and a review date.
- Scope creep
Scope creep is the quiet expansion of a priced piece of client work through additions that each look too minor to renegotiate, until what gets delivered is substantially larger than what was sold.
- Scrum
Scrum is a lightweight framework for delivering complex work in fixed-length iterations called sprints, with three accountabilities, five events and three artefacts, defined in a short public guide.
- Sprint
A sprint is a fixed-length iteration of one month or less in which a team plans a goal, builds a usable increment toward it, shows the result, and reviews how it worked, before the next sprint begins immediately.
- Stakeholder Management
Stakeholder management is the practice of identifying everyone who affects or is affected by a project, understanding what each wants and can do, and engaging them deliberately so that the project keeps the support it needs and hears the objections while they are cheap.
- Statement of work
A statement of work is the document that commits one bounded piece of work to paper: what gets built, on which assumptions, to what deadline, for what money, and what sits outside it.
- User Story
A user story is a short description of a piece of functionality from the perspective of the person who needs it, stating who they are, what they want and why, and carrying acceptance criteria that say when it is done.
- WBS
A work breakdown structure decomposes a project's total scope into a hierarchy of deliverables and, at the bottom, work packages small enough to estimate, assign and track, so that everything to be produced appears exactly once.
Certifications that test it
Vendor exams and free certificates; facts, cost and the preparation path are on each page, and the certifications hub has them all.
- PMI · CAPMCertified Associate in Project Management (CAPM)
- Google · Course completionGoogle Project Management Professional Certificate
- GPM / IPMA · IPMA Level DIPMA Level D — Certified Project Management Associate
- PeopleCert · PRINCE2 Foundation (Version 7)PRINCE2 7 Foundation
- Scrum.org · PSM IProfessional Scrum Master I (PSM I)
- Scrum.org · PSPO IProfessional Scrum Product Owner I (PSPO I)
- PMI · PMPProject Management Professional (PMP)
Neighbouring fields
- Finance and Accounting
Budgets, pricing and unit economics are where the two fields meet; the business hub owns strategy and running the firm, this hub owns the numbers.
- Data, Analytics and AI
Analytics and BI report the business; the data field owns the methods, this hub owns the decisions they inform.
- Digital Marketing
Sales and marketing are two halves of revenue; the marketing field owns the channels, this hub owns strategy, sales and the running of the firm.
- IT Support, Networking and Infrastructure
ITIL's service management is project and change management applied to IT; the IT field owns it.
Frequently asked
- Do I need a certificate to become a project manager?
- No, and plenty of working project managers hold none. A certificate helps where employers filter CVs by it, which is common for the PMP in North America and for PRINCE2 in UK public-sector and consultancy work. What wins a first project role is evidence that you have coordinated something with a deadline and several people, even as a side duty in another job.
- PMP or PRINCE2?
- The two answer different questions. PRINCE2 Foundation checks knowledge of one structured method and has no entry gate. The PMP examines judgement over predictive and agile delivery and requires documented experience of leading projects. If you cannot yet meet that gate, the real comparison is PRINCE2 Foundation against CAPM, and the deciding factor is which one your local employers name.
- Is a scrum master a kind of project manager?
- Not in the Scrum Guide's terms. The scrum master answers for the team's effectiveness and for Scrum being understood, and holds no authority over scope, dates or who does which task. Many organisations blur the two anyway. If an advert asks a scrum master for status reports and Gantt charts, it describes a project management job under another title.
- Where does business analysis end and product management begin?
- An analyst works out what a change must do and whether the delivered solution achieved it, often within a project that ends. A product manager or product owner decides what a living product should become next and answers for its value over years. The skills overlap heavily; the accountability is what differs.
- What should a developer who has just become a team lead do first?
- Talk to each person on the team alone and ask what gets in the way of their work. Then read the leadership topic here before any framework. Most new leads keep doing the technical work because it feels productive, but the job has become making other people productive, and that shift is the hard part.
Courses in the directory
6,175 courses are filed here; the top 6 by our ranking, details and the provider link on each course page.
Last reviewed 26 September 2026 · Getting Digital