PSP — AACE Planning & Scheduling Professional Exam Blueprint

Last revised: July 1, 2026

Practical exam blueprint for the AACE International PSP exam: planning, scheduling, CPM, controls, updates, change, risk, and final review.

How to Use This Exam Blueprint

Use this checklist as an independent study map for the AACE International AACE Planning & Scheduling Professional (PSP) exam, code PSP. It is designed to help you turn broad planning and scheduling knowledge into exam-ready skills.

This page does not state official exam weights or scoring rules. Treat each readiness area as something you should be able to explain, calculate, interpret, or apply in a realistic project-controls scenario.

Readiness scoring

Score	What it means	Action
Green	You can answer scenario and calculation questions without notes.	Maintain with mixed practice.
Yellow	You understand the topic but make errors under time pressure.	Drill targeted examples and traps.
Red	You rely on memorization or cannot apply the concept.	Relearn, then practice from first principles.

Topic-area readiness table

Readiness area	Be ready to do this	Evidence you are ready
Planning vs. scheduling	Explain how planning decisions become schedule activities, logic, calendars, resources, and control points.	You can distinguish project planning, schedule development, schedule maintenance, and schedule control in a scenario.
Project scope and work breakdown	Convert scope, deliverables, contract requirements, and assumptions into a structured planning basis.	You can identify missing scope, weak activity definitions, vague milestones, and poor responsibility assignment.
Activity definition	Build or critique an activity list with clear descriptions, durations, predecessors, successors, and measurable completion criteria.	You can spot activities that are too broad, too granular, duplicated, or not tied to deliverables.
Schedule logic	Apply finish-to-start, start-to-start, finish-to-finish, leads, lags, constraints, and network logic correctly.	You can explain why logic is mandatory, discretionary, preferential, or external.
CPM fundamentals	Perform forward pass, backward pass, critical path, total float, free float, and near-critical path analysis.	You can calculate dates and float by hand and explain what changed when logic or duration changes.
Calendars and constraints	Interpret project calendars, activity calendars, non-work periods, date constraints, deadlines, and imposed milestones.	You can identify when a date is driven by logic versus artificially constrained.
Duration estimating	Estimate durations from quantities, production rates, crew assumptions, historical data, and uncertainty ranges.	You can explain the basis of duration and identify unrealistic productivity assumptions.
Resource planning	Relate labor, equipment, materials, crews, and availability limits to schedule feasibility.	You can distinguish resource loading from resource leveling and describe the schedule effect.
Cost and schedule integration	Understand how cost-loaded schedules, earned value concepts, cash flow, and progress measurement connect to schedule control.	You can interpret schedule variance without confusing cost progress with physical progress.
Baseline schedule	Explain baseline purpose, review criteria, approval, traceability, and change control.	You can say when to preserve, revise, or rebaseline a schedule and what documentation is needed.
Schedule updates	Apply data date, actual starts/finishes, remaining duration, percent complete, logic changes, and forecast dates.	You can diagnose why an update changed the critical path or created negative float.
Progress measurement	Select appropriate progress measures for different work types.	You can separate physical percent complete, duration percent complete, and earned value indicators.
Variance and forecasting	Analyze start/finish variance, float erosion, milestone slippage, and forecast completion.	You can prepare a concise schedule narrative explaining causes, impacts, and corrective options.
Change and delay analysis	Recognize schedule impacts from changes, late information, productivity loss, access constraints, and resequencing.	You can identify what records and schedule versions are needed before drawing conclusions.
Schedule risk	Relate uncertainty, risk events, contingency, mitigation, and probabilistic thinking to schedule confidence.	You can explain why a deterministic finish date may not equal a high-confidence completion date.
Quality checks	Review a schedule for missing logic, open ends, excessive constraints, long durations, excessive lags, invalid dates, and weak coding.	You can critique a schedule without relying only on software output.
Communication and reporting	Translate schedule data into executive summaries, lookaheads, milestone reports, variance reports, and narratives.	You can tailor the message for owner, contractor, scheduler, project manager, and controls stakeholders.
Professional judgment	Choose defensible next actions when data is incomplete, stakeholders disagree, or pressure exists to manipulate the schedule.	You can justify your answer using transparency, documentation, governance, and schedule integrity.

Planning and schedule-development checklist

Project planning foundation

You should be able to check each item confidently:

