30 Questions — PMI – PMI-SP : Certified Scheduling Professional - Domain 1 - Schedule Strategy

Expand any question to reveal the correct answer and explanation.

1. 1 When defining the Schedule Management Plan (SMP) for a project with highly volatile requirements but a fixed contractual end date, which strategic approach allows the team to balance predictability with flexibility?

   Consider a method that combines near-term detail with long-term high-level placeholders.

   Implementing a rolling wave planning technique within a Critical Path Method framework.

   This technique allows for detailed planning of near-term work while maintaining a high-level summary of future work within a deterministic model to track the end date.

   • ✗ Adopting a purely agile scheduling approach to prioritize the backlog daily.

     While agile provides flexibility, it may struggle to provide the deterministic end-date predictability often required by fixed contractual milestones.

   • ✗ Utilizing a strict deterministic model with detailed activity granularity for the entire project duration.

     High volatility makes long-term detailed planning inaccurate and leads to excessive administrative burden for constant re-baselining.

   • ✗ Selecting a probabilistic Monte Carlo simulation as the primary method for daily task management.

     Monte Carlo is a risk analysis tool used for forecasting, not a tactical execution framework for daily task prioritization.

2. 2 A scheduler is establishing configuration management policies for a global project team. Which element is most critical for ensuring business continuity in the event of a catastrophic data failure?

   Focus on the procedural steps required after a backup has been created.

   The documented retrieval procedure for previous schedule instances.

   Performing backups is insufficient if the team lacks a verified, accurate procedure to retrieve and restore that data during a failure.

   • ✗ The selection of a high-end scheduling software tool.

     The software tool provides the environment, but does not inherently manage the procedural aspects of data recovery and continuity.

   • ✗ The frequency of performance threshold reporting.

     Reporting frequency relates to monitoring performance, whereas business continuity focuses on data preservation and recovery.

   • ✗ The assignment of read-only access to executive stakeholders.

     Access rights manage security and data integrity but do not address the recovery of lost information after a system crash.

3. 3 During the development of the Schedule Data Management Plan, the team identifies that distributed users in multiple time zones require varying access rights. What is the primary strategic concern here?

   Think about the intersection of system downtime and the global workday.

   Conflicts between infrastructure maintenance windows and global user accessibility.

   Maintenance like patches or upgrades can lock out users in other time zones who are in their active working hours, impacting data entry.

   • ✗ The determination of the project's critical path logic.

     Time zone access is an infrastructure and data management issue, not a logical sequencing or network analysis problem.

   • ✗ Setting the variance thresholds for the Schedule Performance Index.

     Thresholds are part of the monitoring strategy, while time zone accessibility is a data governance and configuration issue.

   • ✗ Defining the activity granularity for the Work Breakdown Structure.

     Granularity is a modeling choice regarding work packages, whereas time zone access relates to system administration and availability.

4. 4 When is a probabilistic scheduling approach strategically superior to a deterministic approach?

   Consider how the model handles the 'randomness' of task length.

   When activity durations are random variables with significant inherent uncertainty.

   Probabilistic models account for variability by using random variables and distributions rather than static, single-point estimates.

   • ✗ When the project team requires a simple visual Gantt chart for a short-term project.

     Deterministic models are typically simpler and more efficient for projects with low complexity and clear task durations.

   • ✗ When the primary goal is to identify the specific finish-to-start dependencies between two tasks.

     Logic dependencies are present in both models; the distinction lies in how duration and risk are handled, not the relationship types.

   • ✗ When the scheduler needs to define the Resource Breakdown Structure.

     Resource breakdown is a structural requirement for both approaches and does not dictate the choice between deterministic and probabilistic modeling.

