Project Management Central

Please login or join to subscribe to this thread

Topics: Agile, Change Management, IT Project Management
How will you manage change request in Agile?
Network:1525



Handling the change requests in Agile.
Sort By:
Page: 1 2 next>
Network:307



via backlog refinement
...
2 replies by Andrew Craig and Pench Batta
Oct 19, 2018 11:38 AM
Pench Batta
...
Thank you, Peter!
Oct 20, 2018 9:12 AM
Andrew Craig
...
Can't get much more succinct than that :)
Network:103022



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 !
...
1 reply by Pench Batta
Oct 19, 2018 11:43 AM
Pench Batta
...
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.
Network:1525



Oct 19, 2018 9:36 AM
Replying to Peter Ambrosy
...
via backlog refinement
Thank you, Peter!
Network:1525



Oct 19, 2018 11:26 AM
Replying to Rami Kaibni
...
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.
...
1 reply by Rami Kaibni
Oct 19, 2018 1:25 PM
Rami Kaibni
...
Makes sense, thanks for the rationale Pench.
Network:103022



Oct 19, 2018 11:43 AM
Replying to Pench Batta
...
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.
Makes sense, thanks for the rationale Pench.
Network:1106



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
...
2 replies by Ken Yeung and Pench Batta
Oct 19, 2018 3:04 PM
Ken Yeung
...
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.
Oct 19, 2018 3:52 PM
Pench Batta
...
Thank you, Kiron!
Network:12



Oct 19, 2018 2:44 PM
Replying to Kiron Bondale
...
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.
...
1 reply by Pench Batta
Oct 19, 2018 3:53 PM
Pench Batta
...
Thank you,Ken!
Network:1525



Oct 19, 2018 2:44 PM
Replying to Kiron Bondale
...
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
Thank you, Kiron!
Network:1525



Oct 19, 2018 3:04 PM
Replying to Ken Yeung
...
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.
Thank you,Ken!
Network:1669



In the same way you manage a change request using any type of approach: by running the defined change management process. Some people think that using Agile approach the initiative will accept changes at any time in the life cycle and no change management process will run to evaluate it. That is not right, including each method based on Agile practice has a change management process defined on it, sometimes implicit, The reason because in the new PMBOK (just in case you follow the PMI way to manage project) the work "project" was added to most of the items is because things like change management must be derived for corporate policies.
...
1 reply by Pench Batta
Oct 21, 2018 4:38 PM
Pench Batta
...
Thank you, Sergio.
Page: 1 2 next>  

Please login or join to reply

Content ID:
ADVERTISEMENTS

"A behaviorist is someone who pulls habits out of rats."

- Anonymous

ADVERTISEMENT

Sponsors

Vendor Events

See all Vendor Events