Milestone & Constraint Management Flashcards
7 cards from real CST practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Milestone & Constraint Management flashcards as text
Which scheduling software term describes the process of removing a constraint from an activity so its dates are driven only by logic?
Answer: Releasing the constraint
Releasing or removing a constraint allows the CPM algorithm to compute the activity's dates based solely on its predecessor and successor relationships.
A project manager wants to show external reviewers only major decision points without detailed tasks. What schedule view is most appropriate?
Answer: Milestone-only schedule view
A milestone-only schedule view filters to show just key events, providing a high-level summary suitable for executive or external communication.
A CST exam question shows a milestone with Early Finish = Day 100 and Late Finish = Day 100 and a hard MFO constraint on Day 105. What is the milestone's Total Float?
Answer: 5 days
With logic driving EF to Day 100 and the MFO constraint at Day 105, the milestone has 5 days of positive float before it must occur.
Which document typically defines the contractual milestone dates that must be reflected in an Integrated Master Schedule (IMS)?
Answer: Statement of Work (SOW) and Contract Data Requirements List (CDRL)
The SOW defines scope and key events while the CDRL lists required deliverable dates; together they establish the contractual milestones the IMS must reflect.
During schedule risk analysis (SRA), what is typically done with project milestones?
Answer: Milestone dates are modeled probabilistically to produce confidence levels for achieving target dates
In SRA, Monte Carlo simulation propagates duration uncertainty through the network to produce probability distributions for key milestone completion dates.
Which relationship type is most commonly used to tie an activity's completion to the achievement of a milestone?
Answer: Finish-to-Start (FS)
The FS relationship ensures the predecessor activity must finish before the milestone (successor) can be achieved, which is the standard logic for milestone achievement.
A scheduler is reviewing a schedule where the same milestone appears twice — once as a deliverable and once as a contractual event. Which practice should be used?
Answer: Merge them into a single milestone with appropriate predecessor and successor links
Duplicate milestones representing the same event should be consolidated into a single milestone to avoid logical inconsistencies and duplicate reporting.