5. 5 An organization is deciding on a scheduling tool. Why is this considered a strategic decision in Domain 1 rather than a simple procurement task?

   Think about how software features can constrain or enable certain management techniques.

   The tool often dictates the inherent scheduling methodologies and rules available to the team.

   Specific software tools have built-in logic and constraints that facilitate or limit certain approaches like CPM, PERT, or Agile.

   • ✗ The tool determines the actual start and finish dates for project activities.

     The tool processes data, but the project team provides the inputs that ultimately determine the specific dates.

   • ✗ Tool selection is the only way to establish the project's Work Breakdown Structure.

     The WBS is a scope management deliverable that can be created independently of any specific scheduling software.

   • ✗ The tool automatically generates the Schedule Management Plan without human intervention.

     The SMP is a strategic document created by the project team; the tool is merely an instrument to implement that plan.

6. 6 The Schedule Management Plan includes 'Performance Thresholds.' What is the strategic purpose of these thresholds?

   Focus on how management knows when to step in when the schedule slips.

   To define the alarm boundaries that trigger variance analysis and corrective actions.

   Thresholds prevent over-management by establishing when a deviation is significant enough to require a formal response.

   • ✗ To calculate the total float available for non-critical activities.

     Total float is calculated through network analysis (forward/backward pass) rather than being a predefined strategic threshold.

   • ✗ To establish the mandatory sequence of work for the project team.

     Sequencing is determined by logical dependencies and constraints, not by performance management thresholds.

   • ✗ To determine the number of resources assigned to each activity.

     Resource assignment is a function of resource planning and development, not a threshold for monitoring performance.

7. 7 In the context of Domain 1, what is the 'Schedule Model' as opposed to the 'Project Schedule'?

   Differentiate between the engine that creates the forecast and the forecast itself.

   The dynamic representation of the project's logic, activities, and resources used to generate dates.

   The model is the tool and data structure that reacts to inputs, while the project schedule is a specific output or 'instance' of that model.

   • ✗ A static document that lists only the project milestones and deliverables.

     This describes a milestone list or a high-level report, not the functional, dynamic engine of a schedule model.

   • ✗ The final approved baseline that cannot be changed during project execution.

     While the model contains the baseline, the model itself remains dynamic to reflect actual progress and changes.

   • ✗ The software application (e.g., Primavera P6) used by the scheduling professional.

     The software is the 'scheduling tool'; the 'schedule model' is the project-specific data and logic built within that tool.

8. 8 Which factor is most likely to lead to an 'inefficient' schedule model that results in increased project duration and risk?

   Consider the document that provides the 'execution strategy and objectives' for the scheduler.

   A lack of a formal Schedule Management Plan.

   Without a plan, the team lacks a consistent methodology, leading to inconsistent performance and uncoordinated updates.

   • ✗ The use of a deterministic rather than a probabilistic approach.

     Deterministic models are efficient for many projects; their use does not inherently cause inefficiency unless misapplied to high-risk scenarios.

   • ✗ Setting activity granularity to approximately 80 hours of work.

     Moderate granularity is a standard practice; inefficiency usually stems from lack of coordination, not standard work package sizing.

   • ✗ Selecting a software tool that is commonly used in the industry.

     Industry-standard tools generally improve efficiency by providing familiar interfaces and robust support.

9. 9 Establishing 'Activity Granularity' is a key task in Domain 1. What is the risk of excessive granularity (too much detail) in a schedule model?

   Think about the effort required to update thousands of tiny tasks.

   It creates a massive administrative burden that can obscure critical path visibility.

   Too many activities make the model difficult to maintain and can hide the 'big picture' of project progress.

   • ✗ It prevents the use of Earned Value Management calculations.

     EVM can be applied to very detailed schedules; the risk is the effort required to gather status, not the mathematical impossibility.

   • ✗ It eliminates the need for a Resource Breakdown Structure.

     Resources are still needed regardless of task size; granularity does not change the need to understand resource organization.

   • ✗ It forces the team to use a probabilistic scheduling approach.

     Granularity is independent of the choice between deterministic and probabilistic methods.

