How will you manage change request in Agile?

via backlog refinement

To be honest, I see this as a very odd question Pench because Agile is all about change and I see you are very well versed in Agile and have several certifications but maybe your question here is for the purposes of others to learn ?!?!?!?!

Anyways, Peter put it in simple words: Backlog Refinement !

Thank you, Rami! There was a lot of discussion going on in my organization on handling the change requests. Sometimes, teams are not sure how they want to identify the change whether it is part of the scope or out of the scope. That's what I wanted to post this question, to see whether I am going in right direction or is there any other way it will be handled. I always feel, refactoring myself will improve my brain.

Pench -

Change requests are usually driven by the PM and Finance policies & standards of the organization rather than the delivery approach used.

Where there is funding at the value stream or product level, change requests might only be needed if additional funding over and above what was approved for a given fiscal year is needed.

When funding is allocated at the project level, that's where change requests are more frequently needed. While detailed requirements might evolve over the life of a project, if the fundamental capabilities and benefits can't be achieved within the approved timelines or budget, a change request would be needed to do more.

As an example, with my current client (a large bank), a PCR is issued if:

- Funding for more sprints is needed
- Key features are not going to be delivered within the approved time & cost constraints
- Significant benefits erosion is forecast relative to the last approved funding request

Kiron

Pench -

Change requests are usually driven by the PM and Finance policies & standards of the organization rather than the delivery approach used.

Where there is funding at the value stream or product level, change requests might only be needed if additional funding over and above what was approved for a given fiscal year is needed.

When funding is allocated at the project level, that's where change requests are more frequently needed. While detailed requirements might evolve over the life of a project, if the fundamental capabilities and benefits can't be achieved within the approved timelines or budget, a change request would be needed to do more.

As an example, with my current client (a large bank), a PCR is issued if:

- Funding for more sprints is needed
- Key features are not going to be delivered within the approved time & cost constraints
- Significant benefits erosion is forecast relative to the last approved funding request

Kiron

Totally agreed Kiron, and this is exactly what we're doing here per my past experience.

Hi Pench:
In a perfect world in Agile, no PCR is needed, as all resources are 100% allocated and deliver what they can based on their productivity up a a number sprints that your approved budget can account for.