Shulou(Shulou.com)06/03 Report--

Question: what is the fundamental foundation of agile development? What is the essence of Agile Software Development?? From the LinkedIn hot post http://www.linkedin.com/groupAnswers?viewQuestionAndAnswers=&discussionID=156452723&gid=37631&commentID=93678048&trk=view_disc&ut=3OEFTrlSNevlo1, you can also go to the above to take a look at the discussion of foreigners.

The moral Sutra says that Taiji gives birth to two instruments, two instruments give birth to four images, four images give birth to eight diagrams, eight diagrams give birth to 64 diagrams, and 64 diagrams give birth to all things.

But the agile development of most enterprises is too "gossip", can not grasp the root of tai chi, can not derive everything according to the specific situation of the enterprise. There are enough other articles on the blog to describe "everything". This article only talks about Liangyi.

In the previous post, several people supported fast feedback/short iteration, while others supported transparency/teamwork, which together are the two most important aspects of agile development.

Answer: continuous improvement + teamwork

If you use the authentic agile development vocabulary, these are the two.

Continuous improvement includes quick feedback, continues integration, daily buiding, standup meeting, short iteration, refact, working software, etc.

Teamwork includes stands for cross-function team, focusing on customer's value (treating customers as part of a win-win or even win-win team), selforganized team, test automation (developers do testing)

Here is how the two correspond to the 12 Agile principles:

Continuous improvement 1: Our highest priority is to satisfy the customer through early and continuous delivery of valuable software

Deliver valuable software early and continuously to meet customer needs.

3: Deliver working software frequently, from a couple of weeks to a couple of months, with a preference for the shorter timescale

Often release available software at intervals ranging from a few weeks to a few months, as short as possible.

7: Working software is the primary measure of progress.

Available software is the main indicator of project progress

8: Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

Agile processes should be able to maintain sustainable development. Leaders, teams and users should be able to continue to work together at the current pace.

10: Simplicity--the art of maximizing the amount of work not done--is essential.

It is extremely important to keep concise-the art of simplifying the workload as much as possible. Maximizing the amount of work not done in English. My understanding is that any work that is not yet clear will take an unknowable time, so maximize, do not confuse the work that has not been done with the work you are doing.

12: At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

Always summarize how to improve the efficiency of the team and put it into action.

Teamwork: 2: Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage

Agile processes welcome changes in requirements and use them to improve the competitive advantage of users.

4: Business people and developers must work together daily throughout the project.

Business people and developers should work together every day during the development of the project.

5: Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

Take enterprising people as the core of the project, fully support and trust them

6: The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

Face-to-face communication is always the most effective way of communication, both inside and outside the team

9: Continuous attention to technical excellence and good design enhances agility.

Only by paying constant attention to technology and design can we become more and more agile.

11: The best architectures, requirements, and designs emerge from self-organizing teams.

Only a self-managing team can create excellent architecture, requirements and design.

Putting customer and business value into teamwork seems a bit far-fetched, which is why I prefer to use "selfless". "team" is easy to confine people to the content of the development team, in fact, teamwork is saying, "Don't just think about me" or even "Don't just think about us (and think about customers)."

Here are two images generated by continuous improvement: http://blog.csdn.net/cheny_com/article/details/7190094

And the two images of teamwork are here: http://blog.csdn.net/cheny_com/article/details/7189757

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.