According to the PMBOK® Guide, specifically within the Develop Project Management Plan and Define Activities processes, requirements stipulated in a contract are considered Project Constraints.
Contractual Obligations: A contract is a legally binding document. If the contract specifies a final completion date (one year) and a specific interim deadline (foundation in 30 days), these are classified as Milestones.
Milestones vs. Activities: A milestone is a significant point or event in a project. Unlike activities, milestones have zero duration. Because these specific dates are " Hard " constraints dictated by the contract, they must be incorporated into the Milestone List and the Project Management Plan.
Mandatory Nature: The project manager does not have the discretion to ignore these dates. They form the basis of the Schedule Baseline. Once these milestones are added to the plan, the project manager will then sequence the necessary activities to ensure these deadlines are met.
Analysis of other options:
Option A: While the tight timeline represents a risk, milestones are primarily schedule components. You would record the risk of missing the deadline in the register, but you must first put the actual dates into the project plan to manage them.
Option C: This is a technical distractor. Milestones, by definition, have zero duration. They represent a point in time (the completion of the foundation), so there is no duration to calculate for the milestone itself—only for the activities leading up to it.
Option D: " Starting as soon as possible " is a proactive sentiment, but it is not a formal project management procedure. Proper planning (adding the constraints to the plan) must occur to ensure the " fast start " is actually directed toward the correct goals.
Per PMI standards, any date or requirement explicitly mentioned in a legal contract is a Constraint that must be documented in the Project Management Plan and tracked as a milestone to ensure compliance.
