12 principles that must be paid attention to in Agile Development

It was just a little time today. I sorted out the yiha materials. Share.
1. Our top priority is to deliver valuable software as soon as possible to satisfy our customers.
One article analyzes software development practices that help the company build high-quality products. One of these practices shows that early delivery of Systems with some features has a strong correlation with system quality. In this article, the fewer functions contained in the initial delivery system, the higher the quality of the final delivery system. It is also found from this article that there is a strong correlation between the regular delivery system and the final quality in the way of gradually adding features. The more common the delivery, the higher the quality of the final product. Agile practices will be delivered as early as possible and frequently. We strive to deliver a system with basic functions in the first few weeks of the project, then, we strive to deliver a function increasing system every two weeks. If the customer thinks that the current function is sufficient, the customer can choose to add these systems to the product, or they can simply choose to check for some of the existing features and point out the changes they want.
2. Even after development, you are welcome to change your requirements. Agile processes use changes to create competitive advantages for customers:
This is a statement about attitude. Participants in Agile processes are not afraid of changes. They think that changing needs is a good thing, because those changes mean that the table team has learned a lot about how to meet the market needs. The agile team will work very hard to maintain the flexibility of the software structure, so that when the demand changes, the impact on the system is minimal.
3. Regular delivery of software that can work, the delivery interval can be from several weeks to a few months, the shorter the delivery interval, the better:
We deliver software that can work and deliver it as early and regular as possible, not in favor of delivering a large number of documents or design plans
4. During the entire project development, business personnel and developers must work together every day.
In order to be able to develop projects in a keen manner, customers, developers, and stakeholders must make meaningful and frequent interactions.
5. Provide the required environment and support for motivated personal component projects and trust them to complete their work.
In agile projects, people are considered to be the most important factor for project success, and all other factors-process, environment, and management-are considered secondary.
6. Within the team, the most effective way of transmitting information is face-to-face communication.
7. Work software is the primary progress measurement standard,
Agile projects measure the development progress by measuring the number of current software to meet customer needs, they do not measure the development progress based on the development stage, the number of documents that have been written, or the number of common infrastructure code. Only when 30% of the required functions can work, to confirm that the progress has completed 30%
8. The agile process advocates sustainable development speed. Owners, developers and users should be able to maintain a long-term and constant development speed
The Agile Project is not a 50-meter sprint, but a marathon, and the team does not start at full speed and try to maintain that speed during project development; instead, they travel at a fast but sustainable speed.
9. Constantly paying attention to excellent skills and good design will enhance agility.
High product quality is the key to achieving high development speed. Keeping the software as concise and robust as possible is the way to develop software quickly. Therefore, all agile team members are committed to writing only high-quality code that they can write. They don't create chaos and tell themselves that they have more time to clean up.
10. Simple
Agile teams will not try to build those flashy systems.
11. The best architecture, requirements, and design come from self-organizing teams
An agile team is a self-organized team. A task is not assigned to a single team member from outside, but to the entire team. Then, the team determines the best way to complete the task.
12. At regular intervals, the team will reflect on how to work more effectively and effectively, and then adjust their behaviors accordingly.

Just a little time today, collate some information. Shares to you.
1. Our highest priority is to be done through early, continuous delivery of valuable software to enable customer satisfaction :.
An article analyzed companies have built high-quality products to help software development practice, a practice which has shown early part of the delivery system and quality of functional systems between highly relevant. the article said that the initial delivery system contains functions less, the ultimate delivery system for the higher quality. from the text also found that the way to gradually increase the regular functions of the delivery system and quality of the final between the very strong relevance. they treat ordinary delivery, the higher the quality of the final product. practice will rise early, often referred to the conducting of our efforts in the beginning of the project within a few weeks to a basic function of the system, and then we try to uphold every two weeks on increasing delivery of a functional system, if MERs believe that the current function is sufficient, customers can choose to join these systems products, or they can choose to check goes a simple function and that they want change.
2. Even the development of late, and also welcomes change demand. Quick changes to the process used to create competitive advantages for MERs:
This is the attitude that one on. the maid not afraid of hard process changes, changes in demand that they are good things, because those changes mean table team has learned a lot of knowledge of how to meet the needs of the market. the team will be very strong efforts to maintain flexibility in the structure of the software, such as changes in demand, the impact of the system is the smallest.
3. Regular delivery to the software delivery intervals from weeks to months, the shorter the better delivery intervals:
We can work to the software, and the early, regular delivery he did not favor large files or design plan
4. Throughout the project development, business development officers and staff must work together daily
In order to be able to project development of a sensitive manner, customers, the development of trade between the staff and must be meaningful, frequent world
5. focusing on the individual components of the project was to inspire, to provide them with necessary environment and support, and trust them to complete their work. in quick projects, were considered to be the most successful project achieved the most important factor, all other factors -- process, the environment, management, etc. are considered to be minor.
6. In the internal team, the most alternative tive way is face-to-face exchange of information transmission
7. working software is the primary measure of the progress standards, Nimble project through measurement of current software to meet customer needs to measure the amount of progress that they are not on the basis of the development phase, has been prepared by the number of files that have common or infrastructure code number to the measurement of SS, only when 30% of the work must be functional, it can progress to complete the 30%
8. quick process to promote sustainable development speed. responsible persons, developers and users shocould be able to maintain a long-term, constant speed development 50-meter dash was not quick projects, but marathon relay, the team not to start at full speed and trying to maintain that speed in the project development period; Instead, they began to fast but sustainable rate.
9. constant concern of outstanding skills and good design will enhance the ability of quick High-quality products is the development of high-speed access to the key, and maintain the software as simple, healthy development of software is rapid way. thus, the ability of all team members are committed to only prepare them to prepare high-quality code. they will not create chaos, and then tell their own in more time to clean up.
10. Simple Ability to build a team wocould not try to utilize those systems.
11. the best structure, and demand from organizations in the design from the team Since the team was quickly organized team, the task is not allocated to individual team members from the outside, but allocated to the entire team, and then complete the task by the team to determine the best method.
12. Periodically, the team will be more effective in how to work more efficiently tively reflect, and then act accordingly to adjust its own.