Course contentsShow
← Software Engineering
Lesson 162 of 1,9334. Requirements EngineeringFree lesson

Change Request Processes

Formal and lightweight approaches to propose, evaluate, approve, and track requirements changes throughout the project.

Change Request Processes

What you'll learn: How teams formally or informally handle proposals to change requirements once a project is underway.

When a stakeholder or team member wants to change a requirement—add a feature, remove functionality, or modify behavior—you need a structured way to evaluate whether that change should happen. Without a process, chaos ensues: developers work on conflicting goals, timelines explode, and nobody knows what the "real" requirements are.

Lightweight vs. Formal Approaches

Lightweight processes suit agile teams and smaller projects. Someone proposes a change (often as a conversation or email), the product owner and key stakeholders quickly discuss impact, and if approved, it becomes a new user story in the backlog. The emphasis is on speed and collaboration.

Formal processes work better for regulated industries, large enterprises, or safety-critical systems. Changes require:

  • A written change request form documenting what, why, and who benefits
  • Change impact analysis (you learned this last lesson—assessing cost, risk, schedule effects)
  • Review by a change control board (CCB) or steering committee
  • Official approval signatures before work begins
  • Tracking in a requirements management tool with version history

The Core Flow

  1. Propose: Someone submits a change with rationale
  2. Evaluate: Analyze impact (cost, time, dependencies)
  3. Approve/Reject: Decision-makers accept, defer, or deny
  4. Track: Log the decision, update requirements documentation, communicate to the team

Think of it like requesting a building permit: you describe the renovation, the city checks safety and codes, then either grants permission or asks for revisions.

Key Takeaway:
Change request processes provide a controlled gate that prevents unvetted changes from derailing your project—ranging from quick backlog adjustments in agile teams to formal approval workflows in enterprise environments.