How do change-driven methodologies (for example Agile software development) handle requirements change management?
Change-driven methodologies use a formal requirements change control process and a formal requirements prioritization process.
Change-driven methodologies do not typically have a change control process that is separate from the requirements prioritization process. All requirements ("new"/"changed") are recorded in the product backlog and prioritized.
Change-driven methodologies don't prioritize requirements. They handle requirements change in a somewhat arbitrary way, sometimes formally, sometimes informally.
In this matter, change driven methodologies are not different from plan driven methodologies.