10. 10 When developing a schedule strategy for a project involving several subcontractors, what should the scheduler prioritize to ensure integrated control?

    Consider how different models from different sources can be successfully merged.

    Standardizing the scheduling methodology and tool across all project participants.

    Consistency in tools and methods allows for easier merging of sub-projects and accurate enterprise-level reporting.

    • ✗ Allowing each subcontractor to define their own independent performance thresholds.

      Independent thresholds make it impossible for the project manager to have a unified view of overall project health.

    • ✗ Eliminating all cross-project dependencies to simplify the model.

      Removing dependencies ignores reality and prevents the model from accurately forecasting the impact of delays.

    • ✗ Focusing exclusively on the subcontractor with the largest financial contract.

      A critical path can run through a small subcontractor's tasks; all logic must be captured regardless of contract size.

11. 11 The Schedule Management Plan should align with 'Organizational Process Assets' (OPAs). Which of the following is an example of an OPA that influences schedule strategy?

    Look for something that is an internal, reusable organizational resource or standard.

    A corporate template for a progress reporting dashboard.

    Standardized templates and procedures are classic assets provided by the organization to ensure consistency across projects.

    • ✗ The current market interest rate for project financing.

      Interest rates are Enterprise Environmental Factors (EEFs) because they are external conditions that influence the project but aren't internal assets.

    • ✗ The specific availability of a key cybersecurity expert.

      Specific resource availability is a project-level constraint handled during planning and development, not a high-level process asset.

    • ✗ The geographical location of the project's primary construction site.

      Site location is a fixed environmental factor (EEF) and not a process, template, or organizational procedure.

12. 12 Why is 'Schedule Data Management' considered a subset of 'Schedule Strategy'?

    Think about the difference between a management philosophy and the IT rules for the files.

    It addresses the technical infrastructure, such as versioning and storage, that supports the management approach.

    Data management is the 'how-to' of handling the digital files and information that the broader schedule strategy relies on.

    • ✗ It is the process of assigning resources to the critical path activities.

      Resource assignment is part of Schedule Planning and Development, not the strategic data governance layer.

    • ✗ It determines the contractual end date that the project team must meet.

      The end date is determined by project scope, logic, and stakeholder requirements, not by data storage policies.

    • ✗ It replaces the need for a Schedule Management Plan (SMP) in small projects.

      Data management and the SMP serve different purposes; even small projects need a management approach and data security.

13. 13 What is the primary objective of a 'formula brain dump' on a scratch sheet before starting a scheduling exam?

    Focus on the psychological and mechanical benefits of having a reference guide ready.

    To ensure accurate calculations under time pressure without relying on memory recall.

    Writing formulas like SV, SPI, and PERT early prevents errors caused by stress or fatigue later in the exam.

    • ✗ To identify which questions are unscored pretest items.

      Brain dumps help with math, but there is no formula or method to identify which questions are unscored validation items.

    • ✗ To determine the passing score of the examination.

      PMI uses scaled scoring and does not publish fixed passing scores; a scratch sheet cannot reveal this information.

    • ✗ To calculate the total float of every activity in the provided scenarios.

      Network calculations are done question-by-question; the brain dump is for the general formulas themselves.

14. 14 When establishing scheduling policies, the scheduler must determine 'Activity Granularity.' What is the strategic guideline for this in a well-managed project?

    Think about the 'Goldilocks' principle—not too much, not too little.

    The level of detail should be sufficient to allow for effective reporting and control without being overwhelming.

    Strategy involves balancing the need for control with the practical limits of maintaining the schedule model.

    • ✗ Every activity should be broken down into units of no more than one hour of work.

      One-hour granularity is extreme and would create an unmanageable number of activities for most projects.

    • ✗ The granularity should be identical for all projects within the organizational portfolio.

      Granularity should be tailored to the specific complexity and duration of each individual project.

    • ✗ Only the critical path activities should be broken down into detailed work packages.

      All parts of the project scope must be decomposed to ensure they are tracked, even if they aren't on the critical path.

15. 15 A scheduler is choosing between using a 'deterministic' or 'probabilistic' model. If the project has a very high confidence level in all task durations, which is the most appropriate strategic choice?

    Focus on the method that assumes a 'static' duration for activities.

    A deterministic schedule model using the Critical Path Method.

    If variability is negligible, the simplicity and clarity of a deterministic CPM model provide the most effective management tool.

    • ✗ A probabilistic model using a Beta-PERT distribution for every task.

      Probabilistic models are designed for uncertainty; using them when confidence is high adds unnecessary complexity without adding value.

    • ✗ A Monte Carlo simulation based on 10,000 iterations.

      Simulations are used to assess risk boundaries; they are not a day-to-day tactical execution model for stable projects.

    • ✗ An agile scheduling approach with daily stand-up meetings.

      The choice between CPM and Agile depends on scope clarity and delivery style, not just duration confidence.

