The difference between agile and tradition can be realized from finding a girlfriend.

The comparison between Agile software development and traditional software development

Agile Software Development and traditional software engineering comparison, we can simplify, "development" and "engineering" These two parts is just a similar noun, in our comparison can first not to consider, so we have to compare is actually " Agile " and " traditional " difference.

So what is agile and what is tradition?

First of all, we give the following steps for traditional software development

Feasibility Analysis and project development plan↓
Demand Analysis
↓
Overview Design
↓
Detailed Design
↓
Coding
↓
Test
↓
MaintenanceThis is our usual learning Department of the software development process, there is no longer too much analysis.

And agile is literally the first to understand that speed is fast, save time, which is indeed the reason for agile development.

Agile Software development is defined as a software development approach to respond to rapidly changing needs. Based on iterative and incremental development, through self-organization, cross-team, communication and collaboration to complete the development work.

The definition of "agile" corresponds to "the need to respond to rapid change." It seems that the first and foremost understanding is wrong, but is it really?

I don't think so, we seriously consider in our traditional software development, we will encounter rapid change? We have been at the beginning of a long period of feasibility analysis and project development planning , demand Analysis . Then we started to design our software.

Did we analyze it for so long and plan so long that it didn't work?

Have we been doing that for so long that the plan will change a lot in the next few parts of software development?

In that case, it would be a software engineer who snapped his own face. =

So I think that in the traditional software development, we rarely encounter rapid changes in the project. But in the definition, "agile" corresponds to "coping with rapid change", which shows that agile software development from the initial motivation on the traditional software development is different.

Agile development is mainly at the beginning of the time is only a very small form of planning, in the process of development, constantly follow the customer's needs change, requirements change, the function of the software changes.

So I would like to ask big companies, forming enterprises will not know what they want? For entrepreneurs who have been in the market for so many years, it is unclear what kind of software they need. I don't think they need to make any changes to their own needs during the software development process.

At the same time for a large molding company, their work flow is fixed unified, and the top decision-makers are not so much time to constantly deal with the problem of software, so I think that the large enterprises have been molded do not need this software development process needs to change rapidly, they need to be efficient, correct, Product development process.

So what does it take to develop agile?

That is when our project has only one big direction, one main function, and no more details and branches, while we are developing the software while we are at the same time, our software development needs to respond to the changing needs of the project.

I think it is worth noting that the changes we have made at this time are not caused by our software development side, but by the extension of the project.

So for a start-up project, Agile Development is a great fit.

The features of Agile development are:

Human-to-human interaction takes precedence over processes and tools

Software to work with limited documentation for demand perfection

Customer collaboration takes precedence over contract negotiation

Respond to change over time

Such features, coupled with constant changes in the user's needs to respond quickly, so our agile development is to be fast and born.

It benefits our initial project to quickly occupy the market, benefit us to gradually understand our project into the field, but also benefit our gradually evening our products.

So the agility we're talking about is more appropriate for the projects we're developing.

Here we can give an example of the use of these two developments.

Imagine that we are now struggling to find men and women friends .

For the other half of people we look for the other half, more is to hold a try in the heart, is to want in love, gradually understand their needs, gradually formed their own requirements for the other half.

In the continuous deep emotional development, we will have different requirements, different contradictions, we will continue to solve, and constantly find new ways to solve problems, and finally form a perfect couple!

But for those who are already mature and have girlfriends, after breaking up with the other half, there will be a lot of well-planned rules that will know what the other half of what they want to find dead, so he will not rush to start a relationship, but through our feasibility analysis and demand analysis, To decide whether the other half that we need is the one she is, or is she that she is thinking of.

To this we have to know the agile development and the traditional open differences, like our men and women in the same way, no absolute good or bad, in different times, will play a great effect.

Finally in this hope that our classmates can find a suitable for their other half, hope has been found, can be agile "coping with rapid change", running out of a happy couple:p

The difference between agile and tradition can be realized from finding a girlfriend.