PK0-004 · Question #212
A minor change to the baseline schedule is required. This change will be the second minor modification to the schedule. Which of the following is the appropriate version number?
The correct answer is B. 1.2. Project document version numbering uses a major.minor format where the approved baseline starts at 1.0 and each minor change increments the decimal number.
Question
A minor change to the baseline schedule is required. This change will be the second minor modification to the schedule. Which of the following is the appropriate version number?
Options
- A0.3
- B1.2
- C2.0
- D3.0
How the community answered
(62 responses)- A6% (4)
- B89% (55)
- C2% (1)
- D3% (2)
Why each option
Project document version numbering uses a major.minor format where the approved baseline starts at 1.0 and each minor change increments the decimal number.
Version numbers below 1.0 such as 0.x indicate a document that has not yet been formally approved or baselined.
The baseline schedule begins at version 1.0, and the first minor modification incremented it to 1.1, so this second minor modification correctly produces version 1.2. Minor changes increment only the number after the decimal point, reflecting small adjustments to an approved baseline without triggering a full major revision. This convention clearly communicates the nature and history of document changes to all stakeholders.
Version 2.0 indicates a major revision or significant overhaul of the document, not a minor modification to an existing baseline.
Version 3.0 would indicate a third major revision of the schedule, which does not reflect the two minor changes described in the scenario.
Concept tested: Project document version numbering conventions
Topics
Community Discussion
No community discussion yet for this question.