How do we manage change request in Scrum? Saving Changes...
Sort By:
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
Change is embraced. Are we talking change during a sprint or for a later sprint? Either way, the additional story, or modification of a story would be documented and reevaluated as needed.
I'm sure others here can add more detail.
...
1 reply by Tam Nguyen
May 28, 2017 11:17 PM
Tam Nguyen
...
Thank you so much your answer. Can you explain or give me example about that
The answer is depend on the different situation. We always say that change is embraced in Agile. But if your contract has fixed price and specific edge, any change will lead to scope creep. If the request will change probably, it is a better choice to make your contract flexible. If the situation is just about a sprint, yes, modification of a story would be documented and reevaluated as needed.
...
1 reply by Tam Nguyen
May 28, 2017 3:37 PM
Tam Nguyen
...
Thank for your answer. Do your have any case study for that?
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
SCRUM is a framework, no a method. So, you can fill it with the process to do everything that best fits to your initiative. The change process you use today can fit in SCRUM. To be successful you have to understand what does mean framework (in this case SCRUM), method, process and life cycle (in this case is the life cycle used by SCRUM). No more than that.
...
1 reply by Tam Nguyen
May 28, 2017 3:11 PM
Tam Nguyen
...
Can you help me to clear about this. I am still unclear your answer. Thank you
SCRUM is a framework, no a method. So, you can fill it with the process to do everything that best fits to your initiative. The change process you use today can fit in SCRUM. To be successful you have to understand what does mean framework (in this case SCRUM), method, process and life cycle (in this case is the life cycle used by SCRUM). No more than that.
Can you help me to clear about this. I am still unclear your answer. Thank you Saving Changes...
The answer is depend on the different situation. We always say that change is embraced in Agile. But if your contract has fixed price and specific edge, any change will lead to scope creep. If the request will change probably, it is a better choice to make your contract flexible. If the situation is just about a sprint, yes, modification of a story would be documented and reevaluated as needed.
Thank for your answer. Do your have any case study for that? Saving Changes...
Change is embraced. Are we talking change during a sprint or for a later sprint? Either way, the additional story, or modification of a story would be documented and reevaluated as needed.
I'm sure others here can add more detail.
Thank you so much your answer. Can you explain or give me example about that Saving Changes...
"Impartial observers from other planets would consider ours an utterly bizarre enclave if it were populated by birds, defined as flying animals, that nevertheless rarely or never actually flew. They would also be perplexed if they encountered in our seas, lakes, rivers and ponds, creatures defined as swimmers that never did any swimming. But they would be even more surprised to encounter a species defined as a thinking animal if, in fact, the creature very rarely indulged in actual thinking."
