Will Agile change the way Change is managed in Project Management

Thanks Andrew for explaining the phases that goes into Agile.

One question .. What does it mean by prioritization is value driven? Does it mean that the activities are carried out in a sequence , as required to complete each defined work in the backlog?

Sequence? Not necessarily. That promotes the wrong connotation.

The grooming of the product backlog is completed by the product owner. The items groomed to the top, and that are 'READY', can be brought forward to the sprint backlog.

All actions are to be value-driven, including not only the deliverables to complete the effort but even the actions of the team. The product owner prioritizes the work to be done by the amount of value it provides to the customer. Remember, in ideal standards, the intent is to continually produce MVP's. As the backlog is continually prioritized by value, it organically promotes valuable delivery while inhibiting the 'nice-to-haves'.

Does that help?

Just a little comment to @Andrew comment above. @Andrew comment above is great to explain some dynamics. Just take into account that @Andrew is talking about some specific technique and tool; User Stories, Prioritization, Product Backlog. But you can use what best fits to your organization. For example, if you take Scrum, there is no line, there is no statement that said that you have to use User Stories (Scrum is derined by the Scrum Guide: https://www.scrumguides.org. I think it could be usefull for you if you take a look to this paper that was the basement from Scrum framework creation (I worked with one of the Scrum creators and he said me that) and you will see that is nothing to be with software.https://hbr.org/1986/01/the-new-new-product-development-game