An Introduction to Change in Scrum
When we talk about change in connection with Scrum, there are many categories of change; in an agile environment, almost everything is in a state of flux. Here are some of the changes that can be expected in any project:-
- a change in team dynamics and maturity
- an improvement in processes and activities as discussed and adopted from a Retrospective
- an improvement in stakeholder confidence levels as the project progresses
- modifications to the product as originally envisaged during the project.
Managing change requests and scope changes during projects has always been a challenge, no matter what framework is being used; and in traditional projects it is discouraged as much as possible. The Agile Manifesto has a different take on the subject:-
“Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage”
(Agile manifesto – Principles).
This does not mean that there is a free-for-all when it comes to applying changes to the original requirement, changes still have to be managed. Scrum has clear guidelines on the subject, from who the roleplayers are, when change can be introduced, and managing the relevance of changes that have been requested.
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