The Declaration of Interdependence
In 2005, a group of 15 project leaders met to the define the Agile Declaration of Interdependence. This declaration expanded upon the Agile Manifesto by establishing six management principles for complex projects.
The Declaration of Interdependence establishes that all members, stakeholders, and customers are interdependent and connected throughout the team. This declaration is designed to be a set of guidelines that provide additional process refinements.
A scrum master’s role is to facilitate delivery with members of a scrum team to achieve the highest levels of productivity. These team members include the execution team as well as the product owner.
The scrum master removes any impediments to progress and provides guidance for ceremonies, team dynamics, Agile learning’s, product definition and holding to the product vision of stakeholders.
The Six Principles of the Declaration of Interdependence
A strong scrum master embraces the six principles of interdependence understanding that their role is one of pulling together all the components of product delivery.
The six principles are:
1. Increasing the return on investment,
2. Deliver reliable project results,
3. Expect uncertainty and manage for it in a project,
4. Unleash creativity and innovation,
5. Boost team performance and
6. Improve effectiveness and reliability.
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