Exam objective 1.3 asks you to describe the Initiating and Planning process groups and their key deliverables. These two groups are the foundation of every project: they decide whether a project should start and then map out exactly how it will succeed. For the CAPM exam, understanding the difference between ‘getting permission to begin’ (Initiating) and ‘creating the detailed roadmap’ (Planning) is essential because many exam questions test your ability to tell them apart.
Jump to a section
A simple way to picture Process Groups: Initiating and Planning
You are the homeowner and the project manager of a kitchen renovation. Before any walls are knocked down or cabinets ordered, you must decide what you want. This is the Initiating process group. You get a formal go-ahead from your partner (the project sponsor) by signing a one-page charter that says: ‘We are renovating the kitchen, not the whole house. Our budget is £20,000. We need it done in six weeks.’ That charter gives you the authority to start spending money and hiring contractors.
Once that charter is signed, you move to the Planning process group. Now you get specific. You sketch the new layout, list every material (tiles, worktop, sink), get quotes from plumbers and electricians, and create a detailed timeline. You plan for risks: what if the delivery of the new oven is delayed? You add a buffer week. You agree with your partner on the final design. The output is a project management plan — a thick binder with drawings, budgets, schedules, and supplier contracts. Without this plan, you would buy the wrong tiles or run out of money. Initiating says ‘yes, we are doing this project.’ Planning says ‘here is exactly how we will do it.’
In project management, a process group is a logical grouping of the project management processes. The Project Management Institute (PMI) defines five process groups: Initiating, Planning, Executing, Monitoring and Controlling, and Closing. This chapter focuses on the first two: Initiating and Planning.
Initiating is the process group where you formally authorise a new project or a new phase of an existing project. The key deliverable here is the project charter. A project charter is a document that officially starts the project. It names the project manager, gives them the authority to use organisational resources, and states the high-level requirements, objectives, and the business case (the reason the project is worth doing). Think of it as the project’s birth certificate. Without a signed charter, you are not managing a project — you are just doing unofficial work. The Initiating process group also identifies the initial stakeholders. Stakeholders are people or groups who have an interest in the project’s outcome, like customers, sponsors, or end users. You capture them in a stakeholder register, which is a simple list of names, roles, and influence levels.
Planning is the process group where you define the scope of the project, refine the objectives, and develop the course of action required to reach those objectives. The key deliverable is the project management plan. This is a comprehensive document that explains how the project will be executed, monitored, controlled, and closed. It includes subsidiary plans for scope, schedule, cost, quality, human resources, communications, risk, procurement, and stakeholder engagement. Planning also produces the scope statement (what is included and excluded), the work breakdown structure (WBS) — a hierarchical decomposition of all the work needed — and the project schedule. Risk planning is a major part of this group: you identify risks, analyse their impact, and plan responses.
Why does a project need both groups? Initiating answers the question ‘Should we do this?’ Planning answers ‘How exactly will we do it?’ A common mistake is to jump straight into planning without a clear charter. If there is no authorisation, the project may start and stop repeatedly, wasting time and money. Conversely, initiating without planning leads to vague goals and chaos during execution.
On the CAPM exam, you need to know the key outputs of each process group. For Initiating, the outputs are:
Project charter
Stakeholder register (first version)
For Planning, the outputs include:
Project management plan
Scope baseline (scope statement, WBS, WBS dictionary)
Schedule baseline
Cost baseline
Risk register
Stakeholder register (updated)
Remember that Planning is iterative. You may revisit and refine the plan as new information emerges, but the baselines (the approved versions of scope, schedule, and cost) should only change through a formal change control process.
In summary, Initiating gives you the green light and the authority to proceed. Planning gives you the detailed map. Both are critical for project success, and the CAPM exam will test your understanding of their boundaries repeatedly.
Step 1: Develop Project Charter
The project manager or sponsor creates a high-level document that authorises the project. It includes the business case, high-level scope, budget, and milestone dates. This step belongs to the Initiating process group.
Step 2: Identify Stakeholders
The project manager lists everyone who has an interest in the project, such as customers, sponsors, and team members. This creates the initial stakeholder register. Also part of Initiating.
Step 3: Develop Project Management Plan
The project manager and team create the comprehensive plan that will guide execution. This includes subsidiary plans for scope, schedule, cost, quality, risk, communications, and more. This is the main output of Planning.
Step 4: Define Scope and Create WBS
The team details exactly what is and is not included in the project, then decomposes the work into manageable pieces called the work breakdown structure (WBS). This forms the scope baseline.
Step 5: Plan Risk Management
The team identifies potential risks (both threats and opportunities), analyses their impact and probability, and plans responses. These are recorded in the risk register, a key Planning output.
An IT professional, say a project manager at a retail company, is asked to launch a new customer loyalty mobile app. Here is how Initiating and Planning happen in that real scenario.
First, the vice president of marketing approaches the PMO (Project Management Office) with an idea: build a mobile app that lets customers earn points and redeem discounts. The PMO assigns a project manager. The project manager works with the marketing sponsor to create a project charter. The charter states the business case (increase repeat purchases by 15%), the high-level scope (iOS and Android app with points tracking, not a full e-commerce site), the budget of £50,000, and a six-month deadline. The sponsor signs the charter. This is the Initiating process group in action. The project manager now has formal authority to assemble a team and use company resources.
Next, the project manager moves to Planning. They hold a kick-off meeting with developers, designers, and QA testers. Together they define the detailed scope: exactly what screens the app will have, what login methods it will support, and what the points calculation algorithm will look like. They create a work breakdown structure (WBS) breaking the project into tasks like ‘design login screen’, ‘implement points database’, and ‘test on Android 14’. They estimate the time and cost for each task and build a schedule using a Gantt chart. They also perform a risk assessment: what if a key developer leaves? They plan to cross-train a second developer. What if the app store approval takes longer? They add a two-week buffer. All of this is documented in the project management plan.
During Planning, the team also creates the scope baseline. They define what is out of scope — for example, the app will not include a live chat feature or integration with the company’s existing ERP system. They get approval from the sponsor on the final plan. Once the plan is signed off, the project moves into the Executing process group, where the actual coding and testing happen.
In a real IT context, failing to do proper Initiating and Planning leads to scope creep (uncontrolled changes), blown budgets, and missed deadlines. The CAPM exam expects you to know that these two groups happen in a specific order: Initiating first, then Planning.
The CAPM exam tests your knowledge of the Initiating and Planning process groups in several specific ways. You need to memorise the key outputs and the order of activities.
First, expect questions that ask: ‘Which process group produces the project charter?’ The answer is always Initiating. A trap is that some students think the charter is created during Planning because planning seems like the logical first step. But PMI is strict: the charter belongs to Initiating, because it authorises the project before any detailed planning begins.
Second, the exam will test your understanding of the difference between the project charter and the project management plan. The charter is high-level and short. The plan is detailed and long. A common question: ‘Which document contains the project’s business case?’ Answer: the project charter. Another: ‘Which document contains the work breakdown structure?’ Answer: the project management plan (specifically the scope baseline).
Third, the exam loves to ask about the stakeholder register. In Initiating, you create the first version of the stakeholder register. In Planning, you update it with more detailed analysis, like stakeholder power/interest grids. A trap question might say: ‘When is the stakeholder register finalised?’ The correct answer: it is never finalised — it is a living document updated throughout the project.
Fourth, know the exact list of planning outputs that are considered baselines. The three baselines are scope, schedule, and cost performance baselines. They are part of the project management plan. The exam may ask: ‘Which baseline is used to measure scope performance?’ Answer: the scope baseline.
Fifth, understand that Planning is iterative. The exam might describe a situation where the team discovers new information and the plan is updated. They will ask if this is allowed. The answer: yes, Planning is an iterative process, but any changes to baselines require formal change control.
Key terms to memorise for the exam:
Project charter: authorises the project
Project management plan: how to execute, monitor, and close
Scope baseline: approved scope statement, WBS, WBS dictionary
Stakeholder register: list of stakeholders and their characteristics
Business case: economic justification for the project (appears in the charter)
Finally, be ready for questions that mix up process groups. For example, ‘An activity belongs to which process group?’ If the activity is ‘define project scope in detail’, it belongs to Planning. If the activity is ‘obtain formal authorisation to start the project’, it belongs to Initiating. Practice these distinctions because the exam will test them repeatedly.
Initiating produces the project charter, which formally authorises the project and names the project manager.
Planning produces the project management plan, a detailed roadmap for executing, monitoring, and closing the project.
The stakeholder register is first created in Initiating and then updated throughout the planning process.
The three baselines (scope, schedule, cost) are created during planning and are part of the project management plan.
Initiating answers the question ‘should we do this?’; Planning answers ‘how will we do this?’
Planning is iterative and the project management plan can be refined as new information becomes available.
The project charter must be signed by a sponsor who has authority to fund the project.
A project cannot move into Planning until the project charter is formally approved.
These come up on the exam all the time. Here's how to tell them apart.
Initiating Process Group
Produces the project charter
Happens first in the project lifecycle
High-level authorisation, not detailed
Planning Process Group
Produces the project management plan
Happens after Initiating
Detailed, comprehensive roadmap
Project Charter
Authorises the project
High-level scope and budget
Created by sponsor or PM
Project Management Plan
Guides execution and control
Detailed scope, schedule, cost baselines
Created by project team
Stakeholder Register (Initiating)
First version created
Basic list of names and roles
Identifies initial stakeholders
Stakeholder Register (Updated in Planning)
Updated with more detail
Includes power/interest grid analysis
Reflects new stakeholders found during planning
Mistake
The project charter is created after the planning is done, because you need a full plan before you can get approval.
Correct
The project charter is created during Initiating, before any detailed planning. It gives high-level authorisation to start planning.
Beginners often think you need a detailed plan to convince sponsors, but PMI says the charter is a lightweight go-ahead document.
Mistake
The stakeholder register is only created once during Initiating and then never changed.
Correct
The stakeholder register is first created in Initiating but is updated throughout the project, especially during Planning and Executing.
Many students treat documents as static, but project management is iterative — stakeholders may change or new ones emerge.
Mistake
Initiating and Planning happen only once at the start of the project.
Correct
Initiating happens at the start of each new phase of a project, and planning is iterative throughout the project lifecycle.
Beginners think process groups are linear one-time steps, but projects often revisit planning after major changes.
Mistake
The project management plan is just a schedule and budget.
Correct
The project management plan is a comprehensive document that includes scope, schedule, cost, quality, risk, communications, and more.
Beginners reduce the plan to only two dimensions, missing the full breadth of what PMI requires.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Yes. PMI recommends a project charter for every project, regardless of size. For small projects, the charter can be a simple one-page document.
The charter is a high-level authorisation document created in Initiating. The plan is a detailed execution guide created in Planning. The charter says ‘you may start’; the plan says ‘here is how you do it’.
The project sponsor or another authorised person who has the authority to allocate resources and funds to the project.
No. Skipping Initiating means there is no formal authorisation, which can lead to wasted effort and unclear project boundaries. Always create a charter.
No. The stakeholder register includes everyone who can affect or be affected by the project, including internal team members, managers, and external customers.
Planning is iterative. You can update the project management plan, but any changes to the scope baseline must go through formal change control.
You've finished Process Groups: Initiating and Planning. Continue through the CAPM study guide to build a complete picture of the exam.
Done with this chapter?