CompTIA Project+ · Domain 2 of 4

CompTIA Project+ Domain 2: Project Life Cycle Phases

Five objectives that follow a project from business case to sign-off. Most questions ask which activity belongs in the current phase and what has to be true before the project can move on.

Exam weight
30%
Official objectives
5
Estimated questions estimate
~27
Suggested study time estimate
25–30 hrs

About 16 min read Reviewed October 2026

Overview

Project Life Cycle Phases is 30% of Project+ and walks through the five phases CompTIA uses: discovery or concept preparation, initiation, planning, execution and closing. Each phase has its own artifacts and activities, from the business case and the CapEx versus OpEx decision, through the charter, responsibility matrix and kickoff, to the work breakdown structure, budget and project management plan, then vendor management and phase gate reviews, and finally validation, contract closure and sign-off.

The domain tests sequencing. You need to know what must exist before the next step can start, such as an approved charter before detailed planning or accepted deliverables before contracts close. It uses the processes from Domain 1, records them with the tools in Domain 3, and must respect the access, security and compliance requirements in Domain 4.

How it's tested

Domain 2 questions set the scene with a phase marker, such as 'the charter was just approved' or 'all deliverables have been accepted', then ask which activity comes NEXT or which artifact the project manager needs. Performance-based items may ask you to sort activities into phases or order closing tasks.

  • Which phase is this

    An activity or artifact is described and you identify the phase it belongs to, such as a kickoff meeting in initiation or a phase gate review in execution.

  • What comes next

    The scenario states what has just finished and you choose the next correct activity, rejecting options from later phases.

  • Missing prerequisite

    Something is going wrong and the cause is a skipped earlier step, such as no responsibility matrix or no transition plan.

Reasoning it through

The sponsor has signed the charter and the project manager wants to start work quickly. Options include building the schedule, holding the kickoff, identifying stakeholders and ordering hardware. Stakeholder identification and the responsibility matrix belong to initiation and feed the kickoff, while schedules and purchases belong to planning and execution. The best next step is to identify stakeholders, because every later initiation and planning activity depends on knowing who is involved.

Objectives 5

Official objectives from the CompTIA outline, in outline order.

2.1 Explain the value of artifacts in the discovery/concept preparation phase for a project.Business case, existing vendor and client relationships, and CapEx vs. OpEx.
What it means
Before a project is authorized, the organization documents why it should exist and what it can build on: a business case comparing current state with the desired future state and expected return, any prequalified vendors, a predetermined client, existing contracts, and how the spending will be treated financially.
What to understand
The business case justifies the investment and is the reference for later go or no-go decisions. Prequalified vendors and preexisting contracts shorten procurement. Capital expenditure (CapEx) buys long-lived assets that are depreciated, while operating expenditure (OpEx) covers ongoing costs such as subscriptions; moving from on-premises servers to cloud services typically shifts spending from CapEx to OpEx.
How it shows up
A scenario asks which artifact justifies starting the project or how a cloud subscription would be classified financially.
Common confusion
Candidates treat the business case and the project charter as the same document. The business case justifies the investment; the charter, created in initiation, authorizes the project and the project manager.
2.2 Given a scenario, perform activities during the project initiation phase.Charter, stakeholders, responsibility matrix, records, access and kickoff.
What it means
Initiation formally authorizes the project. The charter names the sponsor and project manager and states high-level objectives, scope, milestones, budget and risks; stakeholders are identified and analyzed; a responsibility assignment matrix such as RACI defines who does what; and a kickoff aligns everyone.
What to understand
Know what the charter contains and who signs it (the sponsor). In RACI, Responsible does the work, Accountable owns the result and there should be one per task, Consulted gives input and Informed is kept updated. Initiation also sets up communication channels, records management and the access team members need.
How it shows up
A question describes a new project and asks for the first activity, or gives a RACI problem such as two accountable people for one task.
Common confusion
Candidates assign Accountable to everyone who works on a task. Accountable is a single owner per task; the doers are Responsible.
2.3 Given a scenario, perform activities during the project planning phase.Scope, WBS, schedule, budget, quality, risk, communication and transition plans.
What it means
Planning turns the charter into an executable plan: confirm the resource pool and procurement needs, define scope and decompose it into a work breakdown structure, build the schedule and budget, write the quality assurance and communication plans, assess risks, plan the transition or release, and assemble them into the project management plan.
What to understand
The WBS breaks deliverables into work packages, and the WBS dictionary describes each one; the scope baseline is the scope statement, WBS and dictionary together. The budget is built from cost estimates plus contingency reserve for known risks. The transition or release plan covers how the result will move to operations, including training and support.
How it shows up
A scenario asks which planning document resolves a problem, such as unclear responsibilities for work packages or no plan for handing the system to the support team.
Common confusion
Candidates think the charter replaces the project management plan. The charter is high level and authorizes the project; the plan is the detailed, approved guide for how the project will be executed and controlled.
2.4 Given a scenario, perform activities during the project execution phase.Doing the work, managing vendors, change, conflict, reporting and phase gates.
What it means
Execution carries out the plan: tasks are performed, vendors are managed against their contracts, organizational change management prepares users for the new way of working, status meetings and reports keep stakeholders informed, budget and timeline are updated, conflicts are resolved and phase gate reviews decide whether to continue.
What to understand
A phase gate review is a formal checkpoint where the sponsor or steering committee decides to proceed, change course or stop. Conflict techniques include collaborating (problem-solving, usually the preferred long-term approach), compromising, smoothing, forcing and withdrawing. Organizational change management addresses people adopting the change, not project change control.
How it shows up
A scenario describes friction between team members, a vendor missing milestones, or an upcoming gate, and asks for the best action.
Common confusion
Candidates confuse organizational change management with change control. One helps users accept and adopt the new system; the other governs changes to the project's scope, schedule and budget.
2.5 Explain the importance of activities performed during the closing phase.Validation, contract closure, access removal, release, archiving and sign-off.
What it means
Closing formally ends the project: deliverables are validated and accepted, contracts are closed, access is removed, resources are released, the closure meeting and closeout report capture results and lessons learned, documents are archived, the budget is reconciled, the team is recognized and the sponsor signs off.
What to understand
Order matters: confirm acceptance of deliverables before closing contracts and releasing the team, because you may need them to fix defects. Removing project-granted access is a security control, not an afterthought. Lessons learned and archives make the project's knowledge reusable for future work.
How it shows up
A question gives a list of closing tasks and asks which comes first, or asks why a step such as access removal or archiving matters.
Common confusion
Candidates close vendor contracts as soon as the final invoice arrives. Contracts close after the deliverables are verified as accepted, otherwise the buyer loses leverage to require corrections.

