What statement best describes change management in the SDLC?

What statement best describes change management in the SDLC?

• A. There is no change management in SDLC.
• B. There is a formal change management process throughout to address new information as it comes to light.
• C. End users have final say on all aspects of the project.
• D. All steps must be completed strictly in order.

Answer: (B)

Managing changes in the SDLC relies on a formal process that captures, evaluates, approves, and tracks changes as new information emerges. This approach ensures that requests from stakeholders, regulatory updates, or new requirements are analyzed for their impact on scope, schedule, cost, and quality before they’re implemented. It also preserves the project baseline and provides auditability and traceability, reducing the risk of uncontrolled scope creep. That’s why a formal change management process throughout, which addresses new information as it comes to light, is the best description. In contrast, saying there is no change management ignores real-world needs to govern modifications; letting end users have final say on all aspects contradicts project governance and change control; and insisting that all steps must be completed strictly in order doesn’t fit many modern SDLC approaches that embrace iterative and incremental development.

Managing changes in the SDLC relies on a formal process that captures, evaluates, approves, and tracks changes as new information emerges. This approach ensures that requests from stakeholders, regulatory updates, or new requirements are analyzed for their impact on scope, schedule, cost, and quality before they’re implemented. It also preserves the project baseline and provides auditability and traceability, reducing the risk of uncontrolled scope creep. That’s why a formal change management process throughout, which addresses new information as it comes to light, is the best description. In contrast, saying there is no change management ignores real-world needs to govern modifications; letting end users have final say on all aspects contradicts project governance and change control; and insisting that all steps must be completed strictly in order doesn’t fit many modern SDLC approaches that embrace iterative and incremental development.