30 Questions — PMI – PMI-SP : Certified Scheduling Professional - Domain 5 - Stakeholder Communications Management

Expand any question to reveal the correct answer and explanation.

1. 1 A senior executive requires a report that summarizes an entire multi-year project in a single line to facilitate a quick comparison against other projects within a corporate portfolio. Which schedule level is most appropriate for this specific stakeholder tier?

   Consider the level specifically described as a single-line project summary for senior management.

   Level 0

   Level 0 is specifically defined as a project summary representing the entire project in one line, making it the standard for high-level portfolio comparisons.

   • ✗ Level 1

     Level 1 provides an executive summary that typically includes major contractual milestones and summary activities, which exceeds the single-line requirement.

   • ✗ Level 2

     Level 2 is designed for management summaries and focuses on interfaces between key deliverables rather than single-line comparative overviews.

   • ✗ Level 3

     Level 3 serves as a publication schedule for monthly reporting and contains detail unsuitable for a high-level portfolio overview.

2. 2 During a high-pressure steering committee meeting, a scheduler is asked why a project is behind schedule. The calculated Schedule Performance Index ($SPI$) is $0.82$. How should the scheduler interpret this metric to stakeholders?

   Recall the formula $SPI = \frac{EV}{PV}$ and what a value less than $1.0$ implies about the rate of progress.

   The project is executing work at approximately $82\%$ of the planned rate.

   An $SPI$ of $0.82$ indicates that for every hour of work planned, only $0.82$ hours of earned value have been achieved, reflecting the temporal efficiency.

   • ✗ The project has overspent its budget by approximately $18\%$.

     The $SPI$ measures schedule efficiency relative to time, whereas cost efficiency is measured by the Cost Performance Index ($CPI$).

   • ✗ The project is $18$ days behind the current critical path baseline.

     The $SPI$ is a ratio of efficiency, not a direct count of calendar days, which would be reflected in variance metrics or critical path analysis.

   • ✗ The project has a $18\%$ probability of missing the final delivery date.

     Predicting the probability of completion dates requires quantitative risk analysis, such as Monte Carlo simulation, rather than a point-in-time $SPI$ calculation.

3. 3 A scheduler must design a dashboard for a technical team lead who manages daily field activities with durations of less than one week. Which schedule level provides the necessary granularity for this recipient?

   Focus on the level characterized by working schedules that support resource allocation for tasks under one week.

   Level 5

   Level 5 is intended for detailed planning of daily or weekly tasks, typically formatted as activity lists to support short-term field execution.

   • ✗ Level 4

     Level 4 focuses on execution planning at the work package level for activities generally exceeding one week in duration.

   • ✗ Level 3

     Level 3 is a publication schedule used for monthly reporting of major elements and lacks the daily task detail required by field leads.

   • ✗ Level 2

     Level 2 provides management-level summaries of integration and interfaces, which is too broad for daily field supervision.

4. 4 A project sponsor demands a visual representation of schedule performance that shows the relationship between planned value ($PV$), earned value ($EV$), and actual costs ($AC$) over time. Which reporting tool best facilitates this communication?

   Think of a graphic that plots cumulative progress and expenditure to show divergence from the baseline.

   S-Curve

   The S-curve is the standard Earned Value Analysis visualization tool that plots cumulative data points to reveal trends in cost and schedule performance.

   • ✗ Gantt Chart

     While effective for showing timing and progress bars, a standard Gantt chart does not typically integrate the three core EVM cost components.

   • ✗ Resource Histogram

     A resource histogram is used to visualize resource demand and overallocation rather than integrated performance metrics.

   • ✗ Activity Network Diagram

     Network diagrams are utilized to display logical dependencies and critical paths rather than cumulative performance values.

5. 5 When presenting a recovery plan for a delayed project, the scheduler suggests 'Crashing' the critical path. What is the most critical trade-off that must be communicated to stakeholders regarding this strategy?

   Differentiate between the impact of adding resources versus the impact of overlapping tasks.

   Shortened duration typically results in increased project costs.

   Crashing involves injecting additional resources into critical tasks, which accelerates the timeline but increases the financial expenditure.

   • ✗ Parallel activity execution increases the risk of rework.

     Increasing the risk of rework through parallel tasks is the primary disadvantage of fast-tracking, not crashing.

   • ✗ The project scope must be reduced to meet the new deadline.

     Schedule compression techniques like crashing aim to shorten the duration without necessarily altering the project scope.

   • ✗ Total float across all non-critical activities will increase.

     Crashing focus on critical activities; it does not inherently increase float for non-critical tasks and may actually create new critical paths.

