Back to Validation and Verification of Requirements

Requirements Baselining

5 minutes 5 Questions

Requirements Baselining is the process of formalizing and documenting the agreed-upon set of requirements at a specific point in time, establishing them as the official foundation for further project development. Once the requirements are baselined, any subsequent changes must go through a formal change control process. This ensures that all stakeholders are aware of and agree to modifications, helping to prevent scope creep and unmanaged changes. Baselining involves several steps: finalizing the requirements documentation, obtaining formal approval from stakeholders (often through sign-off), and storing the baseline in a configuration management system. This baseline becomes a reference point against which project progress, deliverables, and changes are measured. In terms of validation and verification, baselining provides a clear and unambiguous understanding of what is to be delivered. It facilitates alignment among stakeholders, project managers, and the development team. By having a formal baseline, teams can verify that subsequent work aligns with the agreed requirements and validate that the final product meets the original objectives. Baselining also supports effective project management by enabling impact analysis when changes are proposed. It helps in tracking requirements throughout the project lifecycle, ensuring transparency, and maintaining control over the project's scope. Ultimately, requirements baselining contributes to delivering a product that meets stakeholder expectations while adhering to time and budget constraints.

Test mode:
Start practice test
PMI-PBA - Validation and Verification of Requirements Example Questions

Test your knowledge of Amazon Simple Storage Service (S3)

Question 1

What must be obtained before making any changes to a requirements baseline during project execution?

Correct Answer: Formal approval through change control process

Formal approval through the change control process is essential before making any changes to a requirements baseline during project execution. This is a fundamental principle in project management and business analysis. Here's why this is correct: - Changes to baselines must follow established control processes - It ensures proper documentation and traceability - It maintains project governance and integrity - It protects the project from unauthorized scope changes Why other options are incorrect: - Stakeholder consensus through informal discussions lacks the necessary rigor and documentation - While detailed documentation is important, it's only part of the process and not sufficient on its own - A project manager's verbal authorization does not provide adequate control or documentation and bypasses proper change management procedures The change control process ensures: - Proper evaluation of impacts - Documentation of decisions - Stakeholder awareness - Baseline integrity - Compliance with project governance

Question 2

During which project phase should requirements baseline versioning begin?

Correct Answer: When the stakeholders formally approve the requirements

Requirements baseline versioning should begin when stakeholders formally approve the requirements. This is the correct point because: The baseline represents the approved version of requirements that serves as the foundation for project work. Until formal stakeholder approval is obtained, requirements are still subject to change and refinement. Having just technical team review is insufficient as stakeholders are the ultimate authority on requirements. The project scope statement is too early in the process, as detailed requirements have not yet been developed and approved. The requirements management plan is a process document that defines how requirements will be managed - it precedes actual requirements development and approval.

Question 3

What is a key characteristic of a well-managed requirements baseline?

Correct Answer: It provides a formal agreement point for stakeholder sign-off

A well-managed requirements baseline provides a formal agreement point for stakeholder sign-off. This is the correct answer because: - It establishes a clear reference point for project scope - It enables formal change control processes - It creates accountability and commitment from stakeholders - It helps measure project progress against agreed requirements The other options are incorrect because: Allowing continuous modifications defeats the purpose of a baseline, which should be stable and controlled through change management processes. Stating requirements cannot be changed under any circumstances is too rigid and unrealistic - changes can occur but must follow proper change control procedures. An informal collection of wishes lacks the formality and structure needed for proper requirements management and project control.

Go Premium

PMI Professional in Business Analysis Preparation Package (2024)

  • 3015 Superior-grade PMI Professional in Business Analysis practice questions.
  • Accelerated Mastery: Deep dive into critical topics to fast-track your mastery.
  • Unlock Effortless PMI-PBA preparation: 5 full exams.
  • 100% Satisfaction Guaranteed: Full refund with no questions if unsatisfied.
  • Bonus: If you upgrade now you get upgraded access to all courses
  • Risk-Free Decision: Start with a 7-day free trial - get premium features at no cost!
More Requirements Baselining questions
25 questions (total)
Start 25 question test