Explain the difference between planning the work and scheduling the work.
Identify the project objective, completion requirements, major deliverables, constraints, and assumptions.
Determine which stakeholders provide scope, logic, production, calendar, access, procurement, commissioning, or turnover information.
Recognize how contract requirements, governance processes, and reporting cycles influence schedule structure.
Define the schedule’s purpose: bid planning, baseline control, lookahead planning, recovery planning, forensic analysis, or management reporting.
Explain why schedule level of detail should be tailored to the decision being supported.
Identify when rolling-wave planning is appropriate because future work is not yet fully defined.
Distinguish a milestone schedule, summary schedule, detailed control schedule, and short-interval lookahead.

Scope, WBS, and activity definition

Topic	Exam-ready skill	Common error
WBS / work packaging	Break scope into manageable deliverables or work packages.	Treating departments, cost accounts, or phases as complete schedule logic.
Activity descriptions	Write activities with action, object, and measurable completion.	Using vague labels such as “work on area” or “continue construction.”
Milestones	Use milestones for meaningful start, finish, approval, turnover, or external events.	Using milestones as substitutes for real activity logic.
Responsibility	Assign accountable parties or disciplines where useful.	Leaving ownership unclear, making status unreliable.
Interfaces	Include owner, designer, vendor, subcontractor, permitting, inspection, testing, and commissioning interfaces.	Modeling only direct production work and ignoring external dependencies.
Completion criteria	Define how activity completion will be measured.	Confusing partial effort with deliverable completion.

“Can you do this?” activity-definition prompts

Given a scope statement, create a reasonable activity list.
Identify activities that should be split because they are too long or cover multiple crews/areas.
Identify activities that should be combined because they are too detailed for control.
Convert deliverables into measurable activity completions.
Add missing predecessor and successor relationships.
Identify external dependencies that should not be hidden in duration estimates.
Explain how WBS, activity codes, cost accounts, areas, phases, and responsibilities support filtering and reporting.

CPM and network logic readiness

Logic relationships you should know

Relationship	Meaning	Scenario cue
Finish-to-start	Successor starts after predecessor finishes.	Sequential handoff, installation after delivery, testing after installation.
Start-to-start	Successor starts after predecessor starts, often with lag.	Overlapping work such as rough-in following framing start.
Finish-to-finish	Successor finishes after predecessor finishes, often with lag.	Closeout, testing, documentation, or parallel completion dependencies.
Start-to-finish	Successor finishes after predecessor starts.	Less common; understand it, but question whether it is appropriate.
Lead	Allows overlap by accelerating successor timing.	May hide risk if used instead of explicit logic.
Lag	Waiting period between related activities.	Cure time, review period, delivery wait, or access window.
Constraint	Imposed date restriction or requirement.	Use carefully; constraints can override logic-driven dates.

CPM calculation readiness

You should be able to perform these without relying on scheduling software:

Conduct a forward pass to calculate early start and early finish.
Conduct a backward pass to calculate late start and late finish.
Determine the critical path or longest path.
Calculate total float and free float.
Explain why the critical path can change after progress, logic changes, or delays.
Identify near-critical paths and explain why they matter.
Explain the impact of multiple calendars on date calculations.
Detect open starts, open finishes, dangling logic, and logic gaps.
Explain why negative float often indicates a constraint, deadline, or required completion earlier than the logic forecast.

Use the date-counting convention given in the question. If a question gives its own convention, follow it even if your workplace uses a different one.

\[ EF = ES + D \]\[ LS = LF - D \]\[ TF = LS - ES = LF - EF \]

Where \(D\) is activity duration and \(TF\) is total float, subject to the date-counting convention used in the problem.

CPM decision checks

If the scenario says…	Ask yourself…	Better exam response
A path has zero or least float	Is it the current controlling path?	Treat it as critical or potentially critical based on the schedule logic and constraints.
Negative float appears	Is there a deadline, imposed finish, or unrealistic constraint?	Identify the driver before proposing acceleration.
A lag is very long	Is the lag representing real work?	Consider replacing hidden work with explicit activities.
Many activities have hard constraints	Is the schedule logic being overridden?	Recommend reviewing constraints and restoring logic-driven sequencing where possible.
Progress is out of sequence	Are actuals valid? How will the schedule calculation treat remaining logic?	Validate actuals, document the method, and explain forecast effect.
Critical path changed after update	Did actual progress, remaining duration, logic, calendar, or constraints change?	Trace the driver rather than assuming software error.