6. 6 A project is midway through execution when a senior stakeholder demands that a major milestone be completed 10 days earlier. The scheduler calculates an Estimate at Completion for time ($EAC_{t}$) using the current $SPI$. What is the primary purpose of presenting this extrapolation to the stakeholder?

   Consider how a forecast based on poor current performance ($SPI < 1.0$) would influence a request for faster delivery.

   To demonstrate that current performance trends are moving away from the requested acceleration.

   Extrapolating $EAC_{t}$ provides a data-driven reality check, showing that current inefficiencies make the new demand even more difficult to achieve without intervention.

   • ✗ To prove that the project is currently ahead of schedule and can absorb the change.

     Calculating $EAC_{t}$ with a low $SPI$ typically reveals a later delivery date, serving as a warning rather than proof of capacity.

   • ✗ To establish a new Performance Measurement Baseline immediately.

     An extrapolation is a forecast used for decision-making; it does not automatically re-baseline the project, which requires formal change control.

   • ✗ To identify which specific resources are causing the delay.

     While $EAC_{t}$ identifies a trend, it is a high-level metric that does not pinpoint specific resource-level causes of variance.

7. 7 In the context of the PMI-SP standard, what is the fundamental distinction between the 'Schedule Model' and the 'Schedule Presentation'?

   One is the dynamic 'engine' or database; the other is a specific 'view' of that data.

   The model is a dynamic database, while the presentation is a static extraction or report.

   The schedule model acts as the engine containing logic and data, whereas presentations (like Gantt charts) are filtered outputs for communication.

   • ✗ The model is used by the project manager, while the presentation is for the team.

     Both stakeholders use both tools, but the distinction lies in the structural nature of the database versus the visual artifact.

   • ✗ The model contains costs, whereas the presentation only contains dates.

     Both the model and presentations can include cost, resource, and date information depending on the configuration and report type.

   • ✗ The model is developed in the planning phase, while presentations are created during monitoring.

     Presentations are generated throughout the lifecycle from the model to communicate planning, status, and forecasts.

8. 8 A scheduler is preparing a monthly publication report for a project manager. According to recommended practices, which level of detail should this report typically provide?

   Recall which level is specifically linked to the monthly publication of major engineering and construction elements.

   Level 3

   Level 3 is defined as the publication schedule level used to support monthly reports, showing major milestones and elements like procurement and engineering.

   • ✗ Level 0

     Level 0 is too high-level for monthly reporting as it reduces the entire project to a single line.

   • ✗ Level 5

     Level 5 is too detailed for monthly management reports, as it focuses on daily or hourly tasks for field supervisors.

   • ✗ Level 1

     Level 1 provides an executive summary that lacks the multi-page detail of engineering and procurement elements found in Level 3.

9. 9 A project is facing significant uncertainty due to volatile weather conditions. When communicating the probability of meeting the project's finish date to the client, which approach is considered best practice?

   Consider the communication technique that uses statistical data to manage expectations in high-uncertainty scenarios.

   Using probabilistic language based on Monte Carlo simulation results.

   Probabilistic language accurately reflects risk by providing ranges and confidence levels rather than misleadingly precise deterministic dates.

   • ✗ Providing a single, deterministic date to instill confidence in the schedule.

     Deterministic dates in high-risk environments are often brittle and can damage stakeholder trust when the inevitable delays occur.

   • ✗ Presenting only the Early Finish date without factoring in risk buffers.

     Focusing on the Early Finish date ignores the impact of uncertainty and potential critical path shifts.

   • ✗ Stating that the project will definitely be on time as long as no more risks occur.

     This approach ignores the reality of ongoing project risk and fails to provide stakeholders with actionable data for contingency planning.

10. 10 During a status review, the scheduler notes a Schedule Variance ($SV$) of $-\$50,000$. Which of the following is the most accurate narrative for the project team?

    Identify the relationship between Earned Value ($EV$) and Planned Value ($PV$) when the variance result is negative.

    The value of work completed is less than the value of work planned for this period.

    A negative $SV$ (derived from $EV - PV$) signifies that the project has achieved less 'earned value' than what was baselined in the 'planned value' for the period.

    • ✗ The project has incurred costs that are $\$50,000$ higher than the earned value.

      This narrative describes Cost Variance ($CV$), which compares $EV$ to $AC$ rather than $PV$.

    • ✗ The project is over budget by approximately $\$50,000$ for the current phase.

      Schedule variance is expressed in monetary terms but represents a time deficiency, not a direct budgetary overage.

    • ✗ The total float on the critical path has been reduced by 50 days.

      While a negative $SV$ indicates a delay, it is a monetary representation of earned work and does not translate linearly to a specific number of float days.

