PMI-SP : Schedule Closeout (Domain 4)
PMI – PMI-SP : Certified Scheduling Professional - Domain 4 - Schedule Closeout
The final stage of the project schedule lifecycle, Domain 4: Schedule Closeout, represents a critical transition where the theoretical schedule model is reconciled with the lived reality of project execution. While only representing approximately 6% of the PMI-SP examination (roughly 9 scored questions), this domain serves as the definitive point of accountability for the scheduling professional. It encompasses the finalization of activity data, the evaluation of performance against baselines, the execution of forensic analysis, and the formal archiving of the schedule model as a permanent organizational record.
Effective schedule closeout is not merely an administrative exercise; it is a technical requirement for defending or evaluating Extension of Time (EOT) claims and providing the data necessary for forensic schedule analysis. This study guide provides a deep exploration of the tasks, methodologies, and strategic imperatives associated with closing a project schedule in accordance with PMI standards and the Practice Standard for Scheduling.
The Strategic Significance of Schedule Closeout
In the lifecycle of a project, the closeout phase serves as the bridge between current performance and future organizational capability. For a Scheduling Professional (PMI-SP), Domain 4 is where the schedule model—once a dynamic tool for prediction—becomes a static historical record.
The primary goal of schedule closeout is to verify that all planned work has been completed and that the final state of the schedule accurately reflects the “As-Built” reality. This process involves a rigorous cleanup of the schedule logic, the capture of final actual durations, and the formal release of resources. Furthermore, this phase is the primary source of truth for forensic schedule analysis, which is essential for resolving disputes, evaluating delays, and securing final contractual acceptance from sponsors or clients.
Finalizing Activity Data and Network Logic Integrity
The first technical requirement of schedule closeout is the finalization of all schedule activities. During the Monitoring and Controlling phase (Domain 3), the schedule is updated periodically with progress. However, as the project nears completion, the scheduler must ensure that every activity in the network has been accurately closed.
Capturing Actual Durations and Dates
Every activity in the schedule model must be transitioned from “In Progress” or “Planned” to “Completed.” This requires capturing:
- Actual Start Dates: The exact date work commenced on an activity.
- Actual Finish Dates: The exact date the activity reached 100% completion according to the defined scope.
- Actual Durations: The total time elapsed between the actual start and finish, accounting for any non-working time or calendar constraints.
Cleaning Up Remaining Logic
A common challenge in schedule closeout is the presence of “dangling” logic or open-ended activities. As activities are completed, some logical relationships (Finish-to-Start, Start-to-Start, etc.) may no longer be relevant or may have been bypassed by field execution. The scheduler must:
- Remove Unnecessary Constraints: Eliminate “Start No Earlier Than” or “Finish No Later Than” constraints that were used for planning but are now superseded by actual dates.
- Verify Relationship Completion: Ensure that every successor has had its predecessor relationships satisfied.
- Address Out-of-Sequence Progress: If activities were performed out of order (contrary to the original logic), the scheduler must decide how this is reflected in the final record—typically by utilizing “Retained Logic” or “Progress Override” settings to ensure the final network remains cohesive.
Performance Measurement: Final Baseline vs. Actual Analysis
Once the schedule is finalized, the Scheduling Professional must evaluate how the project performed relative to its approved baselines. This evaluation is central to identifying business process improvements and validating the success of the project.
Variance Analysis at Completion
The scheduler performs a final variance analysis to compare the “As-Built” dates with the “Baseline” dates. Key metrics include:
- Start Variance: The difference between the baseline start and actual start.
- Finish Variance: The difference between the baseline finish and actual finish.
- Duration Variance: The discrepancy between the planned duration and the actual time taken.
Final Earned Value Management (EVM) Indicators
In many project environments, Earned Value Management is used to provide a quantitative assessment of performance. At closeout, the indices are finalized:
- Schedule Performance Index (SPI): While the SPI will mathematically converge toward 1.0 as the project finishes (because Earned Value eventually equals Planned Value), the historical SPI trends are analyzed to understand where the project lost or gained time.
- Schedule Variance (SV): Similar to SPI, final SV should be zero at completion, but the cumulative SV throughout the project lifecycle provides a narrative of performance deviations.
| Metric | Calculation | Closeout Interpretation |
|---|---|---|
| Schedule Variance (SV) | EV - PV | Measures the total volume of work ahead or behind in currency/units. |
| Schedule Performance Index (SPI) | EV / PV | Measures the efficiency of the schedule throughout the project life. |
| Total Float (TF) | LS - ES or LF - EF | Historically, how much flexibility was available before the critical path was impacted. |
Methodologies of Forensic Schedule Analysis: A Comparative Overview
Forensic schedule analysis is the study of why a project finished late or early. It is a specialized discipline within project controls that uses the schedule model to quantify the impact of delays. The PMI-SP candidate must understand the different methodologies used to reconstruct project history.
Forensic analysis is often required during Domain 4 to resolve claims for an Extension of Time (EOT). The integrity of the schedule updates maintained during Domain 3 directly impacts the validity of these forensic methods.
1. As-Planned vs. As-Built
This is the simplest form of forensic analysis. It compares the original baseline (As-Planned) with the final completed schedule (As-Built).
- Process: The two schedules are overlaid.
- Strength: It is easy to visualize and communicate to non-technical stakeholders.
- Weakness: It does not account for the dynamic nature of the project or the evolving critical path. It fails to identify when specific delays occurred or how they interacted with other activities.
2. Impacted As-Planned
This method involves taking the original, unimpacted baseline schedule and inserting delay events (modeled as new activities) to see how they would have logically pushed the completion date.
- Process: Delay “fragnets” (fragments of networks) are added to the baseline.
- Utility: Useful for demonstrating the theoretical impact of a specific event on the original plan.
Advanced Forensic Techniques: TIA and Windows Analysis
For complex disputes, more sophisticated methods are required that account for the project’s status at the time a delay occurred.
3. Time-Impact Analysis (TIA)
TIA is considered one of the most robust methods for analyzing delays. It is a “modeled” approach that can be used both prospectively (to predict a delay) and retrospectively (to analyze a past delay).
- Process: The scheduler takes a schedule update that was current just before the delay event occurred. A “fragnet” representing the delay is inserted into this “unimpacted” update. The schedule is then recalculated to see the change in the project finish date.
- Strategic Role: Because it uses the contemporaneous schedule update, TIA accounts for the actual progress and resource constraints existing at the moment of the delay.
4. Periodic Analysis / Windows Analysis
Also known as “Snapshot Analysis,” this method breaks the project duration into chronological “windows” (typically monthly reporting periods).
- Process: The scheduler analyzes the critical path at the start and end of each window. By comparing the progress made within that window against the plan, the analyst can isolate exactly how many days of delay occurred in that specific period and what caused them.
- Advantage: It handles the shifting critical path better than any other method, providing a month-by-month account of project health.
5. Collapsed As-Built
This retrospective method starts with the actual As-Built schedule and “collapses” it by removing the activities that represent delays or disruptions.
- Process: After removing the delay events, the schedule is recalculated to determine what the completion date would have been but for those delays.
- Application: Often used when the baseline schedule was poorly constructed or when contemporaneous updates are missing.
The Role of Schedule Maintenance in Claims and EOT Disputes
A project’s ability to defend itself against liquidated damages or to successfully claim for an Extension of Time (EOT) depends entirely on the quality of the schedule maintenance performed throughout the project.
The Contemporaneous Record
Courts, tribunals, and dispute boards place the highest value on contemporaneous records—schedules updated and validated at the time work was being performed. If a scheduler fails to capture actual start/finish dates accurately or allows the logic to become broken, the “As-Built” record becomes unreliable.
Defending Claims
When a contractor or subcontractor claims an EOT, the project scheduler uses the schedule model to:
- Verify Entitlement: Did the delay occur on the critical path? If a delay affects an activity with 20 days of total float and the delay only lasts 10 days, there is no impact on the project finish date and thus no entitlement to an EOT.
- Identify Concurrency: Were there multiple delays happening at the same time? If the owner delayed the project by 5 days, but the contractor also had a concurrent delay of 5 days on a different branch of the critical path, the financial and temporal liability may be shared.
- Mitigation Evaluation: The schedule is used to prove whether the project team took reasonable steps to mitigate the delay (e.g., through crashing or fast-tracking).
Capturing and Documenting Scheduling Lessons Learned
As the schedule is being closed, the Scheduling Professional has a responsibility to capture institutional knowledge. This is a requirement of the organizational process assets (OPA) update.
Technical Lessons
- Estimation Accuracy: Were the original duration estimates realistic? If actual durations consistently exceeded estimates by 20%, this data should be recorded to inform future projects.
- Logic Effectiveness: Did the chosen logical relationships (e.g., heavy use of Start-to-Start with lags) accurately represent how work was performed on-site, or did they lead to “logic loops” and update errors?
- Constraint Usage: Were the constraints applied to the schedule helpful for management or did they artificially mask true float?
Process Lessons
- Update Cadence: Was the monthly or weekly update cycle sufficient for managing the project complexity?
- Stakeholder Engagement: Did stakeholders provide timely and accurate progress data, or was the scheduler forced to rely on “best guesses”?
Archiving the Schedule Model and Organizational Records
The final act of Domain 4 is the systematic archiving of the schedule model. This is not simply saving a file; it is a controlled process to ensure the record is preserved for future use.
The Schedule Model Instance
The scheduler must archive the final “Schedule Model Instance.” This includes:
- The Native File: The raw data file from the scheduling software (e.g., XER for Primavera P6 or MPP for MS Project).
- The Narrative Report: A document explaining the final status, the methodology used for the final update, and a summary of the project’s temporal performance.
- Baseline Comparisons: A final report showing the delta between the original baseline, all approved re-baselines, and the final as-built state.
Archiving for History and Forensics
The archive serves two primary purposes:
- Historical Estimating Data: Future project planners will use this data to build more accurate schedules for similar work.
- Legal Protection: Most construction and engineering contracts have a “statute of limitations” regarding claims. The archived schedule is the primary evidence if a dispute arises years after the project is completed.
Resource Release and Systematic Closure of Work Packages
As the schedule activities are finalized, the resources associated with those activities must be formally released.
Work Package Closure
A work package is considered closed only when:
- All activities within the package are 100% complete.
- All actual dates and durations have been recorded.
- The final deliverables associated with the package have been accepted by the stakeholder.
- There is no remaining logic or budget assigned to the package.
Orderly Resource Release
The scheduler plays a key role in the “demobilization” of the project. By monitoring the final activities on the critical and near-critical paths, the scheduler provides management with the “Release Dates” for:
- Human Resources: When specific skill sets (e.g., specialized engineers or divers) are no longer required.
- Equipment: When heavy machinery (e.g., cranes or tunneling boring machines) can be off-hired or moved to another site.
- Materials: Ensuring that final deliveries are timed to minimize surplus.
Final Acceptance and Transition to Operations
The closeout of the schedule model is often a prerequisite for the project’s final acceptance. The scheduler must obtain formal sign-off on the contractual schedule components.
Final Contractual Milestones
The project typically contains one or more “Final Acceptance” or “Handover” milestones. The scheduler must prove that all predecessor activities required for these milestones have been satisfied according to the contract.
Transitioning to the Operational Schedule
In some industries, the project schedule transitions into an “Operational” or “Maintenance” schedule. The scheduler ensures that:
- The handover of the schedule data is clean.
- Operational stakeholders understand any remaining “punch list” items that may have been deferred.
- The logic and constraints are adjusted to reflect a maintenance environment rather than a construction/development environment.
Study Tools for Domain 4: Schedule Closeout
Short-Answer Questions
1. Question: What is the primary difference between “Total Float” and “Free Float” in the context of a final schedule review? Answer: Total Float is the amount of time an activity can be delayed without impacting the project finish date, whereas Free Float is the amount of time an activity can be delayed without impacting the early start of its immediate successor. Explanation: Total Float relates to the project’s overall end date, while Free Float is localized to the next activity in the sequence.
2. Question: Why is “Retained Logic” often preferred over “Progress Override” during the cleanup of a schedule network? Answer: Retained Logic ensures that if work is done out of sequence, the remaining work still respects the original predecessor logic, preventing unrealistic “gaps” in the schedule. Explanation: Retained Logic preserves the network’s integrity by requiring all logical dependencies to be met, even if progress has started on a successor.
3. Question: In forensic schedule analysis, what is the core methodology of a “Time-Impact Analysis” (TIA)? Answer: TIA involves inserting a fragnet representing a delay event into a contemporaneous schedule update to measure the specific impact on the project completion date. Explanation: It is a modeled, step-by-step approach that accounts for the project’s status at the exact time the delay occurred.
4. Question: What are the three primary actual data points that must be captured for every activity during schedule closeout? Answer: Actual Start Date, Actual Finish Date, and Actual Duration. Explanation: These three points define the “As-Built” reality of the activity and are necessary for final variance reporting.
5. Question: What is a “fragnet” in the context of forensic analysis? Answer: A fragnet (fragment of a network) is a small group of activities and logical relationships that model a specific delay event or change in scope. Explanation: Fragnets are inserted into existing schedule models to demonstrate how specific occurrences impact the overall project timeline.
6. Question: How does the Schedule Performance Index (SPI) behave as a project reaches 100% completion? Answer: The SPI will mathematically trend toward 1.0 because at completion, the Earned Value (EV) will eventually equal the Planned Value (PV). Explanation: Because all planned work is eventually earned, the ratio between EV and PV resolves to 1, regardless of how delayed the work was during execution.
7. Question: What is the main disadvantage of the “As-Planned vs. As-Built” forensic methodology? Answer: It is a static comparison that fails to account for the dynamic changes in the critical path or the interaction between different delays. Explanation: By only comparing the start and end points, it misses the complexity of concurrent delays and logic shifts that occurred during the project’s life.
8. Question: Why is the “Statute of Limitations” a factor in archiving schedule model instances? Answer: Contracts often allow parties to bring legal claims for several years after project completion, making the archived schedule essential evidence in future litigation. Explanation: Archiving ensures that a verified, “locked” version of the project history is available should a dispute arise long after the project team has disbanded.
9. Question: In the context of schedule closeout, what does “Cleaning the Logic” involve? Answer: It involves removing obsolete constraints, closing out all open-ended activities, and ensuring the final network correctly represents the sequence of work as it was actually performed. Explanation: Cleaning the logic ensures the final schedule is a cohesive, logical record rather than a collection of disconnected data points.
10. Question: What is the role of “Windows Analysis” in managing a complex project dispute? Answer: Windows Analysis breaks the project into chronological segments to identify which party was responsible for delays in each specific period. Explanation: By isolating performance into monthly or periodic “snapshots,” it provides a clear narrative of when and why the critical path shifted.
Open-Ended/Design Questions
- Scenario Design: You are the Lead Scheduler for a $500M infrastructure project that finished 6 months late. The owner and contractor are in a dispute over liquidated damages. Design a forensic analysis strategy that utilizes both “Time-Impact Analysis” and “Windows Analysis.” Explain why using both might be more effective than using one in isolation.
- Closeout Workflow: Create a comprehensive checklist for a Scheduling Professional to follow during the final 30 days of a project. Ensure the checklist covers technical cleanup, stakeholder communication, and organizational archiving.
- Critical Thinking: Discuss the ethical implications of a scheduler choosing between “Retained Logic” and “Progress Override” when preparing a schedule for a legal claim. How can the choice of software settings influence the outcome of a delay analysis?
- Process Improvement: You have completed the “Lessons Learned” session for a major project. You found that the critical path was frequently lost because of poor resource estimation. Propose a new “Schedule Strategy” (Domain 1) for the organization’s next project to prevent this issue from recurring.
- Forensic Comparison: Compare and contrast the “Collapsed As-Built” method with the “Impacted As-Planned” method. In what specific project scenarios would one be significantly more accurate than the other?
Glossary of Key Terms
- Actual Duration: The total working time elapsed from the actual start date to the actual finish date of an activity.
- As-Built Schedule: The final version of the schedule that records the actual start and finish dates for all activities performed on the project.
- As-Planned Schedule: The original, approved baseline schedule used to measure performance at the beginning of the project.
- Baseline: The approved version of the schedule model that is used as a benchmark for comparison against actual results.
- Collapsed As-Built: A forensic analysis technique that removes delay events from the as-built schedule to determine a “but-for” completion date.
- Contemporaneous Record: Documentation, including schedule updates, created at the same time the work was being performed.
- Critical Path: The sequence of activities that represents the longest path through the project, determining the shortest possible project duration.
- Extension of Time (EOT): A contractual adjustment that grants additional time to complete the project, typically exempting the contractor from liquidated damages for that period.
- Forensic Schedule Analysis: The technical reconstruction and study of a project’s schedule to determine the causes and impacts of delays.
- Fragnet: A set of activities and relationships representing a specific change or delay, used in impacted schedule analysis.
- Impacted As-Planned: A forensic method that adds delay events to the original baseline schedule to calculate their theoretical impact.
- Lessons Learned: The knowledge gained during a project which shows how project events were addressed or should be addressed in the future with the purpose of improving future performance.
- Liquidated Damages: A contractually agreed-upon amount that a party must pay if they fail to meet a specific milestone or completion date.
- Organizational Process Assets (OPA): The plans, processes, policies, procedures, and knowledge bases specific to and used by the performing organization.
- Progress Override: A scheduling software setting that allows a successor to proceed regardless of its predecessor’s status, ignoring the original logic.
- Retained Logic: A scheduling software setting that requires a predecessor to be 100% complete before its successor can finish, even if work has already started on the successor.
- Schedule Model Instance: A version of the schedule model that has been updated with status and/or changed to reflect a specific point in time.
- Schedule Performance Index (SPI): A measure of schedule efficiency expressed as the ratio of earned value to planned value.
- Time-Impact Analysis (TIA): A forensic technique that inserts a delay fragnet into a contemporaneous schedule update to determine the resulting delay to the project finish date.
- Windows Analysis: A forensic technique that examines project performance within specific chronological “snapshots” or time periods.
Leaderboard
No scores saved yet. Be the first!
25 Questions — PMI – PMI-SP : Certified Scheduling Professional - Domain 4 - Schedule Closeout
Expand any question to reveal the correct answer and explanation.
-
1 When performing a forensic delay analysis, which methodology is uniquely characterized by the insertion of logic 'fragnets' into a schedule model to quantify the impact of a specific change?
Focus on the technique that simulates the 'before and after' of a change event by adding new logic.
Time Impact Analysis (TIA)
TIA models the prospective or retrospective impact of specific delays by incorporating logic fragments directly into the schedule network to measure the shift in completion dates.
-
✗ As-Planned vs. As-Built
This method relies on a high-level comparison of the original baseline and the final actualized schedule without inserting specific logic fragments.
-
✗ Collapsed As-Built
This technique subtracts activities representing delays from the completed as-built schedule rather than inserting new logic into an active or baseline model.
-
✗ Windows Analysis
This approach focuses on analyzing schedule movements across specific update intervals or 'windows' to explain incremental slippage over time.
-
-
2 Which forensic methodology requires the analyst to start with the completed project schedule and then subtract activities representing delay events to determine a hypothetical completion date?
This method is often used when reliable as-built information is available and the goal is to show a 'but-for' scenario.
Collapsed As-Built
The collapsed as-built method, or 'but-for' analysis, removes specific delay durations from the final as-built to demonstrate when the project would have finished without those disruptions.
-
✗ Impacted As-Planned
This method adds delays to the baseline schedule rather than removing them from the final as-built record.
-
✗ Periodic Analysis
This strategy partitions the project duration into segments for incremental comparison and does not involve 'collapsing' the logic.
-
✗ Fragnet Modeling
While fragnets are components of analysis, the overall methodology of subtraction is specific to the collapsed as-built approach.
-
-
3 In the context of schedule closeout, what is the primary purpose of maintaining activity log notes throughout the project lifecycle?
Think about what a forensic specialist needs beyond just 'what happened' when trying to understand the 'why'.
To reconstruct the context and decision-making logic behind task delays
Activity logs provide the qualitative history necessary to explain why logic was altered or why specific tasks took longer than planned, which is vital for forensic reconstruction.
-
✗ To serve as the primary legal evidence for resource over-allocation
While helpful, logs are supplementary to formal resource histograms and contractual records rather than the primary evidence for over-allocation.
-
✗ To automate the calculation of total float in a forensic environment
Total float is a mathematical calculation derived from network logic, not from descriptive narrative notes.
-
✗ To replace the need for formal change request identifiers
Activity logs document the 'why,' but they do not replace formal configuration management identifiers required for auditability.
-
-
4 During project closeout, a scheduler must archive the schedule files. Which of the following is considered a critical component of configuration control for these records?
Having a backup is useless if you do not have a defined way to get the data back out.
Ensuring a verified retrieval procedure exists for the archived data
Effective configuration management requires not only the storage (backup) of data but also a tested and documented procedure to accurately retrieve those specific versions.
-
✗ Converting all schedule files into a non-editable flat-text format
Dynamic schedule files must be retained in their native format to allow for network recalculation and forensic analysis.
-
✗ Deleting all intermediate update instances to save repository space
Configuration control mandates that all versions be retained to provide a traceable history from the baseline to the final as-built.
-
✗ Sharing all access rights with stakeholders regardless of their organizational role
Access rights should be defined and controlled according to the communications plan rather than being universally distributed.
-
-
5 What is the result of performing a re-baseline late in the project lifecycle on the schedule performance metrics?
Consider how resetting the benchmark affects the measurement of previous variances.
Past performance statistics are zeroed out for remaining work
Re-baselining accepts past performance as the new starting point, which essentially resets efficiency indicators like the Schedule Performance Index for all future analysis.
-
✗ The original baseline is permanently deleted and replaced
The original baseline should never be deleted; it must be retained as a historical record against which the overall project is measured.
-
✗ Total float for completed activities is recalculated based on the new finish date
Completed activities have no float as their dates are actualized and static; float only applies to remaining uncompleted work.
-
✗ Negative float is automatically converted into positive contingency
Re-baselining might eliminate negative float relative to the new target, but it does not inherently create contingency time.
-
-
6 When initiating a forensic delay analysis, what is the first step a scheduler should take to understand what was originally planned?
The 'science' of comparison starts by defining the 'as-planned' benchmark.
Review the project contract and charter for schedule documentation requirements
Understanding the contractual obligations and charter objectives establishes the rules and standards that the initial schedule model was required to follow.
-
✗ Interview the project team regarding current actual progress
Interviews regarding actuals relate to determining what occurred, not what was originally planned.
-
✗ Perform a Monte Carlo simulation on the final as-built schedule
Monte Carlo is used for prospective risk assessment on uncompleted work, not for analyzing a static, completed project.
-
✗ Identify all 'open ends' in the final status update
Analyzing open ends in the final update helps evaluate the quality of the record, but it does not define the original plan.
-
-
7 Which artifact is essential for verifying contractual compliance of the schedule model during the closeout phase?
Look for a data-driven summary of actual performance versus the planned baseline.
Final schedule report including variance and EVM analysis
Distributing final reports with Earned Value and variance data is a required task to facilitate closeout and prove performance against contractual benchmarks.
-
✗ The Resource Breakdown Structure (RBS) from the proposal phase
The proposal RBS is a preliminary planning tool and does not reflect the final verified performance required for closeout.
-
✗ A list of all team performance evaluations
Performance evaluations are human resource artifacts and are not part of the contractual schedule model closeout.
-
✗ The initial project charter without any subsequent updates
While the charter is a reference, the updated schedule model and final reports provide the actual data needed for closeout validation.
-
-
8 A forensic specialist identifies that several activities were performed in a different order than specified in the baseline logic. Which concept describes this situation?
Think of a mismatch between the scheduled predecessor-successor relationship and the actual start/finish dates.
Out-of-Sequence (OOS) logic
OOS logic occurs when a successor activity starts or finishes before its predecessor's requirements—as defined by the network logic—are met.
-
✗ Dangling activities
Dangling activities occur when logic exists but does not drive a remaining task, rather than when the sequence of actual work violates the logic.
-
✗ Fast Tracking
Fast tracking is a deliberate planning technique to overlap tasks; OOS is a discrepancy between actual performance and the recorded plan.
-
✗ Critical Path shift
While OOS logic can cause the critical path to shift, the term for the logic violation itself is Out-of-Sequence.
-
-
9 What is the primary objective of obtaining formal acceptance of schedule components from the sponsor or client during closeout?
This is the final validation step to ensure the project records match the agreed-upon deliverables.
To facilitate formal project closeout and satisfy contractual obligations
Formal sign-off by stakeholders ensures that the schedule records are accepted as accurate and that the contractual delivery requirements have been met.
-
✗ To allow the scheduler to delete the baseline from the server
Baseline records must be archived and retained, never deleted, especially after acceptance.
-
✗ To automatically resolve any outstanding forensic claims
Acceptance is a step in the process, but forensic claims often require separate analysis even after general project acceptance.
-
✗ To transition the project team to their next assignments
Resource transitions are a project management function, while schedule component acceptance is a technical governance step.
-
-
10 In forensic scheduling, what is the 'Impacted As-Planned' methodology primarily used to demonstrate?
Think about adding delay events to a 'clean' starting plan.
The effect of specific delays when added to the original baseline schedule
This method involves inserting delay activities into the baseline to see how they would have pushed the completion date, assuming all other planning stayed constant.
-
✗ The efficiency of the project team's recovery strategies
This method ignores actual recovery and focuses only on adding impacts to the original plan.
-
✗ A chronological window-by-window analysis of incremental slippage
Chronological segment analysis is the hallmark of the Windows or Periodic Analysis method.
-
✗ The removal of owner-caused delays from an as-built record
The removal of delays from an as-built describes the Collapsed As-Built method, not Impacted As-Planned.
-
-
11 What role does the 'Data Date' play in the forensic analysis of a project's schedule updates?
Every update cycle depends on this specific 'as-of' timestamp.
It serves as the point in time where the status is recorded and from which remaining work is forecasted
The data date is the 'time-now' point for each update cycle, providing the anchor for performance measurement and future-looking logic.
-
✗ It represents the final contractual completion date defined in the charter
The contractual completion date is a constraint or goal, whereas the data date is a reporting status point.
-
✗ It defines the duration of the critical path in work days
The critical path duration is calculated based on activity lengths and logic, not solely on the reporting date.
-
✗ It is used to calculate the average productivity rate across the entire WBS
Productivity is a ratio of work to time, while the data date is simply a point in time.
-
-
12 When documenting lessons learned for project closeout, why should a scheduler analyze the accuracy of the original baseline compared to the final as-built?
This is part of updating Organizational Process Assets (OPAs) to benefit the next project.
To improve the business processes and planning accuracy for future similar projects
Comparing planned versus actual sequences and durations helps organizations refine their estimating standards and logical modeling for future endeavors.
-
✗ To penalize activity owners who deviated from the original plan
The purpose of closeout analysis is process improvement and organizational learning, not disciplinary action.
-
✗ To satisfy the requirement for a new Performance Measurement Baseline
A new PMB is created during the project to manage change, whereas closeout comparison is for historical archiving.
-
✗ To justify the use of progress override in future updates
The analysis is meant to validate good practices, and retained logic is generally preferred over progress override.
-
-
13 Which forensic technique is generally most effective for evaluating the delay impact of a single, well-defined event that occurred during execution?
This method uses a logic fragnet to 'simulate' the specific delay within the network.
Time Impact Analysis (TIA)
TIA is specifically designed to isolate and model the impact of a discrete change or delay event by inserting its logic into the schedule.
-
✗ Summary As-Planned vs. As-Built
A summary comparison can show that a delay occurred but is less effective at isolating the specific impact of one event from other concurrent factors.
-
✗ Pareto Distribution Modeling
Pareto analysis is a statistical tool for prioritizing issues, not a network-based forensic delay method.
-
✗ Monte Carlo Simulation
Monte Carlo evaluates prospective risk and probability rather than quantifying the retrospective impact of a specific realized event.
-
-
14 If a scheduler utilizes 'Retained Logic' during forensic analysis of an Out-of-Sequence activity, how will the uncompleted portion of that activity be treated?
Think about whether the system 'remembers' or 'ignores' the original logic after work has started prematurely.
It will be delayed until its predecessor's finish date is reached
Retained logic respects the original network dependencies, preventing the remaining work of a successor from proceeding until the predecessor is fully complete.
-
✗ It will be scheduled to start immediately at the Data Date
Starting work immediately despite missing predecessors describes the 'Progress Override' approach.
-
✗ It will be converted into a milestone to remove its duration impact
Forensic analysis must preserve the work duration to be accurate; milestones have zero duration and would distort the analysis.
-
✗ It will automatically be placed on the project's critical path
Critically is determined by float calculations, not by the selection of a status update method.
-
-
15 A scheduler is evaluating a project for schedule closeout and notes a high Schedule Conformance Index (SCI). What does this primarily indicate about the project record?
Think of this as a 'health check' for the technical integrity of the schedule network.
The schedule model adhered to quality standards and good practices during its lifecycle
A high SCI indicates the schedule was well-constructed, following standards like minimal constraints and valid logic, which makes it a reliable tool for forensic analysis.
-
✗ The project was completed ahead of its original baseline date
SCI measures the quality of the schedule's structure, not the project's finish variance or speed of execution.
-
✗ All forensic claims have been successfully resolved with the client
SCI is a technical quality metric, while claims resolution is a legal and administrative process.
-
✗ The project used a hybrid lifecycle rather than a purely predictive one
SCI can be applied to various scheduling approaches to measure structural integrity regardless of the specific lifecycle.
-
-
16 During forensic analysis, why is 'Progress Override' generally discouraged in favor of 'Retained Logic'?
Think about which method might 'cheat' the logic to make the end date look better.
It ignores original network logic and may provide an unrealistically early forecast
Progress override allows work to continue as if logic doesn't exist, which can hide true delays and distort the validity of the schedule's forecasting ability.
-
✗ It requires more manual data entry for every status update
Both methods are automated settings in scheduling tools; the difference lies in the calculation logic, not the amount of data entry.
-
✗ It prevents the scheduler from identifying the project's data date
The data date is a required input regardless of the logic calculation method chosen.
-
✗ It is only compatible with agile burndown charts
These terms refer to CPM (Critical Path Method) calculations and are not applicable to the distinct tracking methods used in agile.
-
-
17 Which of the following is a key difference between the 'Windows Analysis' and 'As-Planned vs. As-Built' forensic methods?
One method takes a 'macro' view of the whole project, while the other takes a 'micro' view of time intervals.
Windows Analysis evaluates slippage incrementally between updates, while As-Planned vs. As-Built compares the beginning and end states
Windows analysis looks at discrete intervals to see how and when slippage occurred, whereas As-Planned vs. As-Built is a more aggregate, start-to-finish comparison.
-
✗ Windows Analysis is only used for prospective delays, while As-Planned vs. As-Built is only for realized delays
Both methods are primarily retrospective (used after the work is done) but operate at different levels of granularity.
-
✗ As-Planned vs. As-Built requires a resource-loaded schedule, while Windows Analysis does not
Resource loading can enhance any forensic method but is not a distinguishing requirement between these two specifically.
-
✗ Windows Analysis ignores the critical path, whereas As-Planned vs. As-Built focuses solely on it
Both methods rely heavily on the critical path to determine the significance of the delays they identify.
-
-
18 When closing out a project, a scheduler should ensure that the final schedule instance is saved. What must be included in this instance to ensure forensic auditability?
Auditability requires knowing exactly 'when' the status was taken and 'what' it was compared against.
The final Data Date, version history, and baseline model for comparison
Capturing the final status date along with the original baseline and version history allows auditors to trace the project's evolution and verify the final performance.
-
✗ A list of all team member contact information for future interviews
While interviews are part of forensics, they are not part of the technical schedule model instance itself.
-
✗ The original proposal budget before any changes were made
The schedule model focuses on time and logic; the final budget record is a separate cost management artifact.
-
✗ A duplicate of the project charter's risk register
The risk register is a separate document; the schedule model needs to contain its own data, such as actual dates and remaining logic.
-
-
19 Forensic delay analysis is often required to resolve 'entitlement' in EOT (Extension of Time) claims. What does 'entitlement' refer to in this context?
Think about which party is 'at fault' and who should be 'compensated' with more time.
The contractual right of a party to be granted additional time due to a specific delay event
Entitlement is the legal or contractual justification that a party is not responsible for a delay and is therefore 'entitled' to a schedule extension.
-
✗ The total amount of positive float available on the project's critical path
Float is a technical scheduling value, whereas entitlement is a contractual/legal status.
-
✗ The authority of the Project Manager to approve schedule changes without a sponsor
Authority levels are defined by governance, while entitlement is a claim-specific determination of right.
-
✗ The organizational hierarchy of stakeholders in the communications plan
Entitlement relates to the causes and responsibilities for schedule slippage, not reporting hierarchies.
-
-
20 Which component of Earned Value Management is typically evaluated in a final schedule report to summarize overall performance at project close?
Consider the metrics that look back at 'what was planned' versus 'what was earned'.
Schedule Variance ($SV$) and Schedule Performance Index ($SPI$)
SV and SPI provide the final quantified measure of how well the project adhered to its time-based budget and efficiency goals.
-
✗ The three different Estimate at Completion ($EAC$) formulas
EAC is a forecasting tool used during the project; at closeout, actual costs and variances are used instead of estimates.
-
✗ The To-Complete Performance Index ($TCPI$)
TCPI measures the efficiency needed to finish the 'remaining' work, which is zero at project closeout.
-
✗ A prospective Monte Carlo simulation of the final baseline
Monte Carlo is a planning tool for uncertainty, not a summary metric for realized project performance.
-
-
21 When archiving schedule data for potential forensic analysis, why is it critical to identify 'virtual open ends' or 'dangling activities'?
Think about how a delay 'travels' through a network if a link is missing.
They make the schedule unresponsive to delays and hide true critical path impacts
Activities without proper driving logic (open ends) do not push successors correctly when delayed, which distorts the critical path and makes forensic analysis unreliable.
-
✗ They automatically cause the project to exceed its baseline budget
Logic errors affect the time forecast; budget issues are driven by cost rates and resource consumption.
-
✗ They prevent the scheduler from using three-point PERT estimates
PERT is a duration estimation technique and can be used even if the logic network has flaws, although the resulting model will be inaccurate.
-
✗ They are only allowed in agile iterations and forbidden in predictive models
While agile doesn't use CPM logic in the same way, 'open ends' are generally considered a bad practice in any structured schedule model.
-
-
22 A forensic analyst is reviewing the project records and finds multiple instances of 'Lead' (negative lag). What is a common risk associated with this practice in a schedule closeout audit?
Consider how 'starting before you finish' might confuse a network model's logic.
It creates unrealistic overlaps and can distort the critical path logic
Leads artificially pull successor work ahead of predecessor completion, which can create non-logical overlaps and make it difficult to determine the true cause of delays.
-
✗ It prevents the calculation of Earned Schedule ($ES$)
Earned Schedule is based on Earned Value and time; while leads might make the baseline hard to read, they don't stop the math of ES.
-
✗ It automatically requires a formal audit by the PMI
PMI audits applications, but they do not automatically audit individual project schedules for the use of leads.
-
✗ It causes the $SPI$ to always appear greater than $1.0$
SPI is a measure of work performed versus planned; leads might affect the 'plan' side, but they don't guarantee a positive efficiency ratio.
-
-
23 During the forensic comparison of as-planned vs. as-built schedules, the 'as-built' schedule is primarily defined by which data?
This is the 'final history' of when every task actually happened.
Actual start dates, actual finish dates, and realized durations
The as-built record is the factual history of the project, documented through the actualized dates and durations of all performed work.
-
✗ The original durations adjusted by a uniform risk factor
Adjusting durations with risk factors creates a 'risk-adjusted plan,' not a factual 'as-built' record.
-
✗ The remaining durations from the final status update
At closeout, there are no 'remaining' durations as all work is complete; only 'actual' durations remain.
-
✗ The sequence of activities defined in the project charter
The charter provides a high-level summary, but the as-built is defined by the detailed, recorded execution of work.
-
-
24 What is the primary benefit of the 'Time Impact Analysis' (TIA) methodology in resolving a dispute over a delay that occurred mid-project?
Think about the importance of 'context' when a delay happens while a project is already in progress.
It isolates the delay event to determine its impact at the specific point in time it occurred
TIA uses a 'snapshot' of the schedule status just before the delay to accurately model how that specific event disrupted the plan at that moment.
-
✗ It provides a cheaper, less labor-intensive alternative to as-planned comparison
TIA is actually one of the most labor-intensive and complex forensic methods because it requires detailed logic modeling for every event.
-
✗ It eliminates the need for detailed activity log notes
TIA relies heavily on logs to justify the logic and durations used in the added fragnets.
-
✗ It is the only method recognized by the $PMBOK^{\circledR}$ Guide for agile projects
TIA is a CPM-based forensic method; agile projects use different tracking mechanisms like burnup charts.
-
-
25 Which closeout task involves extracting final schedule performance data to update the organization's estimating database for future use?
This step ensures that the 'lessons' of the current project help make the next project's plan more realistic.
Updating Organizational Process Assets (OPAs)
Refining corporate databases with actual durations and productivity rates from completed projects is a core part of maintaining and improving OPAs.
-
✗ Performing a forensic delay claim
Claims are about resolving disputes; updating databases is about improving the accuracy of future planning.
-
✗ Obtaining final stakeholder sign-off
Sign-off validates the current project's completion, but it does not inherently involve updating external estimating benchmarks.
-
✗ Finalizing the Performance Measurement Baseline ($PMB$)
The PMB is finalized and 'locked' at the start of work; during closeout, it is compared against, not finalized.
-