When implementing Scrum, Scrum Masters prefer to follow the rule which is never to allow changes during the Sprint. We can only accommodate requests for improvement at the end of the sprint or the beginning of the sprint, but not during the Sprint. However, in a realistic environment, we see product owners, coming up with an urgent request for improvement or fixing bugs.
As we live in the age of agile business environments – always changing, and always adapting – adapting to change is Inevitable. Responding to change is an essential part of IT projects, from the project level and throughout the project life cycle (Fui-Hoon Nah, Lee-Shang Lau et al. 2001). Change drives companies to develop products and deliver right product at a right time.
If you agree with; Scrum acts as a framework for software and other products to be developed (to produce a high-value product, it lets teams communicate and offers a way to address issues and changes). Then, it is wiser, not to obey all the procedures blindly without knowing the business needs and facets of the market. Interacting, re-planning to communicate with all the stakeholders and then making a better decision is always better.
Take a minute to follow me on Twitter if you enjoyed this post and want to see more.
References
Fui-Hoon Nah, F., et al. (2001). “Critical factors for successful implementation of enterprise systems.” Business Process Management Journal 7(3): 285-296.
Most commented