4 Values And 12 Agile Principles

4 Values And 12 Agile Principles
The Agile manifesto consisting of 4 values and 12 agile principles was initiated on 11 - 13 February 2001 at The Lodge, Utah, USA in a meeting attended by 17 people to discuss software development.

4 Agile Values

  1. Prioritizing individual interactions over processes and tools (individuals and interactions over processes and tools)
  2. Prioritizing the use of sufficient documents (working software over comprehensive documentation)
  3. Prioritizing collaboration between business users and development teams to produce outcome values compared to focusing on contract negotiations (customer collaboration over contract negotiations)
  4. Flexible to changes in market conditions compared to planning but not without prior planning (responding to change over following a plan). It would be better to make a short term plan based on current conditions than to make a long term plan because it may not be relevant when the product is released. Agile still makes plans, but if in the middle of the road you need to change, you have to adjust to market needs.
12 Principles of Agile

The principle of agile is the basic guideline for agile thinking as a reference for acting.

The 12 principles of the agile manifesto include customer satisfaction, readiness to accept change, continuous product creation, daily coordination, high motivation, direct communication, products are indicators of progress, continuous development, attention to technicality, simplicity, independence and evaluation.

1. Customer satisfaction

The first agile principle is customer satisfaction so that the goal of all forms of production must be based on customer satisfaction, not product owner satisfaction. Customers are satisfied when they receive working products in stages rather than waiting for a long period of releasing all the products.

An example of providing customer satisfaction is the speed of service providing products or prototypes in an MVP (Minimum Viable Product) manner and is carried out continuously to test customer satisfaction and then repaired after the product owner receives feedback.

Minimum Viable Product (MVP) criteria refer to at least the first 2 points of the following 4 MOSCOW rule points:
  • Must have: must exist for the product to be used and related to regulations.
  • Should have: should exist so that users can use it comfortably.
  • Could have: is nice to have
  • Won't have: has no business value.
2. Ready to accept change

The second principle of agile is being ready to accept changes even though these changes can hamper the work process because agile does not ensure that it has a detailed plan from the start of the project to completion.

3. Create products continuously

The third principle of agile is to create products continuously because products may only be prototypes. Furthermore, the product is finalized in stages according to customer preferences.

4. Daily coordination

The fourth agile principle is the daily coordination of the agile team that interacts intensely because the agile process lasts a short time, maybe only in a matter of weeks, so every agile team has to coordinate every day with the quick daily meeting process.

5. High motivation

The fifth agile principle is that each member of the agile team must be highly motivated and self-directed because the agile process requires each person to work on their own work with minimal supervision. Motivated teams are more likely to give their best work than unmotivated teams.

6. Direct communication

The agile process has a relatively short duration of work so it will be more effective if you communicate directly compared to coordination in the form of video calls and the like. One of the keys to the success of a project is communication.

7. Products are indicators of progress

Products or results are indicators of progress while work processes are not so influential. Products that are ready for release are the main measure of project progress, not based on the percentage of project status.

8. Continuous development

Agile promotes agile processes for continuous development. Agile engages all relevant stakeholders and maintains a continuous tempo of teamwork.

9. Attention to the technical

Product manufacturing techniques will be the main concern with every calculation and size must really be considered. The better the technique, the faster the product is made, the faster the project can be completed. Precise skills and good design ensure the team can keep pace and improve product quality.

10. Simplicity

Agile demands the speed of project completion, not project perfection. A simple but finished product is much better than a cool but incomplete product. The agile team focuses on activities to complete the work according to priorities, not being swayed by doing other things outside the sprint backlog.

11. Independence

The 11th agile principle is independence due to the lack of supervision and the project leader does not interfere much in technical work. Every agile team member needs independence in completing work.

Being able to get work done without a lot of direction and supervision is a quality of an agile team member. Each member will share ideas, skills and knowledge to produce quality products.

12. Evaluation

Self-improvement, process improvement, skills, skills and mutual assistance for team members to work more efficiently because the goal of agile is to align the development team with business needs and the success of agile is clearly visible and transparent.
Work Can Be Fun
Share WhatsApp

Post a Comment