In term of Scrum, how we can manage change requests? 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. Saving Changes...
Usually a new story is created and prioritized for upcoming sprint, this is the way to handle CR. Saving Changes...
Seema SonkiyaHead Business Analysis Practices, PMI-PBA trainer| iZenBridge Consultancy Private LimitedJaipur, Rajasthan, India
Apart from above views, we need to see the how changes are accommodated within the selected Agile Approach to align the 4th principle "Responding to Change Over Following a Plan."
In a simple way, we can see this concept as - In Scrum, team select work for next the iteration goes in the Sprint Backlog. This work comes from the prioritized product backlog. This prioritized Product Backlog is continuously evolved - enable accommodation of changes without any formal process.
Each iteration has the Sprint Goal and team selects all the work necessary to achieve that Goal. As soon as the team finishes the sprint, it gets further work from the Product Backlog. For accommodating changes, remember, Product Backlog is never baseline and continuously evolved - this continuous product backlog grooming is the backbone of accommodating changes. How changes are handled within Sprint, you can watch: https://www.youtube.com/watch?v=rsrMxK-dy30 Saving Changes...
"Life is to be lived. If you have to support yourself, you had bloody well better find some way that is going to be interesting. And you don't do that by sitting around wondering about yourself."