Duration, productivity, and resource readiness

Duration estimating

Be ready to connect quantities, production rates, crew assumptions, calendars, and uncertainty.

\[ \text{Duration} = \frac{\text{Quantity of work}}{\text{Production rate per time period}} \]

Common duration-estimating prompts:

Calculate duration from quantity and crew production rate.
Adjust duration when crew size, shift length, productivity, or calendar changes.
Explain why production rate assumptions should be documented.
Identify when duration is driven by external review, fabrication, delivery, cure time, inspection, or access rather than direct labor.
Distinguish effort hours from elapsed duration.
Recognize when optimistic durations create an unrealistic critical path.

Resource loading and leveling

Concept	What to know	Trap
Resource loading	Assigning labor, equipment, or other resources to activities.	Assuming a resource-loaded schedule is automatically feasible.
Resource availability	Limits on crews, equipment, materials, or specialist labor.	Ignoring bottleneck resources on parallel activities.
Resource leveling	Adjusting activity timing to resolve over-allocation.	Forgetting leveling may consume float or move completion.
Resource smoothing	Adjusting resources within available float.	Confusing smoothing with changing the project finish date.
Cost loading	Assigning budget or cost values to activities.	Treating cost progress as identical to physical progress.
Crew logic	Sequencing work based on crew movement and productivity.	Creating logic that looks valid but ignores real crew flow.

Resource scenario checks

If two critical activities require the same limited crew, can you identify the schedule conflict?
If resource leveling delays the finish date, can you explain why the original CPM schedule was not resource-feasible?
If a stakeholder asks to shorten duration by adding labor, can you identify productivity, access, safety, congestion, and diminishing-return issues?
If procurement delays a material, can you trace which installation, testing, commissioning, and turnover activities are affected?
If weather or site access limits productivity, can you separate calendar effects from production-rate effects?

Baseline, status, and schedule-control checklist

Baseline schedule readiness

Baseline topic	Be ready to explain
Purpose	The baseline is the approved plan used to measure performance and evaluate change.
Review	The baseline should be checked for scope coverage, logic, calendars, constraints, milestones, coding, resource assumptions, and reporting needs.
Approval	Baseline acceptance should be documented through the project’s governance process.
Preservation	The original baseline should be retained for comparison and audit trail.
Change	Approved changes may require schedule incorporation, baseline revision, or separate variance tracking depending on governance.
Traceability	Major changes should be traceable to change records, assumptions, narratives, and schedule files.

Statusing and updating

You should be able to answer update-cycle questions such as “what should the scheduler do next?”

Establish the data date.
Collect actual starts and actual finishes.
Validate remaining duration, not just percent complete.
Update progress consistently across disciplines or contractors.
Confirm whether logic changes are actual work-sequence changes or improper forecast manipulation.
Recalculate the schedule after status entry.
Review changed critical and near-critical paths.
Identify variance from baseline dates and milestone commitments.
Document causes, impacts, and assumptions in the schedule narrative.
Communicate required decisions, recovery options, or risk exposure.

    flowchart TD
	    A[Collect status or change information] --> B[Validate actual dates and remaining durations]
	    B --> C[Update schedule to data date]
	    C --> D[Recalculate CPM]
	    D --> E[Review critical path, float, milestones, and variance]
	    E --> F{Material impact?}
	    F -- No --> G[Document update and issue routine report]
	    F -- Yes --> H[Analyze cause and affected paths]
	    H --> I[Prepare options: mitigation, recovery, change, or escalation]
	    I --> J[Update narrative, logs, and governance records]

Progress measurement readiness

Measurement type	Use when	Watch for
Actual start / finish	Activity has clearly begun or completed.	Entering planned dates as actuals without evidence.
Remaining duration	Forecasting time needed from the data date.	Leaving remaining duration unchanged despite changed conditions.
Physical percent complete	Work quantity or deliverable completion can be measured.	Equating effort spent with work accomplished.
Duration percent complete	Time elapsed is a reasonable proxy.	Misleading when production is ahead or behind.
Units complete	Quantifiable work installed, produced, tested, or accepted.	Poor quantity tracking or inconsistent measurement rules.
Milestone completion	Discrete event occurred.	Claiming milestone completion before acceptance criteria are met.