11. 11 A scheduler is tasked with developing a communication management plan. Which element is essential for ensuring that schedule reports drive effective decision-making across different stakeholder tiers?

    Think about how reporting needs vary between an executive board and a field supervisor.

    Definition of reporting cadences and target visualization tools for each tier.

    Tailoring the frequency and visual format (e.g., Gantt vs. Milestone charts) ensures that each stakeholder level receives relevant, actionable data.

    • ✗ Standardization of Level 5 detail for all reports to ensure maximum transparency.

      Providing Level 5 detail to executives would lead to information overload and likely hinder rather than help decision-making.

    • ✗ Exclusive use of numerical tables to avoid misinterpretation of graphical artifacts.

      Graphical presentations are critical for visualizing trends and logical sequences that are difficult to grasp from tables alone.

    • ✗ The requirement that all stakeholders access the raw Schedule Model database directly.

      Stakeholders generally require processed 'presentations' rather than raw database access, which requires specialized scheduling expertise.

12. 12 When presenting a delay analysis to a client, the scheduler uses the Schedule Conformance Index ($SCI$). What is the primary message conveyed by a low $SCI$ score?

    The index evaluates the 'health' and quality of the schedule model itself, regardless of whether the project is early or late.

    The schedule model lacks the structural integrity required for reliable forecasting.

    A low $SCI$ indicates the schedule model does not adhere to quality standards (e.g., too many open ends or invalid logic), making its outputs untrustworthy.

    • ✗ The project is significantly behind its baselined finish date.

      The $SCI$ measures model quality and conformance to standards, not the actual temporal status of project progress.

    • ✗ The resources assigned to the project are inefficient or under-qualified.

      Resource efficiency is typically measured by productivity rates or $CPI$, whereas $SCI$ focuses on the scheduling database's health.

    • ✗ The project budget is insufficient to cover the remaining work scope.

      Budget sufficiency is a financial planning concern, while $SCI$ evaluates the logic and mechanics of the schedule model.

13. 13 A scheduler needs to foster stakeholder alignment regarding a proposed schedule re-baseline. Which step is most effective for building consensus among skeptical sponsors?

    Think about the importance of transparency regarding the root causes of major project deviations.

    Documenting and agreeing upon the specific drivers and impacts necessitated by the re-baseline.

    Clearly explaining the root causes (e.g., major scope changes or disasters) and their consequences helps stakeholders understand why the original baseline is no longer valid.

    • ✗ Silently updating the model and only presenting the new completion dates.

      Lack of transparency in re-baselining can destroy stakeholder trust and lead to future resistance regarding schedule metrics.

    • ✗ Increasing the detail of the Level 5 tasks to demonstrate the complexity of work.

      While detail is important for execution, it does not address the high-level 'why' behind a baseline change for sponsors.

    • ✗ Eliminating all risk buffers to show a more aggressive and desirable finish date.

      Artificially removing buffers creates an unrealistic plan that will likely fail, further damaging professional credibility.

14. 14 An executive stakeholder group asks for a report to monitor the integration of work between various major contractors and architects. Which schedule level should be used as the basis for this report?

    Identify the level described as communicating work integration across the project lifecycle, often spanning 4-5 pages.

    Level 2

    Level 2 (Management Summary) is specifically intended to communicate the integration of work and interfaces between contractors, consultants, and architects.

    • ✗ Level 0

      Level 0 lacks the interface and deliverable detail necessary to show integration between different project participants.

    • ✗ Level 5

      Level 5 is granular at the task level and would obscure the high-level interfaces between organizational entities.

    • ✗ Level 4

      Level 4 focuses on multidiscipline coordination within work packages rather than the broad integration of major contracting parties.

