In this post you will know the 12 Agile principles where every team member should follow to develop and delivery quality software product. Agile software Development is an approach to software development under which requirements and solutions evolve through the collaborative effort of self-organizing and cross-functional teams and their customer(s)/end user(s).The following are the 12 agile principles.
1. Customer Satisfaction:
Manifesto provides high priority to satisfy the costumer's requirements. This is done through early and continuous delivery of valuable software.
2. Welcome Change:
Making changes during software development is common and inevitable. Every changing requirement should be welcome, even in the late development phase. Agile process works to increase the customers' competitive advantage.
3. Deliver the Working Software:
Deliver the working software frequently, ranging from a few weeks to a few months with considering the shortest time period.
4. Collaboration:
Business people (Scrum Master and Project Owner) and developers must work together during the entire life of a project development phase.
5. Motivation:
Projects should be build around motivated team members. Provide such environment that supports individual team members and trust them. It makes them feel responsible for getting the job done thoroughly.
6. Face-to-face Conversation:
Face-to-face conversation between Scrum Master and development team and between the Scrum Master and customers for the most efficient and effective method of conveying information to and within a development team.
7. Measure the Progress as per the Working Software:
The working software is the key and primary measure of the progress.
8. Maintain Constant Pace:
The aim of agile development is sustainable development. All the businesses and users should be able to maintain a constant pace with the project.
9. Monitoring:
Pay regular attention to technical excellence and good design to maximize agility.
10. Simplicity:
Keep things simple and use simple terms to measure the work that is not completed.
11. Self-organized Teams:
The Agile team should be self-organized. They should not be depending heavily on other teams because the best architectures, requirements, and designs emerge from self-organized teams.
12. Review the Work Regularly: The work should be reviewed at regular intervals, so that the team can reflect on how to become more productive and adjust its behavior accordingly.
1. Customer Satisfaction:
Manifesto provides high priority to satisfy the costumer's requirements. This is done through early and continuous delivery of valuable software.
2. Welcome Change:
Making changes during software development is common and inevitable. Every changing requirement should be welcome, even in the late development phase. Agile process works to increase the customers' competitive advantage.
3. Deliver the Working Software:
Deliver the working software frequently, ranging from a few weeks to a few months with considering the shortest time period.
4. Collaboration:
Business people (Scrum Master and Project Owner) and developers must work together during the entire life of a project development phase.
5. Motivation:
Projects should be build around motivated team members. Provide such environment that supports individual team members and trust them. It makes them feel responsible for getting the job done thoroughly.
6. Face-to-face Conversation:
Face-to-face conversation between Scrum Master and development team and between the Scrum Master and customers for the most efficient and effective method of conveying information to and within a development team.
7. Measure the Progress as per the Working Software:
The working software is the key and primary measure of the progress.
8. Maintain Constant Pace:
The aim of agile development is sustainable development. All the businesses and users should be able to maintain a constant pace with the project.
9. Monitoring:
Pay regular attention to technical excellence and good design to maximize agility.
10. Simplicity:
Keep things simple and use simple terms to measure the work that is not completed.
11. Self-organized Teams:
The Agile team should be self-organized. They should not be depending heavily on other teams because the best architectures, requirements, and designs emerge from self-organized teams.
12. Review the Work Regularly: The work should be reviewed at regular intervals, so that the team can reflect on how to become more productive and adjust its behavior accordingly.
