Requirements Change Management - Requirements Engineering and Management for Software Development Projects - page 124

2. Any CR needing more than 2 person hours, the impact would be passed on to
the customer
3. The impact analysis in terms of effort, schedule and cost would be submitted to
the customer for approval before implementing the CR. All CRs would be
implemented only after approval by the customer.
Now if the project is internal, that is, the development team and the end user
team work in the same organization, there would be no cost implication but the
schedule implication would still be applicable. Since it is internal project, we
should strive to absorb the schedule impact because the delay in deliveries would
adversely affect the system roll out.
Now the above strategies would work fine for CRs from end users/customers.
How do we handle the CRs from project team itself? Well, the change is ours and
therefore, we cannot pass it on to anyone. We need to absorb it.
8.9 Measurement and Metrics of Change Management
Change Management is a critical activity of requirements management. I am
dealing this topic in a separate chapter on measurement and metrics of require-
ments management itself.