Project Management & Agile Courses
Deliver work on time and on purpose - classic project management, Scrum, Kanban, and the certifications that go with them
The methods in this section are simple. Scrum fits in a short guide, the stage-gate structure of a traditional method fits on a page, and a competent person can learn either in a weekend. Nobody struggles because they misremembered a ceremony. They struggle because two directors want different things, because the estimate was a wish, and because someone has to say out loud that the date will not be met. Courses teach the simple half thoroughly and the hard half barely at all.
Certificates here are unusually load-bearing
In project management a credential often acts as a filter rather than a bonus, because the work is hard to evaluate from a CV. Which one depends on geography and sector: the PMI credentials dominate North America and multinationals, PRINCE2 the UK and European public sector, IPMA the German-speaking engineering world, and the Scrum credentials sit across all of them for team-level roles. The certification pages give each one's cost, prerequisites and validity, including the experience requirements that catch people out after they have already paid for a course.
The hard half, and how to spot a course that covers it
- Estimation under uncertainty, including how to present a range to someone who wants a date.
- Saying no, and the ways of saying it that leave a working relationship intact.
- Escalation: when, to whom, and how to do it without it reading as blame.
- Delivering bad news early, which is the single behaviour that most distinguishes trusted project managers.
A syllabus full of artefacts and ceremonies covers none of these. Look for case studies where something goes wrong, role-play, or an instructor who talks about projects they did not rescue.
Agile and traditional are tools, not identities
Practitioners argue about this more than their clients do. Predictable work with a fixed scope and a regulatory deadline does not benefit from iteration for its own sake; uncertain work does not survive a plan written once at the start. Most real organisations run a mixture and want someone who can tell which situation they are in. The vocabulary that underpins both sits in the freelance and project concepts, which cover scope, statements of work and what changes when the brief moves.
Certifications in this area
- Certified Associate in Project Management (CAPM) · Foundational
- IPMA Level D: Certified Project Management Associate · Foundational
- PRINCE2 7 Foundation · Foundational
- Professional Scrum Master I (PSM I) · Foundational
- Professional Scrum Product Owner I (PSPO I) · Foundational
- Project Management Professional (PMP) · Professional
Concepts behind this area
Incident Management (IT Service 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.
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.
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.
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.
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.
The field, explained: Freelance Work
This category belongs to the field Business, Projects and Management, which maps the topics, concepts and certifications behind these courses.
Frequently asked
- Which certification should I take first?
- The one recognised where you want to work. A Scrum credential is cheap, fast and never expires, so it is a sensible first step for team-level roles. The PMI and IPMA routes require documented experience and are worth planning around rather than buying on impulse.
- Can I become a project manager without managing projects?
- Not straightforwardly, but the path usually runs through coordinating something real: a small internal project, a workstream, a volunteer effort. Certificates open interviews; the first genuine story of a project that went sideways gets the job.
- Is Scrum Master a real career?
- It is a real role and an exposed one. Where an organisation treats it as a facilitator with no authority it becomes frustrating; where it is a coaching role with the backing to change how the team works it is substantial. Ask which version a job is before accepting it.
- Agile or traditional: which should I learn?
- Both, briefly, then depth in whichever your sector uses. The transferable skill is diagnosing which kind of work you are looking at, and that is what makes someone useful across both.
Why Learn Project Management & Agile?
Both schools of getting things done: traditional project management with its PMP-style body of knowledge, and the agile family - Scrum, Kanban, and their ceremonies - plus the certification paths (PMP, PSM, CSM) that formalize the skill.
Last reviewed 26 September 2026 · Getting Digital