16. 16 What is the strategic significance of the 'Schedule Conformance Index (SCI)' during the development of schedule policies?

    Think of this as a 'health check' for the schedule's logic.

    It provides a benchmark to audit the quality and integrity of the schedule model.

    The SCI helps ensure that the model follows best practices, such as avoiding open-ended tasks and excessive constraints.

    • ✗ It calculates the total budget required for the project.

      Budget is a cost management function; the SCI focuses on the structural health of the schedule logic.

    • ✗ It determines the specific order of activities in the project network.

      The sequence is determined by logical dependencies; the SCI audits the *quality* of how those dependencies are recorded.

    • ✗ It acts as a substitute for the project's performance measurement baseline.

      The SCI is a quality auditing tool, not a performance baseline for tracking progress against goals.

17. 17 In the 'Schedule Strategy' domain, why must the scheduler evaluate 'Enterprise Environmental Factors' (EEFs)?

    Consider things that are outside the project but still 'press in' on how it's planned.

    To identify external constraints like regulations or market conditions that limit scheduling options.

    EEFs are conditions not under the immediate control of the project team that influence the schedule approach.

    • ✗ To select the specific team members who will perform the work.

      Staffing is a resource management task that occurs later in the planning and development phase.

    • ✗ To create the project's Work Breakdown Structure from scratch.

      The WBS is based on project scope; while EEFs might influence *how* it's built, they aren't the primary source of its content.

    • ✗ To bypass the need for a configuration management policy.

      Environmental factors usually *require* stricter policies rather than eliminating the need for them.

18. 18 Which of the following is a key component of a 'Schedule Data Management Plan'?

    Focus on the 'IT' and security aspects of project scheduling information.

    The frequency and method for backing up schedule data.

    Data management focuses on the infrastructure and security of the information, including its preservation through backups.

    • ✗ The calculation of total and free float for non-critical activities.

      Float calculation is a technical output of the network analysis, not a data storage or infrastructure policy.

    • ✗ The definition of the critical path for the baseline schedule.

      The critical path is a result of schedule planning and development, not a policy for how data files are stored.

    • ✗ The assignment of cost accounts to specific work packages.

      Cost accounts are part of the integration between schedule and budget, not part of the data management infrastructure.

19. 19 How does the scheduler facilitate 'effective participation' by project team members during Domain 1?

    Think about the importance of 'buy-in' and understanding the scheduling process.

    By providing clear information about scheduling objectives, roles, and procedures.

    Communicating the 'rules of the road' ensures that team members know what data to provide and when to provide it.

    • ✗ By performing all network calculations alone to save the team's time.

      Calculating alone does not foster participation; team members must be involved in providing inputs and understanding the outputs.

    • ✗ By allowing team members to change the baseline schedule whenever they fall behind.

      Baselines should only be changed through formal procedures; frequent informal changes undermine the project's integrity.

    • ✗ By ignoring risk data from team members to keep the schedule simple.

      Ignoring risk data leads to an unrealistic schedule and is the opposite of effective team participation.

20. 20 When defining the scheduling approach, what is the significance of the 'Basis of Estimate'?

    Think of this as the 'footnotes' that explain how a task's duration was calculated.

    It documents the logic, data sources, and assumptions used to derive duration and cost estimates.

    The basis of estimate provides the transparency needed to defend and adjust the schedule as project conditions change.

    • ✗ It is the final list of dates produced by the scheduling software.

      The list of dates is the 'schedule'; the basis of estimate is the underlying reasoning *for* those dates.

    • ✗ It is a mandatory legal contract between the project manager and the sponsor.

      The basis of estimate is a project document, not necessarily a formal legal contract, although it may support one.

    • ✗ It determines the exact number of iterations required for a Monte Carlo simulation.

      Iteration count is a statistical decision based on desired confidence, not the justification for individual task lengths.

