Integrating Change
Scrum rules require that the highest priority user stories in the Prioritized Product Backlog are selected before all others. Change requests are integrated into the Prioritized Product Backlog after approval. The Scrum Team makes a determination as to how many tasks are needed to complete the work in the Sprint backlog. The Change Management process is automatically executed during the existing process of ranking and inserting tasks to the Prioritized Backlog and then selected for the Sprint Backlog, seamlessly.
Sprint Changes
In cases where there is an urgent need to consider a change request, the Product Owner consults with the project’s stakeholders to determine whether the change needs to happen immediately or can wait until the next Sprint. If there is an immediate need to add the change, this would mean that the existing Sprint would have to end and a new Sprint must be started. Again, a Sprint should not have a change in its scope after it begins. If the change is not urgent enough, the change will be implemented in a future Sprint.
Backlog Refinement Changes
The purpose of refining the Prioritized Product Backlog is to ensure that prioritized user stories are available for 2 to 3 future Sprints. The Core Scrum Team and stakeholders whose input is needed should be invited to refinement sessions. In the case where the refinement sessions result in any reprioritization, the Scrum Team should agree with the proposed changes.
Sprint Review Changes
The Product Owner makes all decisions as to whether to accept or reject user stories during the Sprint Review meeting. User stories and their acceptance criteria should not be altered after the Sprint is completed. This ensures that user stories can be accepted based on the criteria that was previously agreed on. If user stories need to be changed, then these changes will need to be made in a future Sprint. New user stories may also be created during the Sprint Review meeting based on change requests from the Product Owner or stakeholders.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course:
Course Contents
Section 1: Agile Project Management
Section 2: Using the Agile Manifesto to Deliver Change
Section 3: The 12 Agile Principles
Section 4: The Agile Fundamentals
Section 5: The Declaration of Interdependence
Section 6: Agile Development Frameworks
Section 7: Introduction to Scrum
Section 8: Scrum Projects
Section 9: Scrum Project Roles
Section 10: Meet the Scrum Team
Section 11: Building the Scrum Team
Section 12: Scrum in Projects, Programs & Portfolios
Section 13: How to Manage an Agile Project
Section 14: Leadership Styles
Section 15: The Agile Project Life-cycle
Section 16: Business Justification with Agile
Section 17: Calculating the Benefits With Agile
Section 18: Quality in Agile
Section 19: Acceptance Criteria and the Prioritised Product Backlog
Section 20: Quality Management in Scrum
Section 21: Change in Scrum
Section 22: Integrating Change in Scrum
Section 23: Managing Change in Scrum
Section 24: Risk in Scrum
Section 25: Risk Assessment Techniques
Section 26: Initiating an Agile Project
Section 27: Forming the Scrum Team
Section 28: Epics and Personas
Section 29: Creating the Prioritised Product Backlog
Section 30: Conduct Release Planning
Section 31: The Project Business Case
Section 32: Planning in Scrum
Section 33: Scrum Boards
Section 34: Sprint Planning
Section 35: User Stories
Section 36: User Stories and Tasks
Section 37: The Sprint Backlog
Section 38: Implementation of Scrum
Section 39: The Daily Scrum
Section 40: The Product Backlog
Section 41: Scrum Charts
Section 42: Review and Retrospective
Section 43: Scrum of Scrums
Section 44: Validating a Sprint
Section 45: Retrospective Sprint
Section 46: Releasing the Product
Section 47: Project Retrospective
Section 48: The Communication Plan
Section 49: Formal Business Sign-off
Section 50: Scaling Scrum
Section 51: Stakeholders
Section 52: Programs and Portfolios