High-yield concepts

The terms, rules and formulas this domain turns into questions most often.

  • Business case

    The document that justifies the investment by comparing the current state with the future state and estimating benefits, costs and return.

    Remember
    It is written before authorization and is revisited at gate reviews to confirm the project is still worth doing.
    Tested as
    Questions ask which artifact justifies a project or supports a continue or cancel decision.
    Trap
    Treating the business case as the authorization itself, which is the charter's job.

  • CapEx vs. OpEx

    Capital expenditure buys assets with multi-year life that are depreciated; operating expenditure pays for day-to-day costs as they occur.

    Remember
    Buying servers is typically CapEx; paying a monthly cloud or SaaS subscription is typically OpEx.
    Tested as
    A discovery-phase scenario asks how a hardware purchase or subscription would be classified.
    Trap
    Assuming any IT spending is CapEx because it is technology.

  • Project charter

    The initiation document that formally authorizes the project, names the project manager and sponsor, and records high-level objectives, scope, milestones, budget and risks.

    Remember
    It is signed by the sponsor and gives the project manager authority to use organizational resources.
    Tested as
    Questions ask what document is needed before planning starts or who signs it.
    Trap
    Confusing it with the detailed project management plan produced in planning.

  • RACI matrix

    A responsibility assignment matrix showing who is Responsible, Accountable, Consulted and Informed for each deliverable or task.

    Remember
    Exactly one Accountable per task; several people may be Responsible.
    Tested as
    Scenarios about confusion over ownership or duplicated approvals.
    Trap
    Marking multiple people Accountable or mixing up Consulted (two-way) with Informed (one-way).

  • Stakeholder identification

    Finding everyone affected by or able to influence the project and analyzing their interest and influence.

    Remember
    It happens early in initiation and drives the communication plan and RACI.
    Tested as
    Questions ask the first activity after the charter is approved.
    Trap
    Waiting until planning or execution, then discovering an influential stakeholder late.

  • Kickoff meeting

    The meeting that formally starts the project with the team and key stakeholders, reviewing objectives, roles, communication and next steps.

    Remember
    It follows charter approval and stakeholder identification, so roles can be stated clearly.
    Tested as
    Ordering questions about initiation activities.
    Trap
    Holding it before the team and roles are known.

  • Work breakdown structure

    A hierarchical decomposition of the total scope into deliverables and work packages, the units of work used for estimating and assignment.

    Remember
    If work is not in the WBS, it is not in scope; the WBS dictionary describes each package.
    Tested as
    Planning scenarios about missing tasks or unclear work package definitions.
    Trap
    Treating the WBS as a schedule; it shows what, not when.

  • Transition or release plan

    The plan for moving the finished product into operations, covering deployment, training, documentation and support handoff.

    Remember
    Written during planning so operations is ready at go-live, not improvised at closing.
    Tested as
    Scenarios where the support team is unprepared after launch.
    Trap
    Assuming handoff happens automatically when the project ends.

  • Phase gate review

    A formal checkpoint between phases where the sponsor or governance body reviews performance and decides to proceed, adjust or stop.

    Remember
    It compares progress with the business case and plan, not just task completion.
    Tested as
    Execution scenarios ask what happens at a gate or who decides.
    Trap
    Treating a gate as a routine status meeting with no decision.

  • Organizational change management

    Preparing people and processes to adopt the project's outcome through communication, training and support.

    Remember
    It deals with user adoption; change control deals with changes to project baselines.
    Tested as
    Execution questions about user resistance to a new system.
    Trap
    Answering a user-resistance question with a change request.

  • Conflict resolution techniques

    Collaborating, compromising, smoothing, forcing and withdrawing are the common approaches to conflict.

    Remember
    Collaborating (problem-solving) seeks a win-win and is generally preferred for lasting resolution; forcing suits emergencies.
    Tested as
    Scenarios describe a team dispute and ask for the best technique.
    Trap
    Choosing compromise as the best answer when a collaborative solution is available.

  • Closing order

    Validate and accept deliverables, then close contracts, remove access, release resources, report, archive and obtain sign-off.

    Remember
    Acceptance comes before contract closure and team release.
    Tested as
    Ordering questions in the closing phase.
    Trap
    Releasing the team or paying the vendor before acceptance.

  • Lessons learned

    The documented record of what worked and what did not, captured during and at the end of the project.

    Remember
    Collect throughout the project and finalize at closing; archive it for future projects.
    Tested as
    Closing scenarios and questions about the value of the closure meeting.
    Trap
    Collecting lessons only at the very end, when details are forgotten.

