It takes about one and a half years to enter the project team. In this short year and a half, I experienced the traditional waterfall development model, XP
Exploring programming models and agile development.
The first half of the year was the traditional waterfall development model: one month for demand and one month for prototype. And then two months of development. After the development, QA And then two months of bugs.
Fixing . This mode brings two difficult problems: 1 ) If the demand changes frequently (normally), especially in the later stages of development, the changes to this demand will often lead to more workload and complexity, this will often introduce many new defect So that the product quality becomes unstable; 2 From the time point of view, it takes at least half a year to start from the demand to the customer to see the product (not necessarily usable. For our market-oriented project team, half a year is enough to quadruple the market, that is, the product cannot keep up with the market.
So we thought about whether we could use some other development models. Since I did not ask for advice from the company, I had to explore it myself. XP was selected at the beginning. Several programming methods: Code Review, standup meeting,
Story wall, Pair programming. But it is really difficult to implement it. Sometimes even if you do not do it, you cannot see the results. In this case, we probably struggled between 4 and 5. A month later, "coincidentally", our project team has been dispatched to the current big project team to create another system. This large project team follows Agile programming ) Is coming to work,
They have invited a very large consulting company to guide the implementation of agile practice. . So we can also take this opportunity to learn agile programing How should we implement it.
On Wikipedia The explanation is as follows: Agile Software Development
Refers to a group of software development methodologies based on iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams.
Let's take a look at the subject and guest: 1 ) Agile development is a development method, but it is not only composed of one method, but is implemented by a group of methods. 2 ) It is developed based on iteration. Baidu knows that this is only part of the design and implementation system at a time,
The step-by-step method is called iterative development,
Each design and implementation stage is called an iteration. That is to say, each time only part of the system functions are implemented, but these functions are complete and users can use them completely. I think iterative development is born in response to unstable requirements. We mentioned earlier that the waterfall development model is very annoying for demand changes, because it is often a global design based on stable requirements, however, once the demand changes, it means that the entire system may change. This is terrible. Therefore, iterative development has emerged. A complete iteration takes about one month. It doesn't matter if the user feels that a function needs to be added or what he wants is not such a page, the customer will be able to see what he wants next month.
An iterative development process is like:
In addition to definitionSet up 4Declaration:
1) individuals and interactions over processes and tools(Individual and Interaction
OverProcesses and tools)
2) working software over comprehensive documentation(Available Software
OverComplete documentation)
3) Customer collaboration over contract negotiation(Customer collaboration
OverContract negotiation)
4) responding to change over following a plan(Respond to changes
OverFollow the plan)
AgileIt is composed of a group of methods. Let's take a look at agile.What are the weapons library:
Total number of forests is about 20Mainstream implementation, we have adopted about 13Respectively:
1) Automated build/deployed
2) Automated Testing
3) coding standards
4) continuous integration
5) Pair Programming
6) card wall
7) User stories
8) refactoring
9) Simple Design
10) test driven development
11) Explain spectives
12) daily stand-ups
13) iteration