Variance, forecasting, and reporting readiness

Variance analysis

Be able to interpret:

Baseline start variance.
Baseline finish variance.
Current forecast finish variance.
Milestone slippage.
Float erosion.
Critical path change.
Delayed starts caused by predecessor slippage.
Extended durations caused by productivity loss.
Acceleration or resequencing effects.
Difference between local activity variance and overall project impact.

Earned value and schedule interface

If a question gives earned value data, be ready to apply basic schedule-performance concepts while remembering that earned value indicators do not replace CPM logic.

Term	Plain meaning	Readiness cue
Planned Value	Budgeted value of work planned by a point in time.	Know what should have been earned by the status date.
Earned Value	Budgeted value of work actually accomplished.	Know what was earned based on progress rules.
Schedule Variance	EV minus PV.	Positive or negative value indicates ahead/behind planned value, not automatically CPM days.
Schedule Performance Index	EV divided by PV.	Ratio above or below 1.0 indicates performance against planned value.
CPM forecast	Logic-based forecast of finish dates.	Use for path-driven schedule impact.

Reporting prompts

Can you write a short schedule narrative explaining what changed since the last update?
Can you identify the current critical path and near-critical paths?
Can you state whether the forecast completion changed and why?
Can you separate cause, effect, and recommended action?
Can you tailor detail for an executive summary versus a scheduler’s technical review?
Can you support the report with dates, float, milestones, and documented assumptions?

Change, delay, and disruption readiness

Change-impact thinking

For PSP preparation, focus on defensible schedule logic and documentation. Legal and contractual labels can vary by contract and jurisdiction, so read the scenario carefully.

Topic	Be ready to do this
Change identification	Recognize scope changes, design changes, late approvals, differing conditions, access restrictions, procurement delays, and owner/contractor interface issues.
Impact tracing	Follow the impact through affected activities, paths, milestones, resources, and completion dates.
Contemporaneous records	Identify useful records: schedules, updates, daily reports, correspondence, RFIs, submittals, change logs, meeting minutes, progress photos, and production records.
Fragnet concept	Understand a small network of added or changed activities used to model an impact.
Time impact analysis concept	Understand prospective insertion of a change into an appropriate schedule update to evaluate forecast impact.
As-planned vs. as-built thinking	Compare planned sequence and actual performance carefully before concluding delay impact.
Concurrency awareness	Recognize that multiple delays can affect the same period or different paths.
Mitigation and recovery	Evaluate resequencing, additional resources, overtime, shift work, procurement alternatives, or scope prioritization.

Delay scenario decision points

Scenario cue	What to check first	Likely sound action
A change is issued before baseline approval	Is the change part of the original scope or new scope?	Clarify scope basis and incorporate approved planning assumptions.
A change is issued after baseline approval	Is there a change-control process?	Model the change, document assumptions, and preserve baseline comparison.
A stakeholder claims a delay affected completion	Did it affect the controlling or near-controlling path?	Trace through CPM logic and contemporaneous schedule updates.
A noncritical activity is delayed	Did it consume float or become critical later?	Analyze float use and downstream path effects.
Two delays occur in the same period	Are they on the same path, different paths, or both controlling?	Avoid simplistic conclusions; analyze timing, paths, and records.
Management asks to “fix” the schedule dates	Are dates logic-driven and documented?	Maintain schedule integrity and clearly document approved changes.
Acceleration is proposed	What is the cost, feasibility, risk, and effect on critical path?	Compare options and explain tradeoffs.

Risk, uncertainty, and contingency readiness

Schedule risk concepts

You should be able to explain:

Difference between a risk event and estimating uncertainty.
Why deterministic dates may not capture schedule confidence.
How uncertainty in critical and near-critical activities affects completion.
Why risk mitigation should be tied to specific activities or paths.
How contingency differs from hidden padding.
Why risk responses may create secondary risks.
How schedule risk information should be communicated without overstating precision.

Risk checklist