15. 15 In a high-pressure scenario where a project is behind schedule ($SPI = 0.78$), the scheduler is tasked with 'Re-sequencing deliverables.' How should this action be explained in a stakeholder memo?

    Focus on the logic of how tasks are ordered rather than the speed or resources applied.

    As a strategy to optimize workflow by triaging and recalibrating task order.

    Re-sequencing involves logically rearranging work to improve flow or agility without necessarily adding resources or overlapping tasks.

    • ✗ As a plan to add additional overtime labor to key critical activities.

      Adding labor to critical tasks describes 'crashing,' which is distinct from changing the sequence of work.

    • ✗ As a decision to execute critical path tasks in parallel to shorten the timeline.

      Running critical path tasks in parallel describes 'fast-tracking,' which introduces different risks than standard re-sequencing.

    • ✗ As a method of removing low-priority requirements from the project scope.

      Removing requirements is a scope reduction technique, not a scheduling sequence adjustment.

16. 16 A scheduler is designing a dashboard and must decide whether to use a Milestone Chart or a Logic Network Diagram for a board of directors meeting. Why would the Milestone Chart be preferred for this audience?

    Think about the needs of a board-level audience for high-level visibility vs. technical detail.

    It simplifies high-level progress by focusing on significant events rather than complex task logic.

    Executives need to see the 'big picture' of key deliverables; the intricate logic of a network diagram is typically too granular and distracting for board-level reviews.

    • ✗ It provides a dynamic view that allows the board to perform 'what-if' simulations.

      A milestone chart is a static report; it does not allow for real-time simulation, which occurs within the Schedule Model.

    • ✗ It is the only tool that accurately depicts the project's critical path.

      Critical paths are best visualized in logic network diagrams or Gantt charts; milestone charts usually omit individual task dependencies.

    • ✗ It identifies resource over-allocations and provides leveling solutions.

      Resource-leveling analysis requires detail found in the schedule model and displayed in histograms, not milestone summaries.

17. 17 A scheduler uses the term 'Translator of Time' to describe their role in Domain 5. What does this metaphor imply regarding communication with non-technical stakeholders?

    Reflect on how a scheduler bridges the gap between raw data and stakeholder decision-making.

    Converting technical schedule constraints into narratives that stakeholders can trust and act upon.

    Effective scheduling communication requires making technical concepts (like float or lag) meaningful to those making business decisions.

    • ✗ Accurately converting work hours into financial expenditure data for the finance department.

      While cost-time integration is important, the 'translator' role specifically addresses the communication of schedule implications.

    • ✗ Ensuring the project schedule is available in multiple languages for global teams.

      The metaphor refers to translating technical complexity into strategic insight, not linguistic translation.

    • ✗ Using automated software to generate reports without human intervention.

      The role of a translator requires expert judgment and professional gravitas to shape the narrative, which software alone cannot provide.

18. 18 A scheduler is preparing a Level 4Execution Planning report for a construction team. What is the standard 'look-ahead' period typically supported by this level of granularity?

    Look for the specific timeframe mentioned for Level 4 look-ahead schedules.

    Three weeks

    The standard practice defined for Level 4 schedules is to support 3-week look-ahead reports for construction and commissioning planning.

    • ✗ One day

      A one-day look-ahead is the territory of Level 5 Detailed Planning, which deals with daily task requirements.

    • ✗ Six months

      Six months is more aligned with Level 2 Management Summaries or Level 1 Executive overviews of project stages.

    • ✗ One hour

      Hourly updates are typical for specialized Level 5 schedules in high-volatility environments like manufacturing outages.

19. 19 While managing stakeholder expectations during a project delay, a scheduler identifies a negative Schedule Variance ($SV$). Which recovery strategy involves running critical path tasks in parallel and increases the risk of rework?

    Differentiate between adding more power (resources) versus changing the order of execution (overlapping).

    Fast Tracking

    Fast tracking overlaps tasks that were originally planned in sequence, which accelerates the schedule but often results in rework if errors are caught late.

    • ✗ Crashing

      Crashing accelerates the schedule by adding resources, not by changing task overlap, and primarily impacts cost rather than rework risk.

    • ✗ Resource Leveling

      Resource leveling often extends the project duration to resolve over-allocations, which is the opposite of a compression recovery strategy.

    • ✗ Scope Compression

      This term is often used generally, but specific techniques are crashing or fast tracking; 'compression' by itself doesn't define the rework risk of parallel tasks.

20. 20 A scheduler is asked to provide a verbal update to senior management regarding a delay. Which approach reinforces 'Professional Gravitas' in this interaction?

    Consider how providing choices and trade-offs empowers stakeholders and builds trust.

    Presenting data-driven alternatives and choices rather than a single fixed answer.

    Offering stakeholders choices with explained trade-offs enhances their buy-in and demonstrates strategic analytical acumen.

    • ✗ Apologizing for the delay and promising it will not happen again without providing data.

      A purely emotional response without schedule analysis fails to provide management with the information needed to mitigate the impact.

    • ✗ Blaming the delay on a specific contractor to maintain the internal team's image.

      Effective stakeholder management focuses on solutions and transparent status reporting rather than assigning blame.

    • ✗ Stating that the schedule model is too complex for them to understand.

      It is the scheduler's professional duty to 'translate' complexity into actionable insights, not to withhold information based on complexity.

