TOPIC: Change in plan for agile

I am currently taking the simulator course from prepcast. I came a cross a quiz question about change management in Agile.
I thought making a change in Agile projects doesn't require a change or update in any of the project management subsidiary plans.
Can someone please explain the difference?
The question is in the file attached.

This question was seemed to be posted in multiple locations.

Ashwini:

Regardless of Waterfall or Agile methodologies, all changes that have an affect on scope, schedule or budget must go through a change management process including documentation on the effect of the change on the project.

Harry

Thank you Harry,
So when they Say Agile welcomes changes what does it mean ?
Also does agile have a Change Control Board ?

Typically in agile based projects, the product that the project is aiming at delivering usually gets scoped in real time. Very early in the project, the team begins to work on the product and because the feedback cycle is in real time, there are many changes that happen as the team begins developing the product. The sponsor may not like a certain feature or perhaps had a second thought about a feature that was initially developed, but after seeing it in use did not make sense, so it gets scrapped. Due to the nature of agile, changes are happening all the time. If changes are not welcomed, the biggest risk of the project is that the team ends up developing a product that the sponsor is not satisfied with or does not provide value.

It is uncommon for agile methodologies to have a Change Control Board, but there are dozens of agile methodologies out there and I wouldn't be surprised if at least one of those have a change control board. Generally speaking, a Change Control Board is not associated with agile.

Hope this helps!

Regards,

In reality, most of the organizations do have the CCB, Change Control Board regardless of their Agile maturity. In software project , most of the time for major software releases it is mandated to get an approval from the CCB.
The CCB includes a team of people from various functional domains - IT, security. architecture, development team, marketing & sales. release management , change management etc.
The change is presented in the CCB meeting just so everyone is aligned and If there are some action items coming out of the meeting, post resolution of those action items , the final approval is signed-off.
Also, senior leadership might attend the CCB meetings.