1,175 Questions Name No Industry at All. The Scenario Is a Costume.

September 8, 2026 · 8 min read

TL;DR: Of 1,948 single-answer questions here, 604 mention software or IT, 87 mention construction, 72 manufacturing, 58 healthcare. And 1,175 name no industry whatsoever. The setting is scenery that sets stakes and cadence. Two questions with identical structure and different industries have the same correct answer, and that is by design.

"I work in construction, and every practice question I see is about a software team." It is one of the most common complaints from PMP candidates, and it is half true in an interesting way.

What is the actual industry mix?

We counted mentions across all 1,948 single-answer stems. A stem can match more than one category, and most match none.

Setting named in the stemCountShare of 1,948
No identifiable industry1,17560.3%
Software / IT / application / platform60431.0%
Construction / civil874.5%
Manufacturing723.7%
Healthcare / pharmaceutical583.0%
Public sector432.2%
Energy / utilities231.2%
Finance / insurance120.6%

So the complaint is right about the ranking and wrong about the magnitude. Software does dominate the named settings, roughly seven to one over construction. But the biggest category by a wide margin is no setting at all: a project manager, a team, a sponsor, a problem, and no clue what is being built.

That 60% is the tell. If the industry mattered to the answer, the item writers could not leave it out of three questions in five.

If the setting does not decide the answer, what is it for?

Three jobs, and all three are worth reading for.

It sets how reversible a mistake is. A two-week sprint on an internal tool and a concrete pour on a bridge are different because one can be redone next iteration and the other cannot. That changes how much you should find out before acting, which is genuinely a factor in what comes first.

It tells you whether an outside authority is involved. Pharmaceutical, aviation, financial services and public-sector scenarios usually imply a regulator, an inspector, or a statutory approval, and those turn "get the team's agreement" into "get the team's agreement and then confirm it clears the approval." The industry is a shorthand for the presence of a gate.

It sets the cadence. Sprints, phase gates, milestones, annual budget cycles. This one determines which vocabulary the correct answer will be phrased in, which is why it feels like it matters more than it does.

Notice that none of those is domain expertise. You do not need to know how concrete cures to answer the question about it; you need to know that a fourteen-day cure is a mandatory dependency, and the stem tells you so.

Common trap: "This scenario is about an industry I have never worked in, so I am at a disadvantage." The industry detail is almost never load-bearing. Consider the geothermal construction project drifting off schedule despite a well-performing team: the keyed answer is to review the timeline with the whole team, and it would be identical if the project were a mobile app, a hospital wing, or a satellite. What decides it is that nothing in the stem tells you where the delay is coming from. This bank explains which sentence in the scenario drove the answer, so you can see for yourself how rarely it is the industry one.

How should this change the way I read a stem?

Read the industry once, for stakes and cadence, then stop looking at it. Spend your attention on the four things that actually move the answer:

  1. What has already happened. Has the change been approved? Is the baseline set? Has the client signed off? This is the single largest source of discrimination in this bank.
  2. What is documented. A stem that mentions the risk register, the charter, or an approved plan is usually telling you that the answer involves consulting it rather than inventing something new.
  3. Who holds the decision. Sponsor, product owner, self-organizing team, change control board, regulator. Most wrong answers put the decision in the wrong pair of hands.
  4. What the scenario has deliberately not told you. The most common defect in a wrong answer is assuming a cause the stem never established. If you cannot say why the problem is happening, the correct answer is usually the one that finds out.

None of those four is industry-specific. All four are readable from any stem in any sector, which is precisely why 1,175 questions can omit the sector entirely.

Why is software over-represented at all, then?

Two honest reasons, neither of which is that the exam favours software people.

The first is that agile and iterative delivery is now a large part of the exam, and the vocabulary of agile came out of software. Sprints, backlogs, story points and definition of done are software words being applied to all kinds of work. A stem that uses them will often reach for a software setting because that is where the words sit most naturally.

The second is simply that software makes a convenient scenario. Requirements change visibly, progress is hard to see, and stakeholders can have opinions without technical knowledge. Those are useful properties for writing a question about ambiguity, and they need no explanation to a reader from any sector.

Neither reason implies the answers differ. If you are a construction, manufacturing or public-sector project manager, the translation cost is one sentence at the start of each question, and after fifty questions you will stop noticing it.

FAQ

Is the PMP exam biased toward software or IT projects? In this bank, 604 of 1,948 single-answer stems mention software, an application, a platform or IT, against 87 for construction and 72 for manufacturing. But 1,175 name no industry at all, so the largest single group is the one with no setting.

Do I need software experience to pass the PMP? No. The industry in a stem sets the stakes and the vocabulary, not the answer. The agile and iterative content is genuinely heavier than it once was, but that is a delivery-approach question rather than an industry one, and hybrid and predictive scenarios are well represented.

What is the industry detail in the stem actually doing? Three jobs: signalling how reversible a mistake is, telling you whether external approval is involved, and setting the cadence. A regulated pharmaceutical scenario and a two-week sprint scenario need different first actions for those reasons, not because of the sector.

Should I skip the industry detail when reading a question? Do not skip it, but do not study it either. Read it once for stakes and cadence, then read the rest of the stem for what actually decides the answer: what has already happened, what is documented, and who holds the decision.

Try it yourself

PMP Practice's 2,141 questions are re-certified against PMBOK 8 and the July 2026 ECO, and span predictive, hybrid and agile delivery across every sector, with every wrong answer explained rather than just marked wrong. Start the free 20-question sample - no card, no signup required to try it.

Related

Sources

FAQ

Is the PMP exam biased toward software or IT projects?

In this bank, 604 of 1,948 single-answer stems mention software, an application, a platform or IT, against 87 for construction and 72 for manufacturing. But 1,175 name no industry at all, so the largest single group is the one with no setting.

Do I need software experience to pass the PMP?

No. The industry in a stem sets the stakes and the vocabulary, not the answer. The agile and iterative content is genuinely heavier than it once was, but that is a delivery-approach question rather than an industry one, and hybrid and predictive scenarios are well represented.

What is the industry detail in the stem actually doing?

Three jobs: signalling how reversible a mistake is, telling you whether external approval is involved, and setting the cadence. A regulated pharmaceutical scenario and a two-week sprint scenario need different first actions for those reasons, not because of the sector.

Should I skip the industry detail when reading a question?

Do not skip it, but do not study it either. Read it once for stakes and cadence, then read the rest of the stem for what actually decides the answer: what has already happened, what is documented, and who holds the decision.