Side by side

Concepts candidates mix up, compared on the point that decides the answer.

Business case vs. charter vs. project management plan

ConceptMeaningKey differenceCommon trap
Business case Justifies why the investment is worthwhile Discovery or concept phase; supports the decision to authorize Using it as the authority to start work
Project charter Authorizes the project and the project manager Initiation; high-level and signed by the sponsor Expecting it to hold detailed schedules and budgets
Project management plan Describes how the project will be executed, monitored and controlled Planning; detailed, integrates subsidiary plans and baselines Thinking it can be written before the charter is approved

Organizational change management vs. project change control

ConceptMeaningKey differenceCommon trap
Organizational change management Helping people adopt the new system or process Focuses on users, training and communication Using it to approve scope changes
Project change control Formal evaluation and approval of changes to baselines Focuses on scope, schedule, cost and quality Using a change request to address user resistance

Responsible vs. Accountable in RACI

ConceptMeaningKey differenceCommon trap
Responsible Performs the work on the task Can be several people Assuming the doer must also approve
Accountable Owns the outcome and signs off Exactly one per task Assigning it to every team member who contributes

Exam traps

Each trap is an answer that looks right. Learn the clue that should change your mind.

  1. Planning before authorization

    What candidates pick
    Build the schedule and budget immediately after the business case is approved.
    Why it looks right
    It feels productive and gets the project moving.
    Why it's wrong
    The charter must be approved first to authorize the project and the project manager; detailed planning follows initiation.

    Clue to watch for The scenario mentions an approved business case but no charter.

  2. Kickoff too early

    What candidates pick
    Hold the kickoff meeting the day the project is announced.
    Why it looks right
    Kickoffs are associated with starting.
    Why it's wrong
    The kickoff works only after stakeholders are identified and roles are set, so it can confirm responsibilities and communication paths.

    Clue to watch for Roles or the stakeholder list are still unknown in the scenario.

  3. Change request for resistance

    What candidates pick
    Submit a change request when users resist the new system.
    Why it looks right
    It sounds like a change problem.
    Why it's wrong
    User resistance is addressed by organizational change management: communication, training and involving users, not by changing project baselines.

    Clue to watch for Words such as 'users are reluctant' or 'adoption is low'.

  4. Close the contract on invoice

    What candidates pick
    Pay and close the vendor contract once the final invoice arrives.
    Why it looks right
    It keeps finances tidy and the vendor relationship smooth.
    Why it's wrong
    Contracts should close only after deliverables are validated and accepted, so the buyer can still require defects to be fixed.

    Clue to watch for Acceptance testing is incomplete or a defect is mentioned.

  5. Release resources first

    What candidates pick
    Reassign the team as soon as the last task finishes.
    Why it looks right
    Other projects need the people.
    Why it's wrong
    The team may be needed to correct issues found during validation; resources are released after acceptance.

    Clue to watch for The scenario lists validation or sign-off as pending.

  6. Skipping access removal

    What candidates pick
    Treat closing as paperwork: report, archive and celebrate.
    Why it looks right
    The visible closing tasks are documents and meetings.
    Why it's wrong
    Removing project-granted access to systems, facilities and data is a required closing activity that prevents security exposure after the project ends.

    Clue to watch for Contractors or temporary accounts appear in the scenario.