21. 21 A scheduler is establishing a policy for Earned Value Management (EVM). Which Domain 1 activity is most critical for successful EVM implementation?

    Consider the 'integration' aspect of schedule, scope, and cost.

    Defining the alignment between the schedule model and the cost management plan.

    EVM requires integrated data between schedule progress and actual costs, which must be strategically planned before execution.

    • ✗ Assigning specific logic relationships like Start-to-Finish to every task.

      Relationship types are tactical modeling choices and do not inherently dictate whether EVM can be implemented successfully.

    • ✗ Conducting a forensic delay analysis on a completed sub-project.

      Forensics is a closeout or historical analysis activity, while EVM setup is a forward-looking planning task.

    • ✗ Updating the project calendar to include all international holidays.

      Calendars are important for date calculation, but the integration with cost accounts is the core strategic requirement for EVM.

22. 22 Which scheduling technique assumes that detailed information is available for near-term work but only high-level information for future work?

    Think of a 'wave' that gets closer as time moves forward.

    Rolling Wave Planning

    This iterative approach avoids premature detail by planning in waves as accurate information becomes available.

    • ✗ Critical Path Method

      CPM is a method for calculating end dates based on logic; it doesn't inherently dictate the timing of detail added to the model.

    • ✗ Monte Carlo Simulation

      This is a statistical simulation technique for risk analysis, not a decomposition or planning technique.

    • ✗ Resource Leveling

      Leveling is a technique used to resolve resource over-allocations by shifting dates, not a way to manage planning detail.

23. 23 The PERT (Program Evaluation and Review Technique) expected duration formula $(\mu = \frac{O + 4M + P}{6})$ is a form of:

    The formula uses three points to find a single 'weighted' average.

    Probabilistic scheduling based on a weighted Beta distribution.

    PERT uses three-point estimation to account for uncertainty and weights the most likely outcome more heavily.

    • ✗ Deterministic scheduling using a standard single-point estimate.

      Deterministic models use a single 'most likely' duration without accounting for optimistic or pessimistic ranges.

    • ✗ Resource smoothing to minimize daily workforce fluctuations.

      Resource smoothing is an optimization technique and doesn't involve duration estimation formulas like PERT.

    • ✗ Earned Schedule management for calculating time-based variances.

      Earned Schedule is used for performance monitoring, whereas PERT is used for duration estimation during planning.

24. 24 Why would a scheduler choose a 'Critical Chain' approach over the 'Critical Path Method' at the strategic level?

    Think about the 'chain' of both logic and resources.

    To focus on resource constraints and the use of aggregated buffers to manage risk.

    Critical Chain accounts for both logic and resource availability while using buffers to protect the end date.

    • ✗ To eliminate the need for any logic relationships between activities.

      All professional scheduling methods require logic; Critical Chain simply adds resource constraints to that logic.

    • ✗ To allow every team member to set their own project finish dates.

      Scheduling is a centralized management function; allowing individuals to set independent end dates would lead to chaos.

    • ✗ To reduce the amount of time spent on project communication.

      Critical Chain often requires *more* communication regarding buffer consumption and resource status.

25. 25 Which of the following is a primary goal of a 'Schedule Management Plan' regarding risk management?

    Consider the relationship between the 'Risk Register' and the 'Schedule Model'.

    To define how project risks will be captured and reflected in the schedule model.

    The SMP should provide the strategy for integrating risk data, such as mitigation tasks or contingency buffers, into the schedule.

    • ✗ To guarantee that no delays will occur during the project lifecycle.

      No plan can guarantee zero delays; the plan's goal is to manage the *response* to delays and uncertainty.

    • ✗ To identify every specific risk event that could possibly occur.

      Risk identification happens during the Risk Management process; the SMP defines the *how* of reflecting those risks in the schedule.

    • ✗ To assign financial responsibility for all schedule-related claims.

      Claims and financial liability are typically legal and procurement matters, not part of the functional schedule management approach.

