The Agile Principles for Developers
Besides the Agile Manifesto, one of the most iconic documents for Agile Software Development is the list of Agile Principles. These twelve principles offer more depth than the four basic components of the Agile Manifesto. Not only do they give more depth, but they are more specific to software development as a practice. The Agile Principles affect the entire Scrum team, but they also have a specific influence on the developer role. Developers who follow the Agile Principles are able to work more effectively in Agile environments, and better integrate with Scrum teams.
1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
The entire Scrum team should obviously want to satisfy customers. However, this has specific meaning for developers on the team. The key points in this principle are early and continuous. Traditional software development does not release working software until very late in the process. Often, the first release is at the very end of the project, after everything is finished. Not only that, but the release is often one of just a few. Future versions usually only address bug fixes, and the time between these releases can be very long.
Developers in Agile software development get working software to customers as soon as possible. Once the requirements are determined, developers work on the highest priority features immediately. A release containing these features goes to customers by the end of the first sprint. The iterative nature of Agile means that customers will receive valuable software at the end of each sprint, with new features in every release.
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