Answer framework

For any life cycle question, locate the phase first and then find the activity that must be complete before the next one starts.

  1. Identify the current phase from the clues in the stem, such as an approved business case, a signed charter, an approved baseline, a phase gate or accepted deliverables.
  2. List the artifacts that should already exist at this point, such as the charter, RACI or transition plan, and check whether a missing one explains the problem described.
  3. Eliminate answer options that belong to a later phase, or to an earlier phase already completed, however useful they seem.
  4. Among the remaining options, choose the activity that other activities depend on, such as stakeholder identification before the kickoff or acceptance before contract closure.
  5. Confirm the choice respects authority and governance: sponsor sign-off, phase gates, contract terms, and security steps like granting or removing access.

Practice question

A project to deploy a new HR system has completed user acceptance testing, and the sponsor has formally accepted all deliverables. The vendor contract and several contractor accounts remain open. What should the project manager do NEXT?

Want more like this? The CompTIA Project+ practice test has questions for every domain.

Checklist

0 of 14

Tick each one you can do without notes. Your ticks stay in this browser.

Study strategy

Study this domain in life cycle order, because the exam rewards knowing what must exist before each step. For each phase, write the key artifacts it produces and the activities that depend on them: business case and financial classification for discovery, charter, stakeholders, RACI and kickoff for initiation, the WBS, schedule, budget and subsidiary plans for planning, and so on.

Give extra time to the boundaries candidates underestimate: business case versus charter versus project management plan, organizational change management versus change control, and the order of closing tasks. The closing objective uses the 'explain the importance' verb, so expect questions about why access removal, contract closure and archiving matter, not just whether they happen.

After learning the phases, practice sorting mixed lists of activities into phases and answering 'what should the project manager do NEXT' items. Then connect each phase to Domain 3 by naming the tool used there, such as the Gantt chart in planning and the status report in execution, which also prepares you for tool-selection questions.

FAQ

How much of Project+ is Domain 2?

Project Life Cycle Phases is 30% of the PK0-005 exam, the second-largest domain, with five official objectives covering discovery, initiation, planning, execution and closing.

Why is there no monitoring and controlling phase?

The PK0-005 outline organizes the life cycle into discovery/concept preparation, initiation, planning, execution and closing. Tracking, reporting, budget updates and phase gates are covered inside the execution objective, and control processes such as change control sit in Domain 1.

What is the difference between the charter and the project management plan?

The charter authorizes the project and gives high-level objectives, scope and budget; the project management plan is the detailed, approved guide to how the work will be executed and controlled. The charter comes first.

Which closing activity comes first?

Validation and acceptance of deliverables. Contract closure, resource release and sign-off depend on it, so questions usually reward confirming acceptance before anything else.

Do I need to know financial calculations for the discovery phase?

Expect concepts more than math: what a business case and return on investment represent, and how CapEx and OpEx differ, including how moving to cloud services shifts spending.

How long should I study Domain 2?

As a planning estimate, about 25 to 30 hours, less if you already run projects through a formal life cycle and more if you have only worked inside Agile sprints.

How does Domain 2 connect to the other domains?

It applies the processes from Domain 1 in phase order, uses the logs and charts from Domain 3 at each stage, and must meet the security and compliance requirements from Domain 4, such as access control at initiation and closing.

Other Project Management certifications

Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.

Test your Domain 2 knowledge

You have followed a project from business case and charter through planning, execution and closing. Test whether you can choose the right next activity in timed Project+ scenarios.

Take the CompTIA Project+ practice test Check your CompTIA Project+ readiness

Keep going