21. 21 What is the recommended communication cadence for a 'stable, long-term, low-risk project' as defined in the scheduling standards?

    Look for the interval suggested for projects that do not experience rapid rates of change.

    Monthly or bimonthly

    Standards suggest that for low-risk, stable projects, a longer interval like monthly or bimonthly is sufficient to provide control without being burdensome.

    • ✗ Hourly or every shift change

      Hourly updates are reserved for highly volatile, high-risk projects such as planned manufacturing outages.

    • ✗ Weekly stand-ups only

      While weekly updates are common, the standard specifically notes that monthly/bimonthly is appropriate for low-risk, stable endeavors.

    • ✗ Daily retrospectives

      Daily cadences are more typical of agile environments or high-pressure phases, not general low-risk long-term projects.

22. 22 Which specific report is described as a 'Management Summary' that reflects interfaces between contractors and architects, typically rolled up from more detailed data?

    Identify the level that sits between the executive summary and the monthly publication schedule.

    Level 2

    Level 2 is the management summary that communicates work integration and interface points across 4-5 pages.

    • ✗ Level 1

      Level 1 is a higher-level executive summary, usually one page, focusing on contractual milestones.

    • ✗ Level 3

      Level 3 is a publication schedule for monthly reports that includes more detailed elements of engineering and procurement.

    • ✗ Level 4

      Level 4 is for execution planning and coordinating multidiscipline/craft activities at the work package level.

23. 23 A scheduler wants to align stakeholder expectations regarding 'Time reserves on the critical path.' What term should be used in the narrative to describe these as proactive risk insurance?

    Focus on the term for time reserves used as a strategic response to probability analysis.

    Schedule Contingency

    Schedule contingency or buffers are insurance mechanisms woven into the timeline to manage known uncertainties on the critical path.

    • ✗ Free Float

      Free float refers to the amount an activity can be delayed without affecting a successor, which is different from a strategic risk-mitigation buffer.

    • ✗ Lag

      Lag is a directed delay in a relationship; it is a structural logic requirement rather than a contingency reserve for risk.

    • ✗ Inefficiency

      Buffers are explicitly described in the material as 'not inefficiencies' but as proactive insurance mechanisms.

24. 24 In a scenario involving 'Monte Carlo Simulation,' the results show only a $55\%$ probability of finishing by Day 90. How should the scheduler communicate this to a client demanding 'predictability'?

    Think about how a scheduler should act when a simulation reveals a low confidence level for a deadline.

    Frame the current finish date as high-risk and propose building in schedule contingency.

    A $55\%$ probability is low for predictability; framing it as a risk allows the scheduler to propose necessary contingency reserves.

    • ✗ Tell the client that the project is $55\%$ complete and on track.

      Probability of finish is a forecast of completion, while percent complete is a measure of historical work performance; mixing them is inaccurate.

    • ✗ Guarantee that the project will be finished on Day 90 since it is better than a coin flip.

      A $55\%$ probability does not provide the certainty clients need, and guaranteeing it would be professionally irresponsible.

    • ✗ Suggest that the statistical modeling is flawed and wait for more data.

      Ignoring quantitative data prevents proactive decision-making and fails to address the underlying risks driving the low probability.

25. 25 When extracting a targeted performance report for the finance department, which two metrics from the Schedule Model are most critical for validating the 'Schedule Performance Index'?

    Recall the two cost-based inputs used to measure temporal efficiency in Earned Value Management.

    Earned Value ($EV$) and Planned Value ($PV$)

    The $SPI$ is calculated specifically as $EV$ divided by $PV$, making these the two essential components for efficiency analysis.

    • ✗ Actual Cost ($AC$) and Earned Value ($EV$)

      The relationship between $AC$ and $EV$ defines cost performance ($CPI$), not schedule efficiency ($SPI$).

    • ✗ Free Float and Total Float

      While important for flexibility, float values are not components of the monetary $SPI$ calculation.

    • ✗ Early Finish and Late Finish

      These dates define float and the critical path but are not used in the standardized monetary calculation of $SPI$.

