Requirements Baseline

Correct Answer: A formal review point where requirements are approved and serve as foundation for future changes

A Requirements Baseline is a formally reviewed and approved set of requirements that serves as the foundation for future project work and changes. The correct answer accurately describes that it's a formal review point where requirements are approved and serve as the basis for future changes. This represents the controlled nature of a baseline and its role in change management. The other options are incorrect because: - A dynamic document with continuous updates contradicts the purpose of a baseline, which needs to be stable and controlled - The initial set from the first stakeholder meeting would be too preliminary to serve as a baseline, as requirements need proper analysis and refinement - A comprehensive collection before prioritization lacks the formal review and approval that defines a true baseline A Requirements Baseline is essential for project control and serves as a reference point against which proposed changes are evaluated and tracked. It provides a stable foundation for project execution while ensuring proper change control processes are followed.

Correct Answer: After stakeholders have approved all requirements and before development begins

The Requirements Baseline should be established after stakeholders have approved all requirements and before development begins. This is the correct timing because: A requirements baseline represents the agreed-upon, reviewed, and approved set of requirements that serves as the foundation for development work. Establishing the baseline at this point ensures: - All stakeholder needs are captured and validated - Requirements are complete and approved - Changes can be properly managed through change control - Development team has clear direction Other answers are incorrect because: - Setting the baseline at project charter signing is too early as requirements are not yet fully defined - Establishing baseline after development starts is too late and can lead to scope creep and rework - During initial requirements gathering is premature as requirements are still being discovered and analyzed

Correct Answer: To verify the completeness and consistency of requirements documentation

The main purpose of a requirements baseline audit is to verify the completeness and consistency of requirements documentation. This is the correct answer because baseline audits serve as quality control checkpoints to ensure that: - Requirements are properly documented - Requirements are internally consistent - No critical requirements are missing - Documentation follows established standards - Requirements are clear and unambiguous The other options are incorrect because: Stakeholder approval is an ongoing process throughout requirements development, not the main purpose of a baseline audit. Comparing performance metrics against historical data is more related to process improvement and benchmarking, not a requirements baseline audit. Validating requirements traceability to business objectives is part of requirements validation, but not the primary focus of a baseline audit which concentrates on documentation quality and completeness.