First, the agility of seven areas
- Agile guidelines and ideas
- Value-driven delivery
- Stakeholder involvement
- Team Performance
- Adaptation plan
- And solve problems found
- Continuous improvement (product, process, personnel)
Second, the Agile Manifesto:
We are helping them through hands-on practice and reveal better ways of developing software by this work, we believe that:
个体和交互 胜过 过程和工具
可以工作的软件 胜过 面面俱到的文档
客户合作 胜过 合同谈判
响应变化 胜过 遵循计划
The right term although valuable, but we think the items on the left have a greater value
Third, the classification of the Agile Manifesto:
See generally Agile core 4 declaration sentence, in fact Agile declaration sentence is 3, i.e., the interior can be divided into three parts Agile declaration usually "4 + 1 + 1" mode
- 1: "We are through hands-on practice and help others, reveal better ways of developing software." This sentence illustrates the use of direct background of the Agile Manifesto, that is, to the best practices in the software industry / IT Internet industry.
- 4: 4 declaration, using "A better than B" mode, not the simple choice. A not recommended not to use B. But A and B are to be recognized in the same project, we need more focus in terms of A
- 1: "Although the right item has value, but we believe that the left items of greater value." This sentence is easily overlooked, most people understand agile when deviation will be easy to understand, for example, you would not think agile required documentation, or agility does not require a contract, does not need to process. This one went into the ditch inside. I guess this should also be a test center, such as agile sponsors believe that the right term processes, documents, contracts, plans are still needed, just to remind you interact concern items on the left more in the implementation of the project, the software can work , customers, respond to changes
Fourth, the Agile Manifesto Category:
Let us understand the agile four-Declaration
1. Individuals and interactions over processes and tools
Processes and tools are in need of our project, the purpose of the team is focused on individual participation and interaction. Project is done by people, not by the tool. It is difficult to solve by people, not by the process. Similarly, the project was done by a human, the scope is determined by the people, by the people to project success is defined. Individual participation and interaction is conducive to the success of the project. However, it does not mean that processes and tools for the success of the project and did not help, but these are important organizational process assets. We have engineering backgrounds, they will naturally tend to meet and logic of processes and tools to bring. However, the project ultimately related to the people, so to be successful, we need to spend a lot of time to perfect some areas unpredictable. The first values "Individuals and interactions over processes and tools" will help focus the individual's time, energy and passion.
2, working software over comprehensive documentation
Software projects can create value, high-quality software primary target. However, many people are often too much attention to some temporary deliverables, such as general documents, but not too concerned about the ultimate goal of the project support software can work. No documentation software described certain problems and obstacles will appear on the technical support and maintenance, but only well-documented but did not complete the software for any organization it is of no value. Therefore, the document is needed, but the need to grasp the degree of them.
In large team, complex software systems, problems often arise such as free text left. Therefore, in such an environment, the document is required. Many software developers will pay attention to detail and process, although these can bring high returns, but developers will focus personnel away from the original intention of software development projects ---- complete working software. So Agile Manifesto "working software than comprehensive documentation" to remind members of the target ---- project worth more focus to the project. If you focus too much on the document at the expense of working software, the document is useless, worthless.
3. Customer collaboration over contract negotiation
It reminds us that the values of this article need to be flexible and inclusive, but not rigid, like "doing things right" and "do the right thing." We can be done in full accordance with the provisions of the original product, once customers change their minds or priority, the best thing to do is to complete the new goals through a flexible approach, instead of the original provisions to fight.
Knowledge is dynamic project, especially software system; software is intangible and difficult to reference, each software is unique. Rapidly changing needs of the outside world, technological innovations very quickly, we should recognize events will be changed, the common definition of customer "Finish." This will depend on mutual trust and a more flexible contract models, but also need to focus our work is never value-added activities (such as the debate on the scope of) transferred to the richer valuable work.
4. Responding to change over following the change
Follow the plan refers to the act according to plan, the middle may need to take corrective measures, intended to make the expected future performance of the project plan and do everything the same. In response to change is the adaptation process, through superior ideas and constant feedback to adaptation measures, adaptation is a response to the purpose of practice rather than a scheduled basis, is not the correct response.
The initial plan is sometimes not completely perfect. If we try to project implementation as originally planned, then we will put in more effort to respond to inevitable changes, therefore resulting in the effort will be wasted. But the Agile Manifesto does not suggest we have to respond to changes and completely abandon the project. We need to plan for the project, and we have to understand that the initial project plan is the beginning of our making, as the process of work, we need to continue to update a lie. So, Agile advocate 5th floor plan. About 5 floor plan, and then explain in detail later.
"Responding to change over following a plan" is particularly important for software projects there is a high rate of change. Similarly, we instead suppress change and a lot of time and effort by a corresponding change to follow a large-scale plan. Agile projects with high visibility work queue to form plans dos and task Kanban. Thrust is to promote the values of agile adaptation planning requires full participation.
Fifth, the Agile Manifesto Summary:
Agile Manifesto to guide us to value-oriented implementation of the project. We also need processes, tools, documentation and plans, however, with respect to these, we need to focus more focused on the people engaged in the project, ongoing product, cooperation and flexibility.
Author: talk of the town next door to the first
link: https: //www.jianshu.com/p/f9f2cbf688a4
Source: Jane book
Jane book copyright reserved by the authors, are reproduced in any form, please contact the author to obtain authorization and indicate the source.