Difficulty: Medium
Correct Answer: A high level description of the project scope that refines the project charter and will be elaborated in later planning
Explanation:
Introduction / Context:
Earlier editions of the PMBOK Guide included a process called Develop Preliminary Project Scope Statement as part of Project Integration Management. Although newer editions integrate scope definition differently, many exam style questions still refer to this concept, especially in legacy material. The preliminary scope statement refines the project charter by providing more detail about what the project will and will not deliver, without being as detailed as the full scope baseline developed later. This question tests your understanding of that purpose and output.
Given Data / Assumptions:
Concept / Approach:
The preliminary project scope statement expands on the project charter by adding more information about deliverables, constraints, assumptions and boundaries. It is still high level but provides enough definition to guide the development of the project management plan and detailed scope baseline. It is not the same as the activity list, network diagram, cost baseline or lessons learned. Therefore, we look for an option that describes a high level scope document that serves as a bridge between the charter and full planning.
Step-by-Step Solution:
Step 1: Review option A. It describes a high level scope description that refines the charter and will be elaborated in later planning. This matches the intended role of the preliminary scope statement.Step 2: Review option B. The detailed activity list and network diagram are outputs of schedule planning processes such as Define Activities and Develop Schedule, not of this integration process.Step 3: Review option C. The finalized project budget baseline comes from cost planning processes, such as Determine Budget.Step 4: Review option D. The lessons learned register is part of closure activities, particularly Close Project or Phase, and not part of initiation.Step 5: Conclude that only option A correctly states the purpose and main output of Develop Preliminary Project Scope Statement.
Verification / Alternative check:
Legacy PMBOK documentation describes the preliminary scope statement as a progressively elaborated document that provides more detail than the project charter but less than the final scope baseline. It often includes product description, acceptance criteria, boundaries, assumptions and constraints. This description aligns precisely with option A. The other outputs listed in the remaining options clearly belong to different process groups and knowledge areas, confirming that they are not correct here.
Why Other Options Are Wrong:
The detailed activity list and network diagram are scheduling tools used for time management, not scope definition at initiation. The cost baseline is a financial planning artifact and requires detailed scope and schedule information that are not yet available at this early stage. Lessons learned are captured primarily at the end of a project or phase and documented during closing, not during initiation.
Common Pitfalls:
Because the preliminary scope statement exists only in some editions of the PMBOK Guide, candidates sometimes confuse it with the final scope statement or the entire scope baseline. Another pitfall is to associate any document with the word statement to closing, such as mission statement or final statement. To avoid confusion, remember that this process is an early integration activity intended to define scope just enough to support planning, not to finalize every detail.
Final Answer:
The main purpose and key output is a high level description of the project scope that refines the project charter and will be elaborated in later planning.
Discussion & Comments