ITTO explained — what it actually is, walked through one real project

Reference. Not a lesson with an ECO task number — the thing you read before the ITTO cheat sheet makes any sense. If you already know what the columns mean and just need to look a process up, go straight to the cheat sheet.

Most people meet ITTO as a wall: forty processes, each with three lists, and an instruction to memorise them. It is the single most common reason people decide PMBOK is bureaucratic nonsense and go back to their issue tracker.

The wall is an artefact of how ITTO is usually presented, not what it is. This page walks one thread through one real project — the Coral Ridge Resort build, a $48,000,000 beachfront hotel with a schedule baseline ending 31 August 2028 — and by the end the grid should read as obvious rather than arbitrary.

What an ITTO actually is

Inputs · Tools & Techniques · Outputs. Every process takes some things, does something to them, and produces some things.

That is the entire idea. A process is a function:

	Means
Input	What must already exist before you can start
Tool / Technique	What you do to it
Output	What exists afterwards that did not before

If you have ever written a function signature, you already have the concept. inputs → transform → outputs. The PMBOK Guide applies it to 40 processes across 7 performance domains in the 8th edition.

The part nobody tells you: the lists are illustrative, not exhaustive. The 8th edition marks them so explicitly. They are examples of what a competent PM would reach for — not a checklist to tick, and not a set to recite.

Why the table form misleads you

Two honest things that most ITTO material will not tell you.

First: ITTO-per-process is a PMBOK 6 structure. The 6th edition organised the whole guide around 49 processes, each with its own ITTO block. The 7th edition moved to principles and performance domains and stopped presenting it that way. The 8th edition keeps the processes but is explicit that the lists are illustrative.

So if ITTO feels like it belongs to an older, more clerical way of thinking about projects — that is because it partly does.

Second: the exam tests it far less literally than the study material implies. Since the 2021 ECO the PMP is scenario-based. You will not be asked to recite the seven inputs to Develop Schedule. You will be asked what a project manager should do next — and answering that requires knowing what must already exist and what you are trying to produce.

Which is ITTO. Just not as a memorisation exercise.

The reframe: ITTO is not forty lists. It is a dependency graph. One process's output is the next one's input. Learn the chain and the lists mostly derive themselves.

The chain — one thread through Coral Ridge

Follow a single thread: can we start building the frame? Watch how each output becomes the next input.

1 · Initiate Project

Coral Ridge begins as an intent, not a project. Initiate Project turns it into one.

• Inputs: the business case, the sponsor's mandate
• Tool: expert judgement, and a conversation about what "done" means
• Output: the project charter — which fixes the $48M budget envelope and names the opening season the build has to hit

The charter is the first real artefact. Everything downstream cites it.

2 · Define Scope

• Input: the charter (an output from step 1)
• Tool: decomposition
• Output: the WBS — real work packages, including 1.2.4 Coastal & environmental clearance, 1.3.2 Piling on coastal soil, 1.4.1 RCC frame — floors 1–5

Notice the handoff. You could not have decomposed the scope before the charter existed, because you would have had nothing to decompose against.

3 · Identify Risks

• Input: the WBS (output of step 2) and the site surveys
• Tool: expert judgement, site investigation
• Outputs: register entries. Three real ones from Coral Ridge:

Entry	Type	Status
Coastal water table is high; piling reaches competent strata by −22 m	Assumption	Confirmed
ECA clearance granted before superstructure	Constraint	Pending
Monsoon (Jun–Sep) halts external works ~10 weeks/yr	Assumption	Confirmed

Keep the third one in view. A monsoon that stops external work for ten weeks a year is not a risk you respond to — it is a constraint you schedule around. That distinction is about to matter.

4 · Develop Schedule

Here is where the chain pays off. Look at what has to already exist:

• Inputs: the WBS (step 2), the duration estimates, and the register entries from step 3 — the monsoon windows and the ECA dependency
• Tools: the critical path method; and PERT for 1.3.2 Piling, because founding depth on coastal strata is genuinely uncertain
• Output: the schedule baseline — ending 31 August 2028

Why PERT only on the piling? Because that is the one duration nobody can state confidently. The tool is chosen to fit the uncertainty, not applied uniformly. That is what "tools and techniques" means in practice — a menu you select from, not a procedure you follow.

And the ECA constraint is why the superstructure cannot simply be scheduled early. The clearance is an output of a permitting process that is still pending. Until it exists, 1.4.1 RCC frame has an input it cannot get.

So: can we start building the frame? No — and ITTO tells you exactly why, without anyone having to explain it.

5 · Monitor Schedule

• Input: the schedule baseline (output of step 4) plus actual progress
• Tool: variance analysis, earned value
• Outputs: variance, forecasts, and change requests

And a change request is an input to Assess Changes, whose output may be a re-baseline — which becomes the new input to Monitor Schedule.

The chain closes into a loop. That is the bit the grid cannot show you.

What this means for how you study

The chain above touched five processes. Nobody memorised anything, and yet the inputs were all predictable — because an input is just an output somebody else already produced.

Three rules that generalise:

Outputs are nouns; tools are verbs. Baselines, registers, charters, plans — those are outputs. Decomposition, estimation, analysis, judgement — those are tools. If a term names a document, it is almost never a tool.

Plans are outputs of planning processes and inputs to everything else. "Plan Schedule" outputs the schedule management plan — the rules. "Develop Schedule" consumes those rules and outputs the baseline — the dates. Two different processes, two different outputs, and candidates confuse them constantly.

If a process produces something, something downstream consumes it. An output with no consumer usually means you have misread the process — or you are producing documentation nobody uses, which is its own problem.

Now the grid makes sense

With the chain in mind, the ITTO cheat sheet stops being a wall. All 40 processes, 7 performance domains, with the VanillaPM tab for each — use it as a lookup, not a reading list.

The two pages do different jobs:

	This page	Cheat sheet
Answers	"What is an ITTO, and why?"	"What are Develop Schedule's outputs?"
Shape	One narrative	A lookup grid
Read it	Once	Whenever you need an answer

Then drill it: PMP Reps turns the grid into spaced-repetition flashcards with a coach and a glossary. No login.

Where you see this in VanillaPM

The chain is not a teaching device — it is how the app is wired, and you can click it.

Open the Coral Ridge sample (python manage.py seed_tutorial) and follow the same thread: the Charter tab holds step 1's output; WBS holds step 2's; the Risk and Assumption registers hold step 3's; the Gantt consumes all of them and produces the baseline; and the Variance view is step 5 feeding change requests back into governance.

Every arrow in the chain above is a real foreign key in a real database. That is the most convincing argument that ITTO describes something true: you cannot build a working project tool without it, whether or not you call it ITTO.

What the exam actually asks

Not "list the inputs to Develop Schedule." It asks things like:

The environmental clearance a project depends on has not been granted, and the superstructure phase is due to start. What should the project manager do first?

Answering that needs no recall. It needs you to know the clearance is an input that does not yet exist, that proceeding without it manufactures a far worse problem, and that the correct move is to work the dependency and the schedule impact — not to escalate blindly, and not to start and hope.

That is ITTO doing its real job: telling you what must exist before a thing can begin, and what you are accountable for producing. The lists are the footnotes.

When you are ready for the walked tasks, start at P1 · Develop a common vision — the same Coral Ridge project, one ECO task at a time.