Requirements Baselining

Correct Answer: To establish an approved foundation for tracking changes and managing requirements scope

Requirements baselining serves as a formal approval point that establishes an agreed-upon foundation for managing project scope and changes. The correct answer captures the true purpose of requirements baselining - creating an approved foundation that allows for effective change tracking and scope management. This is crucial because it provides a reference point against which all future changes can be evaluated and managed. The other options are incorrect because: - Simply having stakeholders read and document requirements is not the main purpose of baselining; it's about establishing formal approval and change control - Requirements are not meant to remain unchanged throughout the project; baselining actually helps manage changes effectively rather than preventing them - While technical validation is important, it's not the primary purpose of requirements baselining; baselining focuses on establishing a formal starting point for change management

Correct Answer: Assess impact, get stakeholder approval, update requirements, update traceability matrix

The correct sequence when handling a change request for baselined requirements is: 1. First assess the impact - This is crucial as you need to understand how the change affects the project, resources, timeline, and other requirements 2. Then get stakeholder approval - After understanding the impact, stakeholders need to approve the changes based on the impact assessment 3. Once approved, update the requirements - Only after approval should the actual requirements be modified 4. Finally, update the traceability matrix - This ensures all relationships and dependencies are properly documented The other sequences are incorrect because: - Updating requirements before impact assessment and approval could lead to wasted effort if changes are not approved - Getting stakeholder approval before impact assessment means decisions are made with incomplete information - Updating the traceability matrix first makes no sense as there are no approved changes to trace yet This sequence follows logical project management and business analysis best practices, ensuring proper control and governance of requirement changes.

Correct Answer: Baselining ensures requirements have a fixed reference point for tracing changes and impact analysis

The correct answer states that baselining ensures requirements have a fixed reference point for tracing changes and impact analysis. This is accurate because: Baselining and traceability are closely interconnected processes: - Baselining establishes a formal, reviewed set of requirements that serves as a foundation - This foundation becomes the reference point against which all future changes are tracked - It enables effective traceability by providing a stable basis for tracking requirement evolution Why other options are incorrect: - Baselining and traceability are not independent processes - they work together in requirements management - Baselining is not a one-time process - it occurs at multiple points as requirements evolve - Traceability does not need to be established before baselining - they can be developed in parallel, and baselining often helps establish initial traceability links