Project Management Certifications: What IPMA, PMP and Scrum Say

Why project management certifications are hard to read

One applicant lists a PMP on his résumé, another an IPMA Level D and a Scrum Master certificate. A service provider advertises that its project manager is certified. A public contracting authority requires a certified project manager in its tender. In all these cases, a certification is meant to prove something that cannot be seen from the outside: that someone can lead projects.

Whether it does depends heavily on the certification. This leads to the guiding question of this assessment: What do the common project management certifications actually say, and when are they worthwhile for a small company, both in hiring and in training? To answer it, we first clarify the terms and give an overview of the main certifications. Then we assess them with signaling theory, review the research, weigh two perspectives, and derive rules for practice.

A certification answers the question of what someone knows. Whether they can get a project through a difficult week, you still have to ask.

Terms: certification, certificate of attendance, recertification

A certification here is confirmation by an independent body that a person has met defined requirements in an examination. It differs from a certificate of attendance, which only proves that someone attended a course. Recertification requires a certification to be renewed after a few years through evidence of further training or practice; otherwise it lapses.

For the assessment, a second distinction matters more. Knowledge exams test whether someone knows the terms, processes, and rules of a method, usually in a multiple-choice test. Competence assessments evaluate whether someone has applied this knowledge in real projects, for example through project reports, proof of experience, or an interview with assessors. Most entry-level certifications are knowledge exams.

The main certifications at a glance

In German-speaking countries, five certifications are particularly common. They differ in issuer, prerequisites, and validity. The information reflects the situation in November 2026 according to the issuers’ and certification bodies’ websites. Prices and details change regularly.

Two changes are new. PMI changed its exam in July 2026 and now gives considerably more weight to the business context of projects. And Scrum certifications are narrower in content than the others: they concern a single way of working, which according to the article on agile or traditional fits mainly projects whose goal or path is still unclear.

The thinking model: certifications as signals

In 1973, the economist Michael Spence developed signaling theory using the example of the labor market. When one side cannot observe the quality of the other, it needs a signal. A signal is credible only if it is more costly for someone of poor quality than for someone of good quality. A degree convinces an employer because it is harder to obtain for less capable applicants. The articles on guarantees and on the employer brand use the same theory.

Applied to project management certifications, this means: a certification says more about the ability to lead projects the harder it is to get without that ability. A knowledge exam you pass after a weekend of study is a weak signal of leadership ability but a useful signal of basic knowledge. A certification that requires three years of documented project leadership or has project reports assessed is harder to fake and therefore more meaningful.

A comparison from road traffic makes the difference tangible. The written driving test shows that someone knows the rules. It does not show whether they drive safely on ice. A bus company therefore asks not only for the license but for years behind the wheel and accident-free miles.

What research shows about certifications and project success

Robust studies on the link between certification and project success are rare. One of the more precise comes from Strang and Vajjhala (2025). They analyzed data from 518 team members across many projects at a fintech company from 2021 to 2024. Only 4 percent held a PMP. Certification was weakly positively related to project success. Another factor had a much stronger effect: team members’ willingness to disclose their past performance reviews. According to the authors, this willingness was about four times as influential as certification and raised the explained share of differences in project success from 9.6 to 18.8 percent.

The authors name their own limits. A single company was studied, the data are partly self-reported, and the timing of the measurements does not allow firm conclusions about cause and effect. The finding fits signaling theory, though: disclosed evidence of performance in real projects is a stronger signal than a certification.

What project managers need in difficult situations is shown by a survey by Gmerski, Opas, and Ćwil (2025). 151 professionals from Polish project management communities, including members of IPMA Poland, rated the 28 competences of the IPMA framework for projects triggered by an unexpected crisis. Interpersonal competences ranked highest, followed by risk management and timely handling of information. Procedural and compliance competences were considered less important in the first phase. The very competences that matter are the ones knowledge tests examine least.

Useful proof or paper? Two perspectives

The first view says: certifications create a common language and a minimum standard. Whoever is certified knows terms such as milestone, risk register, and acceptance and does not have to learn them at the company. For customers and public contracting authorities, they are verifiable proof, and in some tenders they are a requirement. When such tenders are worthwhile for small companies is described in the guide to public tenders.

The second view says: a certification proves a passed exam and little else. Projects in small companies rarely fail because someone does not know the term work package, but because of unclear goals, lack of time, and difficult conversations with customers. A multiple-choice test does not examine these abilities.

I consider both views justified and draw from them a distinction between filter and selection. As a filter, certifications are useful: they show that someone has engaged seriously with the field, and for certifications requiring proof of experience, that experience exists. As a selection criterion, they are of little use because they barely measure what determines success. Selection belongs in the structured interview about real projects, as described in the guide to the job interview.

When is a certification worthwhile for your company?

For training your own employees, the question is turned around. Here it is not about the external signal but about what is learned. The article on planning training describes that learning takes hold mainly when it can be applied immediately. A course without an ongoing project fizzles out. Four cases follow in which a certification pays off for a small company.

1. Customers or tenders require it. Then the certification is an entry ticket, and the choice follows what is required.
2. An employee takes on projects for the first time. An entry level such as IPMA Level D or PRINCE2 Foundation provides the basic terms if a real project runs in parallel.
3. The team is to introduce a shared way of working. A Scrum fundamentals course helps if the team actually wants to and may work according to Scrum.
4. Experienced project managers are to reflect on their practice. Higher levels that assess projects force reflection, much like well-run lessons learned.

The example shows that working time often costs more than the fee. A certification that is not applied in a project after the exam is therefore mainly an expensive certificate. What a lean project plan for small teams looks like, on which the learning can be tested, is described in the guide to planning projects in small teams.

Questions for certified applicants

• Which project did you last lead, with what goal, budget, and team?
• When was it in danger of failing, and what exactly did you do that week?
• What from your certification did you apply in this project, and what did you deliberately leave out?
• May I speak with a client or team member from this project?

Conclusion: what do project management certifications say?

The question was
the common project management certifications say and when they are worthwhile for a small company. They say different things. Scrum certifications and entry levels prove knowledge of terms and methods. The PMP and the higher IPMA levels also prove experience, because they require documented project leadership or the assessment of real projects. According to signaling theory, these certifications are therefore the more meaningful ones.

The research is thin but points in the same direction: certifications are weakly related to project success, disclosed performance from real projects much more strongly. For hiring, a certification works as a filter; for selection, the interview decides. For training, it pays off when customers require it or when what is learned is applied immediately in a project. The sober observation is: a certification is worth as much as the project in which it proves itself afterward.

What you can do this week

1. Check whether customers or tenders you take part in require specific certifications.
2. Classify the certifications in your team by whether they prove knowledge or experience.
3. Add the four questions for certified applicants to your interview guide.
4. Plan a certification only when a project is set in which the learning will be applied immediately.