Основные идеи:1. Личности и их взаи

Основные идеи:
1. Личности и их взаимодействие важнее, чем процессы и инструменты.
2. Работающее программное обеспечение важнее, чем полная документация.
3. Сотрудничество с заказчиком важнее, чем контрактные обязательства.
4. Реакция на изменения важнее, чем следование плану.
Принципы:
1. удовлетворение клиента за счёт ранней и бесперебойной поставки ценного программного обеспечения;
2. приветствие изменений требований даже в конце разработки (это может повысить конкурентоспособность полученного продукта);
3. частая поставка рабочего программного обеспечения (каждый месяц или неделю или ещё чаще);
4. тесное, ежедневное общение заказчика с разработчиками на протяжении всего проекта;
5. проектом занимаются мотивированные личности, которые обеспечены нужными условиями работы, поддержкой и доверием;
6. рекомендуемый метод передачи информации — личный разговор (лицом к лицу);
7. работающее программное обеспечение — лучший измеритель прогресса;
8. спонсоры, разработчики и пользователи должны иметь возможность поддерживать постоянный темп на неопределённый срок;
9. постоянное внимание улучшению технического мастерства и удобному дизайну;
10. простота — искусство не делать лишней работы;
11. лучшие технические требования, дизайн и архитектура получаются у самоорганизованной команды;
12. постоянная адаптация к изменяющимся обстоятельствам.

Results (English) 1:

Main ideas:1. Individuals and their interaction is more important than processes and tools.2. Working software is more important than the complete documentation.3. cooperation with the customer is more important than the contractual obligations.4. reaction to change is more important than sticking to the plan. Principles:1. customer satisfaction due to the early and continuous delivery of valuable software.2. greeting requirements change, even at the end of the design (this can enhance the competitiveness of the product);3. frequent delivery of working software (each month or week or even more frequently);4. close, daily contact with developers throughout the project;5. project are motivated individuals who have the necessary working conditions, support and confidence;6. recommended method of information transfer is a personal conversation (face to face);7. working software is the best measure of progress;8. sponsors, developers, and users should be able to maintain a constant pace indefinitely.9. constant attention to improving the technical skill and excellent design;10. simplicity is the art of not doing unnecessary work;11. best technical requirements, design, and architecture are the self-organized teams;12. regular adaptation to changing circumstances.

Results (English) 2:

The basic ideas:
1. Personality and their interaction is more important than processes and tools.
2. Software works is more important than full documentation.
3. Cooperation with the customer is more important than contractual obligations.
4. Responding to change is more important than following a plan.
The principles:
1. customer satisfaction due to early and uninterrupted delivery of valuable software;
2. greeting requirements change even at the end of development (this may enhance the competitiveness of the product obtained);
3. frequent delivery of working software (every month or a week or more often);
4. close, daily contact with the developers of the customer throughout the project;
5. The project covers motivated individuals who provide the necessary working conditions, support and trust;
6. the recommended method of transmitting information - a private conversation (face to face);
7. operating software - the best measuring progress;
8. sponsors, developers and users should be able to maintain a constant pace indefinitely;
9. constant attention to improving the technical skills and user-friendly design;
10. Simplicity - the art of not doing unnecessary work;
11. best technical requirements, design and architecture derived from self-organized teams;
12. constant adaptation to changing circumstances.

Results (English) 3:

The main ideas:
1. Individuals and their interaction is more important than processes and tools.
2. Running software is more important than full documentation.
3. Cooperation with the customer more importantly,Than contractual obligations.
4. The response to changes is more important than adherence to plan.
principles:
1. customer satisfaction through early and smooth delivery valuable software;
2.Greeting change requirements even at the end of (this can improve competitiveness received product) ;
3. frequent delivery operating software (every month, or a week or even more frequently) ;
4.Close, daily communication with the developers on the customer throughout the project;
5. The project is motivated by identity, which are provided with appropriate terms and conditions of work, support and confidence;
6.The recommended method for transfer of information - personal conversation (face to face) ;
7. running software - the best gauge progress;
8. sponsors,Developers and users should be able to maintain a steady pace for an indefinite period;
9. constant attention to improving technical skills and convenient design;
10.Easy - the art not to do unnecessary work;
11. the best technical requirements, design and architecture are derived from self-organized command;
12. continuous adaptation to changing circumstances.