Where this came from
This process did not exist under this name before the Eighth Edition. Here is what it was called, and where the previous write-up still lives:
Elicit and Analyze Requirements is where stakeholder needs become documented requirements: the features and functions a product, service, or result has to have for it to be worth delivering.
What changed
This is Collect Requirements renamed, and the two added words are the substance of the change. “Collect” describes gathering what stakeholders say they want. “Elicit and analyze” describes drawing out what they have not said, and then testing what you have for consistency, feasibility, and value. The second is what business analysts have always actually done; the eighth edition puts it in the name of the process.
The tool list moves the same way. Design thinking and prioritization/ranking now sit alongside the familiar data-gathering and data-analysis groupings.
The output list got shorter, not longer
This is the change most likely to catch someone out. The process now lists a single output: requirements documentation. The requirements traceability matrix, which the previous set produced here, is no longer named as an output of this process.
Traceability has not left project management. It has stopped being an artifact that this particular process is defined as producing — which is consistent with the edition’s general retreat from prescribing a fixed deliverable for every step.
If you learned the previous set
Adaptive delivery gets an explicit mention rather than a footnote: requirements arrive as user stories and are prioritized in a backlog, and the guide treats that as a normal shape for this process’s output, not a variation on the real thing.
ITTO at a glance
All three lists are formally open-ended — every ITTO column in the eighth edition ends in “Etc.”, so none of them is a closed set to be memorized. PMBOK® Guide — Eighth Edition, §2.2.2.2. What changed in the ITTOs, across all 40 processes.