Change Request Management

Correct Answer: The change request board evaluates proposed changes while configuration management tracks approved modifications

The correct answer represents the true complementary relationship between a change request board and configuration management in a business analysis context. A change request board evaluates and approves proposed changes based on their impact, feasibility, and alignment with business objectives. Configuration management then takes responsibility for tracking these approved changes, managing versions, and maintaining the integrity of project artifacts. Other options are incorrect because: - Technical implementation is not the primary role of a change request board; it evaluates and approves changes rather than implementing them - The change request board considers all impacts, not just budget impacts, and configuration management's role extends beyond timeline adjustments - While stakeholder communication is important, the change request board's primary function is evaluating changes, and configuration management does more than just version control - it maintains the integrity of all project artifacts and ensures proper implementation of approved changes

Correct Answer: Linking each change to its source requirement and affected components

Linking each change to its source requirement and affected components is the most crucial element for traceability because it: 1. Establishes clear connections between requirements, changes, and impacted system elements 2. Enables impact analysis and tracking of requirement implementation 3. Facilitates verification that all requirements are properly addressed 4. Supports future maintenance and changes by providing clear relationships The other options are less effective because: Extensive documentation of impacts, while valuable, does not establish the essential relationships between requirements and changes. Maintaining technical discussion logs is helpful for context but doesn't create the necessary traceability links. Recording stakeholder approvals is important for change control but doesn't contribute to requirement-to-implementation traceability.

Correct Answer: Create a change impact matrix and assess interdependencies between workstreams

Creating a change impact matrix and assessing interdependencies between workstreams is the most effective approach because: 1. It provides a systematic way to visualize and analyze how changes affect multiple workstreams simultaneously 2. It helps identify potential ripple effects across the project 3. It enables proactive risk identification and mitigation strategies 4. It facilitates better communication among stakeholders about change impacts Why other options are less effective: Evaluating workstreams separately and combining assessments at completion misses critical real-time interdependencies and can lead to integration issues. Developing a comprehensive risk analysis framework, while valuable, is too broad and may not specifically address the immediate needs of managing change requests effectively. Scheduling sequential implementation creates unnecessary delays and doesn't leverage the benefits of concurrent work, potentially extending project timelines and increasing costs.