26. 26 When defining 'Activity Granularity,' what is the most important factor to consider to ensure the model remains 'dynamic'?

    Think about the 'feedback loop' of progress reporting.

    The ability of the team to provide accurate and timely progress updates at that level.

    A model only remains dynamic if it is updated frequently; excessive detail that can't be updated makes the model static and useless.

    • ✗ The total number of colors used in the Gantt chart visualization.

      Visualization style is a reporting choice and does not impact the dynamic functionality of the underlying schedule model.

    • ✗ The price of the scheduling software per user license.

      Cost is a procurement factor, not a technical factor influencing how 'dynamic' a schedule's logic remains.

    • ✗ The number of sub-projects that can be merged into a single database.

      Database capacity is a technical infrastructure issue, not a choice about individual task detail levels.

27. 27 A senior practitioner is creating a Schedule Strategy for a project with multiple interdependent sub-projects managed by different entities. Which strategic task is most vital for success?

    Consider the term 'Integrated Master Schedule' (IMS).

    Establishing integrated master scheduling policies and inter-project dependency logic.

    Integrated master scheduling allows for visibility across all entities and ensures the overall end date is realistic.

    • ✗ Forcing all sub-projects to use the exact same resource names for every task.

      While standardization helps, the logic dependencies between sub-projects are the primary driver of schedule integrity.

    • ✗ Creating a separate schedule management plan for every single sub-project.

      Too many disparate plans lead to inconsistency; an overarching integrated plan is more effective for complex programs.

    • ✗ Ignoring the sub-projects until the main project is at least 50% complete.

      Dependencies exist from day one; ignoring them is a strategic failure that leads to unforeseen delays.

28. 28 Which of the following describes the relationship between the 'Schedule Management Plan' (SMP) and the 'Communication Management Plan'?

    Think about how technical data is 'packaged' for different audiences.

    The SMP defines the technical schedule data to be shared, while the Communication Plan defines the target audiences and delivery methods.

    The two plans must work together to ensure that the right scheduling information reaches the right stakeholders at the right time.

    • ✗ The SMP is a minor appendix to the much larger Communication Management Plan.

      The SMP is a primary management plan in its own right, critical for defining the technical baseline and strategy.

    • ✗ The Communication Management Plan replaces the need for an SMP in most projects.

      Communication plans manage *how* people talk; the SMP manages *what* work is done and *when*.

    • ✗ There is no relationship between these two plans as they cover completely different domains.

      The plans are highly integrated, as schedule reporting is one of the most frequent forms of project communication.

29. 29 Establishing 'Schedule Configuration Management' policies primarily ensures that:

    Focus on 'version control' and 'data integrity'.

    Schedule data is accessible, stored, and retrieved in a consistent and controlled manner.

    Configuration management is about the integrity and control of the data files and versions over the project lifecycle.

    • ✗ The project will be completed with zero total float on the critical path.

      Float is an output of logic; configuration management is about the control of the files containing that logic.

    • ✗ Team members are allowed to delete activities whenever they are finished.

      Activities should be marked complete, not deleted, to maintain a historical record and audit trail.

    • ✗ The cost of the project is always kept within 5% of the original budget.

      Configuration management is a data integrity function, not a financial control or cost-saving measure.

30. 30 What is the strategic advantage of performing a 'what-if analysis' during the development of a schedule strategy?

    Think about 'scenario planning'.

    It allows the team to predict how the schedule model will react to different risk scenarios or changes.

    What-if analysis helps the team understand the sensitivity of the schedule to various inputs and potential roadblocks.

    • ✗ It eliminates all project risks by proving they will never happen.

      Analysis identifies the impact of risks; it cannot delete the risks themselves from reality.

    • ✗ It automatically adjusts the project's contractual end date in the project charter.

      charter dates are changed by sponsors through formal governance, not by a scheduler running a 'what-if' simulation.

    • ✗ It is the only way to calculate the critical path for a project.

      The critical path is found via standard CPM analysis; what-if analysis is an optional exploratory tool.