26. 26 A project manager wants to ensure stakeholders are prepared for 'necessary corrective actions.' Which interpersonal proficiency is highlighted as essential for this Domain 5 activity?

    Think about the 'soft skills' needed to persuade stakeholders to support difficult scheduling decisions.

    Emotional Intelligence and diplomacy in high-pressure situations.

    Managing stakeholder reactions to delays and proposed changes requires empathy, clarity, and an understanding of organizational priorities.

    • ✗ Expert-level proficiency in proprietary scheduling software code.

      Technical coding skills belong to Domain 2 (Planning); alignment with stakeholders requires interpersonal leadership skills.

    • ✗ The ability to memorize the 49 project management processes.

      Process memorization is helpful for general PMP knowledge but does not replace the interpersonal diplomacy needed for alignment.

    • ✗ A background in legal forensics for contract disputes.

      Forensic skills are useful for Domain 4 (Closeout), but Domain 5 focuses on proactive engagement and relationship-building.

27. 27 A scheduler is explaining the 'Schedule Level' concept to a new team member. Which level is described as a single-page report containing major contractual milestones?

    Focus on the level that serves as the 'Executive Summary' and fits on a single page.

    Level 1

    Level 1 is specifically defined as a summary-level executive report, usually limited to one page, focusing on contractual milestones.

    • ✗ Level 0

      Level 0 is a single-line summary, which is less detailed than a one-page milestone report.

    • ✗ Level 2

      Level 2 is a management summary, typically spanning four to five pages, making it too detailed for the Level 1 definition.

    • ✗ Level 3

      Level 3 is used for monthly reporting and includes elements of engineering and procurement beyond just contractual milestones.

28. 28 According to Domain 5 tasks, how should a scheduler communicate schedule issues that could impact delivery of project scope?

    Reflect on the proactive nature of 'Stakeholder Communications Management' in managing project risk.

    Elevate awareness to relevant stakeholders in a timely manner.

    Domain 5, Task 5.2 (and others) emphasizes the scheduler's responsibility to proactively raise visibility of risks and issues to the right audience.

    • ✗ Wait until the monthly publication schedule is due for distribution.

      Waiting for a monthly cycle can lead to missed opportunities for mitigation; timely elevation is required by professional standards.

    • ✗ Adjust the model logic so that the delay is not visible in the Gantt chart.

      Manipulating logic to hide delays is an unethical practice that undermines the integrity of the schedule and professional certification.

    • ✗ Only report the issue if the project manager specifically requests it.

      The scheduler has a professional obligation to maintain schedule visibility and foster relationships that support schedule collaboration.

29. 29 What is the primary visual difference between a 'Schedule Presentation' for an executive and one for a work package manager?

    Consider the core concept of 'Schedule Levels' and how they are applied to different recipients.

    Granularity: high-level milestones for executives versus task-specific layouts for managers.

    Targeted reporting extracts tailored views (Levels 1-2 vs. Levels 4-5) to meet the specific information needs of different stakeholder tiers.

    • ✗ Color: executive reports must be in color, while team reports are in black and white.

      While visual design is important, the fundamental difference defined in the standard is the level of detail or granularity.

    • ✗ Software: executives use Microsoft Project, while managers use Primavera P6.

      Both stakeholders view reports generated from the same underlying Schedule Model database, regardless of the software used.

    • ✗ Frequency: executive reports are hourly, while manager reports are quarterly.

      This reverses standard practice; execution planning (managers) usually requires more frequent updates than executive overviews.

30. 30 A scheduler is reviewing a project's health and finds many 'Open Ends' in the schedule logic. When presenting this to the project team, what impact should they emphasize regarding the schedule's behavior?

    Think about how missing predecessors or successors affect the 'dynamic nature' of a schedule database.

    The schedule model will not react predictably to progress updates or changes.

    Open ends prevent the scheduling tool's calculation engine from accurately calculating float and completion dates, making the model dynamic but brittle.

    • ✗ The project cost will automatically increase by $10\%$ per open end.

      Open ends are a logic error; they do not have a direct, fixed monetary penalty, although they create risks of hidden costs.

    • ✗ The project will be identified as high-performing on the Schedule Conformance Index.

      Minimizing open ends is a requirement for a high $SCI$ score; their presence significantly lowers the conformance index.

    • ✗ Every task with an open end is automatically part of the critical path.

      Open ends often hide the true critical path because the logic breaks, causing tasks to appear to have more float than they actually do.