agile versus waterfall

Development is no longer a newcomer, but many of my friends have asked some concepts about development models, such as Waterfall models, eXtreme Programming, and agile development. I feel like I have a vague understanding of the concept, today, I accidentally saw a simple article about this.Article, Reprinted to give yourself a conceptual knowledge. How to quickly respond to customer demand changes----

improve it, but to set up the main functions first, in the shortest time,The minimum loss is to complete an "imperfect outcome" until it is submitted. Then, through feedback from customers or users, we will gradually improve this "imperfect outcome.Spiral developmentTo a large extent, it is a risk-driven method system, because risk assessment must be carried out before each stage and before frequent loops.Agile development,Compared with iterative development, both emphasize submitting software

of each iteration, and to make suggestions for improvement. 7.showcase. 8. Communication is very important and all developers should be consistent in their understanding of the project activity. Strengthen communication between teams and customers. 9. Test-driven Development (TDD) 10. Stronger personal and team skills are required. 11. Agile management is the self-management of the team and the service management of the project manager. 12.

the characteristics of the waterfall model (Traditional way of development) 1. Emphasis on document  The output from the previous phase is the input to the next stage, and the document is the only information that is linked to the stage. So many developers seem to be developing documents rather than developing software, because the software's "look" can be seen later in the development. 2, no iteration and feedback. The

the characteristics of the waterfall model (Traditional way of development) 1. Emphasis on document  The output from the previous phase is the input to the next stage, and the document is the only information that is linked to the stage. So many developers seem to be developing documents rather than developing software, because the software's "look" can be seen later in the development. 2, no iteration and feedback. The

Next let's take a look at how agile processes solve waterfall-style process problems one by one: mso-char-indent-count:0;line-height:150%;mso-list:l0 level1 lfo1">Ø deployment process problems: The release time is getting longer and longer. In an agile process, a version is composed of a series of incremental integration, which are developed in an iterative and