Risk area	Exam-style cue	Prepared response
Weather or seasonal limits	Calendar and productivity effects.	Model non-work periods or reduced production realistically.
Long-lead procurement	Delivery controls installation or commissioning.	Include procurement, fabrication, delivery, inspection, and release milestones.
Design or approval delays	Work cannot proceed without information.	Model submittals, reviews, RFIs, and approvals as schedule logic where appropriate.
Resource shortages	Planned parallel work is not feasible.	Test crew and equipment availability, then level or resequence.
Access constraints	Work area not available.	Include turnover, permits, outages, or access milestones.
Commissioning risk	Late testing affects turnover.	Plan testing, punch list, approvals, and handover explicitly.
Interface risk	Multiple parties share dependencies.	Use interface milestones and clear responsibility.

Schedule quality and validation checklist

Before treating a schedule as reliable, you should be able to review it for technical quality.

Technical schedule checks

Are all required scope areas represented?
Are activities clearly defined and measurable?
Does each activity have appropriate predecessors and successors?
Are open starts or open finishes justified?
Are lags used appropriately and not hiding real work?
Are leads used sparingly and logically?
Are constraints necessary, documented, and not masking poor logic?
Are calendars assigned correctly?
Are durations reasonable for the work and control level?
Are unusually long activities reviewed?
Are milestones meaningful and traceable to requirements?
Are critical and near-critical paths plausible?
Are negative float and missed deadlines explained?
Are resources and production assumptions feasible?
Are cost loading and progress rules aligned with reporting needs?
Is the data date correct in updates?
Are actual dates supported by records?
Are baseline and current schedules clearly distinguished?
Are schedule narratives consistent with the calculated schedule?

Artifact recognition checklist

Artifact	What you should be able to interpret
Network diagram	Logic flow, paths, dependencies, and sequencing.
Gantt chart	Activity timing, bars, milestones, and overlaps.
Activity list	Scope coverage, durations, coding, and responsibility.
Logic report	Missing predecessors/successors, relationship types, lags, and constraints.
Baseline comparison	Variance between approved plan and current forecast.
Lookahead schedule	Near-term work readiness and constraints.
Progress update	Actuals, remaining duration, data date, and forecast dates.
Schedule narrative	Causes, impacts, path changes, risks, and actions.
Change log	Approved, pending, and rejected changes affecting scope or schedule.
Risk register	Risk events, probability, impact, response, and ownership.
Delay analysis record	Schedule versions, events, windows, impacts, and supporting documents.

Scenario judgment checklist

The PSP exam is likely to reward applied judgment, not isolated memorization. Practice choosing the best next action.

“What should the scheduler do next?” prompts

Situation	Strong next action
Actual progress differs from the planned sequence.	Validate actuals, update remaining logic consistently, document out-of-sequence treatment, and review forecast impact.
A milestone is forecast late.	Identify the driving path, quantify variance, review mitigation options, and communicate impact.
A stakeholder disputes the current critical path.	Trace logic, calendars, constraints, and recent updates; use evidence rather than opinion.
A new constraint creates negative float.	Determine why the constraint was added, whether it is valid, and how it affects the forecast.
A schedule has many activities with no successors.	Review for open ends and missing logic before relying on critical path results.
A progress report shows high percent complete but late finish forecast.	Check remaining duration, critical path, incomplete deliverables, and progress measurement method.
A proposed recovery plan adds crews.	Test resource availability, productivity limits, access constraints, and actual effect on critical activities.
A change affects a noncritical path.	Determine available float and whether the path could become critical.
A procurement delay is discovered.	Identify downstream installation, testing, commissioning, and turnover effects.
A team wants to rebaseline to remove variance.	Confirm governance approval, change basis, audit trail, and reporting purpose.

Artifact-to-update decision table

Event	Artifact or record to review/update
New approved scope	WBS, activity list, schedule logic, baseline/change records, cost/resource loading as applicable.
Late design information	RFI/submittal logs, design milestones, affected activities, schedule narrative.
Actual start/finish received	Progress update, daily records, data-date status file.
Remaining work forecast changes	Current schedule update, narrative, risk register if uncertainty changes.
Resource shortage	Resource plan, schedule logic, leveling analysis, mitigation log.
Missed milestone	Variance report, critical path analysis, stakeholder communication.
Recovery plan adopted	Schedule update, assumptions, resource plan, cost/time tradeoff record.
Delay claim or impact request	Baseline, updates, change records, correspondence, daily reports, as-built data.
Risk response approved	Risk register, schedule activities, contingency assumptions, narrative.
Governance decision made	Decision log, baseline/change-control records, reporting package.

Common weak areas and traps

