The Agile Principles
When the Agile Manifesto was drawn up in 2001, it embodied four values and twelve principles that signaled a new approach to application development. The first and most important principle states:-
“Our highest priority is to satisfy the customer through early and continuous delivery of valuable software”.
This is a simple enough statement to understand. What is not so obvious is the effort required to keep to the implied promise in this principle. It calls for:-
Valuable Software
● Valuable software. To the customer that means software that fits their requirements and is defect-free. To achieve this, the requirements must be carefully constructed and the software must be rigorously tested. The Seventh Principle states that “Working software is the primary measure of progress”, that is software that has been debugged and performs according to specification.
Early Delivery
● Early delivery. The software must be delivered as early as possible. This is achieved in two ways, firstly by delivering the leanest possible product that will fulfill the customer expectations, without any frills attached. The Tenth Principle describes this as “Simplicity”. The second action is to break down the code into small work packets that can be coded and tested in a short time of two to eight weeks. This is stated in the Third Principle.
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