Scrum Principles
The principles for both single scrum master projects and those with Chief Scrum Masters for larger projects, programs, and portfolios are similar. The primary differences are around scaling the principles.
Team collaboration takes on a different level of scalability and management by the Scrum Master with larger program and portfolio opportunities. Managing team activities across multiple work streams requires that Scrum Masters collaborate across the program versus having a single stream perspective. Scaled Agile introduces an even larger enterprise component to the delivery of projects using Scrum Masters as domain specialists to guide teams within the more expansive nature of program and portfolio delivery.
Large Scrum programs expand the principles of Scrum by:
● Creating self-organizing teams with Scrum Masters who manage interdependencies
● Specialization in scrum team delivery may require a Scrum Master with similar capabilities
● Stronger definition of guidelines and processes to ensure consistency and
Coordination with the leadership of the Chief Scrum Master to create coordinated releases
Ceremonies
The value of ceremonies in an Agile Scrum project are paramount in obtaining the benefits of the framework. The ceremonies that are consistent for both single and enterprise are:
● Backlog Prioritisation
● Sprint Planning
● Daily Stand Up
● Sprint Review and
● Sprint Retrospective.
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