Use this list for final review. If any item feels uncomfortable, drill it before moving to full-length practice.

Weak area	Why it causes errors	How to fix it
Planning vs. scheduling	Candidates jump into dates before understanding scope and strategy.	Start every scenario by identifying purpose, deliverables, constraints, and stakeholders.
Total float vs. free float	Float terms are often confused.	Practice small networks until you can explain who can use the float and what downstream effect occurs.
Critical path vs. shortest visible bar sequence	Gantt charts can mislead.	Trace logic and calculate path duration or float.
Constraints vs. logic	Imposed dates can hide the true forecast.	Ask whether dates are calculated by relationships or forced by constraints.
Percent complete misuse	Percent complete does not always predict finish.	Focus on remaining duration and completion criteria.
Resource feasibility	CPM may assume unlimited resources.	Check resource conflicts and leveling effects.
Hidden work in lags	Long lags can conceal real activities.	Convert significant waiting, review, cure, fabrication, or delivery into explicit activities when appropriate.
Multiple calendars	Calendar differences change path timing.	Note which calendar applies to each activity or relationship.
Baseline confusion	Candidates mix original plan, current update, and revised baseline.	Label schedule versions and know the purpose of each.
Out-of-sequence progress	Software settings can change forecasts.	Understand the logic issue and document treatment.
Near-critical paths	Focusing only on one critical path misses emerging risk.	Review paths with low float and high uncertainty.
Negative float	Candidates treat it as ordinary float.	Identify the imposed date or missed deadline causing it.
Cost progress vs. schedule progress	Earned value may not show CPM path impact.	Use EV for performance indicators and CPM for logic-driven finish forecasts.
Delay conclusions without records	Claims analysis depends on timing and evidence.	Preserve baseline, updates, actual records, and change documentation.
Over-acceleration assumption	More resources do not always shorten duration.	Consider access, productivity, congestion, sequencing, safety, and cost.

Final-week checklist

Knowledge review

Review the current AACE International PSP candidate materials and compare them with your checklist gaps.
Revisit planning and scheduling terminology until definitions are precise.
Work several CPM networks by hand, including multiple paths and float calculations.
Practice interpreting schedule updates, not just building initial schedules.
Review baseline, rebaseline, revision, update, and change-control distinctions.
Review schedule narratives and variance explanations.
Review resource loading, leveling, and productivity assumptions.
Review delay, change, and impact-analysis vocabulary at a practical level.
Review schedule risk and uncertainty concepts.
Review common traps: constraints, lags, open logic, negative float, and percent complete.

Calculation practice

Forward pass and backward pass.
Total float and free float.
Critical and near-critical path identification.
Duration from quantity and production rate.
Effect of changed duration on finish date and float.
Effect of a new relationship, lag, or constraint.
Basic earned value schedule indicators if data is provided.
Calendar or non-work-period adjustments when specified.
Milestone variance and forecast completion variance.

Scenario practice

Identify the best next action after a delayed activity.
Decide which artifact should be updated after a change.
Explain whether a delay affects project completion.
Determine whether to escalate a schedule risk.
Choose between recovery options based on path impact.
Explain why a schedule is technically weak.
Interpret conflicting stakeholder claims using evidence.
Write a short narrative for a late milestone.
Decide when baseline revision is appropriate.
Defend schedule integrity when asked to manipulate dates.

Exam-readiness self-test

You are close to ready when you can do the following consistently:

Explain every major planning and scheduling concept in plain language.
Solve CPM calculations accurately under time pressure.
Interpret schedule reports and identify what matters.
Diagnose schedule-quality problems from limited facts.
Connect scope, logic, duration, resources, cost, risk, and change.
Choose defensible next actions in judgment-based scenarios.
Avoid assuming facts not stated in the question.
Recognize when contract, governance, or stakeholder context changes the best response.
Support answers with schedule principles, not workplace habit.
Complete mixed practice with stable accuracy across all topic areas.

Practical next step

Mark each topic area Green, Yellow, or Red. Start with Red items that affect many questions: CPM logic, baseline/update control, progress measurement, change impact, and schedule-quality review. Then move into timed mixed practice so you can apply the checklist the way the AACE Planning & Scheduling Professional (PSP) exam is likely to test it: through calculations, artifacts, and practical project-controls judgment.

Study Plan

Scenario Guide