Agile Manifesto - Principles - Part 1
0 likes147 views
The document outlines the 12 principles of the Agile Manifesto which provide guidance for agile methods. It discusses each principle individually. The principles focus on satisfying customers, welcoming changing requirements, frequent delivery of working software, collaboration between business and developers, motivating individuals, face-to-face communication, using working software to measure progress, maintaining a sustainable pace, technical excellence and design, simplicity, self-organizing teams, and continuously improving.
Agile Manifesto - Principles - Part 1
- 1. Introduction to Agile Agile Manifesto - Principles
- 2. Agile Manifesto Principles https://agilemanifesto.org/ The authors of the Manifesto created twelve principles for agile methods.
- 3. Principles #1: Satisfy customer with great value. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Principles #2: Welcome change any time. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Principles #3: Deliver frequently. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Principles #4: Work with business. Business people and developers must work together daily throughout the project. The Twelve Principles https://agilemanifesto.org/
- 4. Principles #5: Motivate people. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. Principles #6: Face-to face communications. The most efficient and effective method of conveying information to and within a development team is face-to face conversation. Principles #7: Measure systems done. Working software is the primary measure of progress. Principles #8: Maintain sustainable pace. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. The Twelve Principles https://agilemanifesto.org/
- 5. Principles #9: Maintain design. Continuous attention to technical excellence and good design enhances agility. Principles #10: Keep it simple. Simplicity-the art of maximizing the amount of work not done-is essential. Principles #11: Team creates architecture The best architectures, requirements, and designs emerge from self-organizing teams. Principles #12: Reflect and adjust At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. The Twelve Principles https://agilemanifesto.org/
- 6. Principles #1 Satisfy customer with great value. • Satisfy the customer. • Early and continuous delivery. • Delivering is valuable software.
- 7. Principles #2 Welcome change any time. • Changes can be great for a project. • Well-understood, high-visibility methods for handling changes. • Agile keep the project adaptive and flexible as long as possible.
- 8. Principles #3 Deliver frequently. • Frequent testing and feedback. • Delivering within a short timeframe. • With demos and feedback, we learn of new requirements or changes.
- 9. Principles #4 Work with business. • Demos are example of how business and developers work together. • Daily face-to-face engagement. • Documents, e-mails, and even telephone calls are less efficient. • By working together daily, we can learn about the business.
- 10. Principles #5 Motivate people. • Build projects around motivated individuals. • Smart and motivated people on the team. • People work better when they have the freedom to organize their work.
- 11. Principles #6 Face-to face communications. • Documents are great for lasting record of events and decisions. • Face-to-face communication allows transfer a lot of information. • In a face-to-face, questions can be immediately answered.
- 12. Principles #7 Measure systems done. • Working software/systems is a primary measure of progress • Shifting our focus to results rather than documentation and design. • Working product helps ensure that features accepted by the customer.
- 13. Principles #8 Maintain sustainable pace. • Agile strive to maximize value over the long term. • Agile recognize the value of a work- life balance. • Working at a pace leads to a productive team.
- 14. Principles #9 Maintain design. • Keeping the design clean, efficient, and open to changes. • Technical excellence and good design allow the team to understand and update the design easily. • Balance between deliver value with attention to the design.
- 15. Principles #10 Keep it simple. • Agile focus on simplicity. • Boiling down our requirements to their essential elements only. • Simplest thing that could possibly work.
- 16. Principles #11 Team creates architecture. • The best result come out from self- organized team. • Self-organizing allows finding an approach that works best. • Self-organized team are closest to the technical details of the project.
- 17. Principles #12 Reflect and adjust • Gather lessons learned while they are still applicable and actionable. • Make sure we adjust how we complete the remainder work. • Retrospectives reflect on how things are working. • Retrospectives identify opportunities for improvements.
- 18. Thanks ً شكرا