CAPM Practice: Determine how to gather requirements

Clear scope boundaries focus requirements gathering on what the solution must address and explicitly exclude what it won't handle. Early scope definition prevents scope creep, aligns stakeholder expectations, and makes elicitation more efficient.

**Why not A:** Writing detailed technical specifications is part of solution design, not scope definition. Scope definition establishes what is and is not included in the solution at a boundary level, while technical specifications describe how included features will be built.

**Why not B:** Defining the project team's roles and responsibilities is part of the resource management or organizational planning process, not scope definition. Scope definition focuses on the boundaries of what the solution will address, not on team structure.

**Why not D:** Creating the project schedule and resource plan are project planning activities, not scope definition. Scope definition must happen before scheduling, as the boundaries of what is included directly inform what needs to be planned and resourced.