Initiate Project or Phase & Identify Stakeholders
The first batch of a process-by-process pipeline through all 40 PMBOK processes, full ITTO (Inputs, Tools & Techniques, Outputs) detail — covering the two processes that make up the Initiating focus area, plus reference illustrations, an illustrated case study, and a 167-question practice quiz.
Each stepper item now represents an entire focus area, not a single step — Planning alone has 19 processes across 7 domains, so it will take many steps (6, 7, 8…) to finish, same for Executing and Monitoring & Controlling. The stepper flips to "done" only once every process in that column has a finished page.
| Domain | Process | Status |
|---|---|---|
| Governance | Initiate Project or Phase | ✅ Step 5 (this page) |
| Stakeholders | Identify Stakeholders | ✅ Step 5 (this page) |
Governance Initiate Project or Phase — Definition & Authority
Reference diagram: the whole Initiate Project or Phase flow in one picture — Business Case, Benefit Management Plan, Agreements, and EEFs/OPAs feeding the Project Charter, senior management authorizing it, and that authority mobilizing the team.
- It's about developing a document — the Project Charter — to formally authorize a project or a phase.
- It outlines the project objectives.
- Defines the authority of the project manager.
- Provides the PM with authority to put resources together for project activities.
- The approved project charter formally initiates the project.
Performance Domain: Governance · Focus Area: Initiating — per the PMBOK 8th Edition Process Chart (see the reference table below).
Governance Initiate Project or Phase — Inputs
Business Documents
Business documents contain the specific information as to why a project should be initiated. There are two main documents.
- Necessary information that determines whether or not the project is worth the required investment.
- Common triggers: market demand, customer request, organizational need, legal requirement.
- Describes the main benefit(s) the project will produce once complete, and how to measure those benefits.
- The benefit could be the product, service, or result; may be created via a cost-benefit analysis.
How these documents flow together
Agreements
- SLA (Service Level Agreement)
- Letter of intent
- Contract between internal & external customer
- Work requirement to be performed for payment
Enterprise Environmental Factors & Organizational Process Assets
- Policy
- Template
Governance Initiate Project or Phase — Tools & Techniques
- Expert Judgement — get help from specialists.
- Data Gathering — brainstorming, focus groups, interviews.
- Interpersonal & Team Skills — conflict management, facilitation, meeting management.
- Meetings.
Responsibility Assignment Matrix (RAM) — RACI Chart
Reference diagram: a sample RACI chart, showing how Responsible/Accountable/Consulted/Informed get assigned across project tasks — note that only one role sits in the Accountable column per task.
A chart that displays roles & tasks of the project team.
| Letter | Role | Meaning |
|---|---|---|
| R | Responsible | The person doing the work. |
| A | Accountable | Who makes sure the work gets done. |
| C | Consulted | Expert or stakeholder who provides input. |
| I | Informed | Who needs updates. |
There should be only one person held Accountable for a given piece of work.
Project Canvas
- A visual tool used to outline & plan the key parts of a project.
- Gives the PM & stakeholders a quick, high-level view of the project.
- Early in the project, the canvas may be simple & high-level; as the project progresses, it can become more detailed.
Governance Initiate Project or Phase — Outputs
Reference diagram: what the Project Charter formally authorizes, plus what the Assumption Log exists to capture.
- Formally authorizes the existence of the project.
- Assigns the project manager and their authority level.
- Signed by the organization's senior management.
- Contains high-level requirements & risks.
- Contains preliminary project budget & schedule.
- Contains project purpose & justification.
- A list of things perceived to be true (assumptions) & things that might constrain the project.
Stakeholders Identify Stakeholders — Definition
Reference diagram: what Identify Stakeholders means, and why it keeps recurring throughout the project rather than happening just once.
- Finding out who's affected by the project.
- Identifies people, groups, or organizations that have a stake in the project.
- Includes analyzing stakeholder interest, involvement, influence, interdependencies, and impact on project success.
- Key benefit: helps the project team decide how to engage each stakeholder or group.
- Stakeholder identification should happen regularly, not just once at the beginning.
- Continuous stakeholder identification can support risk management as the project environment changes.
- This process is performed periodically throughout the project, as needed — despite sitting in the Initiating column.
Stakeholders Identify Stakeholders — Inputs
Reference diagram: the six input categories feeding Identify Stakeholders — Project Charter, Business Documents, Project Management Plan, Project Documents, Agreements, and EEFs/OPAs.
- Identifies the key stakeholder list; sponsor & customer serve as a starting point for further identification.
- Business Case — identifies the project objectives & stakeholders who care about the business value.
- Benefit Management Plan — identifies stakeholders who will receive the benefits & who are responsible for tracking them.
- Communications Management Plan — if it exists, lists previously identified stakeholders & their communication needs.
- Stakeholder Engagement Plan — documents currently identified stakeholders & engagement strategies.
- Change Log — changes may introduce new stakeholders or alter existing ones' roles.
- Issue Log — issues often surface affected stakeholders previously overlooked.
- Requirements Documentation — identifies stakeholders with requirements that must be met.
- Vendor contracts & partnership agreements identify external stakeholders with formal roles.
- Organizational culture, government regulations (may create regulatory stakeholders); stakeholder registers from prior projects & lessons learned.
Stakeholders Identify Stakeholders — Tools & Techniques
Reference diagram: the three prioritization/categorization methods side by side — the Power/Interest Grid, the Salience Model, and Direction of Influence.
- Expert Judgement — specialists with knowledge of the political environment, industry, technology, and prior project stakeholder lists.
Data Gathering
- Questionnaires and surveys — an efficient way to gather views from a large or dispersed group of potential stakeholders.
- Brainstorming — team-based ideation to identify any stakeholder who could affect or be affected by the project.
Data Analysis
- Stakeholder Analysis — examines who the stakeholders are and how they feel about the project; their role (sponsor, team member, customer, etc.); how the project affects them (positively/negatively); whether they are active or passive; and their power & authority.
- Document Analysis — reviews existing documents (charter, agreements, lessons learned) to identify stakeholders.
Data Representation — Stakeholder Mapping (Power/Interest Grid)
Methods to categorize stakeholders
- Power — level of authority
- Urgency — immediate attention
- Legitimacy — involvement
- Upward — senior management
- Downward — team members
- Outward — vendors, government, public, end users
- Sideward — peers / other PMs
- Prioritize stakeholders — e.g. using the Salience Model or Power/Interest Grid above.
Stakeholders Identify Stakeholders — Outputs
Reference diagram: the Stakeholder Register, Change Request, Project Management Plan updates, and Project Document updates that Identify Stakeholders produces.
- Project document that stores information about the project's stakeholders.
- Identification information: names, role, organizational position, location & contact details.
- Assessment information: stakeholder requirements, expectations, influence & impact.
- Classification: internal/external, power/interest, impact/influence, or other models chosen by the PM.
- Identification of new stakeholders (or changes to previously identified ones) may trigger change requests to management plans or project documents.
- Requirements Management Plan — new stakeholders may have new requirements.
- Communications Management Plan — new stakeholders need tailored communication.
- Risk Management Plan — new stakeholders may introduce or affect risk.
- Stakeholder Engagement Plan — updated to include new stakeholders & their engagement strategies.
- Assumption Log — assumptions about stakeholders documented.
- Issue Log — issues raised by or about stakeholders.
- Risk Register — risks involving stakeholders identified during analysis.
Reference The 40-Process Chart — PMBOK 8th Edition
Source: printed handout, "PMBOK 8th Edition Process Chart — Andrew Ramdayal, PMP Exam Prep Course," Technical Institute of America. This chart is being built one focus area at a time as each step's notes are transcribed — for now it shows only the Initiating column; Planning, Executing, Monitoring & Controlling, and Closing will be filled in as those steps are covered.
| Performance Domain | Initiating |
|---|---|
| Governance | Initiate Project or Phase |
| Scope | — |
| Schedule | — |
| Finance | — |
| Stakeholders | Identify Stakeholders |
| Resources | — |
| Risk | — |
Mindset Captain Vyom's Hint Sheet — Answering Like a PM
The PMP exam rewards a specific mindset more than raw recall — most wrong answers aren't wrong because you didn't know a term, they're wrong because you picked the technically-correct-sounding option instead of the most PM-like one. Read this before starting the quiz below, and come back to it whenever an answer choice feels like a toss-up.
If an option says "immediately escalate to the sponsor," "report to management," or "involve the customer" before anything else has been tried, it's almost always a trap. The PM's instinct is to work the problem with the people closest to it — the team, the functional manager, the stakeholder directly involved — before pulling in someone above them. Escalation is a late move, not a first move.
An option that patches the symptom ("just redo the work," "extend the deadline," "add more resources") loses to an option that investigates why the problem happened in the first place. Look for language like "determine the root cause," "analyze," or "meet with the team to understand" — that's usually the answer the exam wants, even if a faster fix is sitting right next to it.
This step's own material is a good example: a new stakeholder shows up mid-project → the right move isn't just "go talk to them," it's update the Stakeholder Register, and let that flow into the Communications Management Plan, the Stakeholder Engagement Plan, and the Risk Register as needed. If an option skips the paperwork and jumps straight to action, be suspicious — PMI wants you to formalize what changed before you change your behavior around it.
A PM doesn't have unlimited authority — only what the Project Charter grants. If an option has the PM unilaterally approving a scope change, spending outside the budget, or overriding the sponsor, that's a red flag no matter how sensible it sounds operationally. The Charter is the leash; work within it, or go get it extended through a proper change request.
PMI expects you to respect the standard flow (you don't skip Identify Stakeholders because you're in a hurry) — but it also expects tailoring: a two-person project doesn't need the same ceremony as a hundred-person one. When a question describes a specific project context (agile team, small startup, heavily regulated industry), let that context shape which "correct" answer fits, rather than reflexively picking the most bureaucratic-sounding option.
Watch for options that finish the task but ignore why the project exists. The Business Case and Benefit Management Plan exist precisely so the team keeps sight of the value being delivered, not just the checklist being completed. If two options both "solve" a scenario but only one ties back to the stated business benefit, that one usually wins.
A lot of Step 5 questions hinge on knowing exactly which artifact a described action belongs to — is this a Business Case (why) or a Benefit Management Plan (how we'll measure success)? An EEF (external, not controlled by the org) or an OPA (internal, reusable)? A Change Log entry or an Issue Log entry? When you're unsure, ask what specific question that document answers, not just what general category it's in.
Any RACI-flavored question that offers "everyone is accountable," "no one needs to be accountable since the team is self-managing," or "accountability rotates daily" is wrong on sight. Exactly one person is Accountable for a given piece of work — full stop — even though several people can be Responsible for actually doing it.
Several Step 5 processes — Identify Stakeholders chief among them — explicitly happen more than once, on a recurring basis throughout the project, not just during Initiating. Any option that treats one of these as a single checkbox event ("identify stakeholders once at kickoff and move on") is almost certainly the wrong answer.
- Prefer the option that involves communicating or clarifying over the one that assumes and proceeds.
- Prefer the option that documents or formalizes over the one that just verbally agrees.
- Prefer the option scoped to what a PM actually controls (schedule, team, plan, process) over one that reaches into things they don't (a sponsor's budget authority, a customer's business decision).
- If an option sounds like it was written to be obviously wrong (extreme language: "never," "always," "immediately fire," "ignore"), it usually is.
Recall Recall Quiz
Straight recall — Initiate Project or Phase and Identify Stakeholders, full ITTO, straight from the notes above.
Scenario Case Study Quiz
Short, standalone situational questions — apply the concepts above to one scenario at a time.
New Format Long Case Studies
Matches the newer PMI exam format: one longer scenario, several linked questions. 5 case studies, 6 questions each — one per topic cluster across both Step 5 processes, starring Nutan, Nargis, Madhubala, Sharmila, and Meena.
Advanced Step 1–4 Mix
Integration questions blending Step 1 (PMP Mindset & Fundamentals), Step 2 (Principles & Leadership), Step 3 (Development Approaches & Project Lifecycles), and Step 4 (Process Groups & Performance Domains) — deliberately not mixing in Step 5's own new Initiating content, since that's already covered in full above.
Illustrated The Ravenscroft Manor Case
Cover: "Opening the Case File"
The Coolsville Chronicle headline pinned to the study wall says it all: "MYSTERY HAUNTS LOCAL MANSION!" Four investigators and their scruffy grey terrier crowd around the table — a hand-drawn map marked with a red X, a folder stamped "EVIDENCE," a scattering of photographs, a magnifying glass. Pinned to the clipboard between them is a plain checklist: Who? What? Where? When? Why? How? — the very first rough sketch of a case that doesn't have a name yet.
On the wall above them hangs a five-gauge instrument panel: Initiating, Planning, Executing, Monitoring & Controlling, Closing. Only one gauge glows. The case — soon to be known as the Ravenscroft Manor case — is just getting started.
the Initiating focus area (as one of the five shown on the panel); the idea that a project begins with basic framing questions long before a formal Charter exists.
Initiate Project or Phase: Definition & Authority
Fred is summoned to the mayor's office. Behind the mayor's desk, a nameplate reads "MAYOR OF COOLSVILLE"; the town crest hangs on the wall. With a heavy stamp — "APPROVED" — the mayor presses it onto a scroll already reading "CASE CHARTER — AUTHORIZED," then hands it across. "You're formally in charge now, Fred."
Behind Fred, a chalkboard easel lists three still-empty checkboxes: Objectives. Authority. Resources. The charter is signed — but what it actually contains is still being worked out.
Initiate Project or Phase; formal authorization; the sponsor role; the Project Charter as the vehicle that grants the PM authority.
Initiate Project or Phase: Inputs
Velma's desk is buried in research. Her open binder pairs two facing pages: on the left, "Business Case — why?" — newspaper clippings ("Tourists Scared Off!", "Mystery Mansion Terrorizes Town Again!") and a sticky note doing the math: "Too scary = no visitors = no revenue!" On the right, "Benefit Mgmt Plan — how do we measure success?" — a small rising graph tracking "Visitor Confidence," with the goal spelled out underneath: "Happy Tourists, Safe Coolsville!"
Behind her, Shaggy and Scooby hold up a signed document — "AGREEMENT — Letter of Intent," countersigned by both of them — clearly pleased with themselves. Nearby, two labeled boxes sit stacked: "EEF: Town Policy" and "OPA: Case File Template."
Inputs to Initiate Project or Phase — Business Case, Benefit Management Plan, Agreements, Enterprise Environmental Factors, Organizational Process Assets.
Initiate Project or Phase: Tools
Velma stands at a chalkboard, drawing out a four-column RACI chart: Responsible (Daphne, Shaggy), Accountable (Fred's name, circled once, emphasized), Consulted (a small owl icon), Informed (the mayor's silhouette). Beside it, pinned to the van, hangs a Project Canvas — still rough. "Why?" is filled in (Frightened tourists problem / Protect Coolsville), but "What?," "Who?," "How?," and "Risks" are all still blank question marks over a loose pencil sketch of the mansion.
A stack of books sits nearby — PMBOK Guide, Lessons Learned, Best Practices — as Scooby watches Velma work, tilting his head.
Tools & Techniques for Initiate Project or Phase — Expert Judgement (the reference books), RACI/RAM, the Project Canvas as a tool built up progressively.
Initiate Project or Phase: Outputs
The Charter is signed. Fred holds it aloft with both hands, sunlight streaming through the window behind him — the same mansion from the newspaper clipping visible outside, quiet in the morning light. Daphne and Velma look on, one writing in her own notepad. Beside them, the terrier sits on a chair with a small notepad of his own, headed "Assumption Log," a paw-print pressed onto the page next to a scribbled thought: "What if it's not what it seems?"
Above them, the instrument panel is back — still only "Initiating" lit.
Outputs of Initiate Project or Phase — the Project Charter and the Assumption Log.
Identify Stakeholders: Definition
Daphne walks Coolsville's main street, notepad in hand. A thought bubble over her head sketches three stick figures connected in a triangle — a stakeholder map taking shape as she goes. First she stops the anxious owner of the Mystery Emporium, hands raised mid-explanation. He points her toward Sheriff Bronson, badge and cowboy hat, standing in front of the sheriff's office. The sheriff, in turn, gestures further down the street — toward a wary groundskeeper, peering out from behind a door marked "KEEP OUT — GROUNDSKEEPER."
Identify Stakeholders — definition, and its iterative, ongoing nature.
Identify Stakeholders: Inputs
Back in the van, Shaggy and Scooby sit cross-legged in a mess of paper — a "Change Log," an "Issue Log," and a growing stack of "Requirements" folders, a pizza box and a bag of Scooby Snacks scattered between them. A sign taped nearby jokes, "Old Case Files Never Die!"
Through the open van door, three visibly panicked goth-rock musicians — the Hex Girls — hold up a signed "AGREEMENT — Battle of the Bands." A poster behind them reads "COOLSVILLE COMMUNITY CENTER — BATTLE OF THE BANDS — CANCELLED?" "Please! Don't cancel the show!"
Inputs to Identify Stakeholders — Change Log, Issue Log, Requirements Documentation, and Agreements as a source of newly-surfaced stakeholders.
Identify Stakeholders: Tools
Out on the pavement, the team chalks out a large 2x2 grid: "Power" up the side, "Interest" along the bottom. Small photo cutouts sort the town's cast into quadrants — the Mayor and Sheriff Bronson land in Manage Closely; the town's shopkeepers in Keep Satisfied; the school principal and a local reporter in Keep Informed; a quiet old man and the groundskeeper in Monitor.
A hooded figure with a faint green glow leans in from the side: "Don't forget the ones with hidden influence!" A notebook nearby checks off a full toolkit — Power/Interest Grid, Salience Model, Stakeholder Mapping, Data Review — all ticked, all in use.
Tools & Techniques for Identify Stakeholders — the Power/Interest Grid, the Salience Model, Data Gathering and Analysis, using multiple prioritization methods together.
Identify Stakeholders: Outputs
The whole team gathers around a corkboard headed "STAKEHOLDER REGISTER," covered in photos connected by string. Card by card: the Coolsville Mayor (role: sponsor, influence: high, impact: high), Sheriff Bronson (law enforcement, high, high), the Hex Girls (performers, medium, high), Town Shopkeepers (community, medium, medium), Mystery Inc. itself (investigators, high, high), the old man with the cane, the groundskeeper — and one newly-pinned card: Vincent Van Ghoul, marked role: suspect, influence: high, impact: high.
Sticky notes nearby list what's next: "Stop the hauntings. Keep everyone safe. Save the town's reputation." And beside them: "Communication Plan. Engagement Approach. Review Regularly." A small plaque underneath reads: "Stakeholder Updates: ongoing."
Outputs of Identify Stakeholders — the Stakeholder Register, and its role as a living document that feeds forward into planning.
Illustrated Mystery Inc. Long Case Study Quiz
6 linked case studies starring the same Mystery Inc. cast from the story above — Fred, Velma, Daphne, Shaggy & Scooby, Scrappy-Doo, and the whole gang — one per topic cluster across both Step 5 processes, 5 questions each (30 total).
Illustrated RACI Chart Deep-Dive Quiz
The reference RACI chart from the Tools & Techniques section above, revisited one more time — 11 PMI-exam-level questions that require reading the chart row by row and column by column, including a chart-reading trap or two. Tough questions are flagged.
Reference diagram, revisited: the same sample RACI chart, showing how Responsible/Accountable/Consulted/Informed get assigned across project tasks — study it closely before answering the questions below.