Do not simply understand agile development

Agility is an efficient development model, but it is not suitable for any project, and it is not necessary to overturn the current waterfall model to adopt agility completely. What is the essence of agility? What are the core principles of agility? Can the waterfall model use Agile Ideas to optimize the current model? There is no such pattern that it is suitable for any company, any project, or from the perspective of company characteristics and project characteristics. Next we will explain them one by one based on Agile Ideas and look at those suitable for optimizing the waterfall model.

Agility is an efficient development model, but it is not suitable for any project, and it is not necessary to overturn the current waterfall model to adopt agility completely. What is the essence of agility? What are the core principles of agility? Can the waterfall model use Agile Ideas to optimize the current model ??

There is no such pattern that it is suitable for any company, any project, or from the perspective of company characteristics and project characteristics. Next we will explain them one by one based on Agile Ideas and look at those suitable for optimizing the waterfall model.

Agile declaration :?

1. Individuals and interactions are better than processes and tools?
2. Can software work better than all-around documents?
3. Is customer cooperation better than contract negotiation?
4. Responding to changes is better than following the plan?

Agile 12 principles?

1. our top priority is to satisfy our customers by delivering valuable software as soon as possible and continuously .?

This guides us to clarify and refine customer needs as early as possible. of course, it is difficult to fully explore customer needs at one time. However, we can at least try to improve our demand mining and refinement capabilities, each communication with the customer (market personnel) can clarify as many requirements as possible and reduce the number of demand iterations.

2. Even after development, you are welcome to change your requirements. Agile processes use changes to create competitive advantages for customers .?

The background of agility is to respond to the changing needs of customers. in addition to reducing the number of iterations mentioned above, it is also necessary to ensure that the impact of iterations is as small as possible. This requires that the code coupling should be as low as possible.

3. the software can be delivered on a regular basis. the delivery interval can be from several weeks to several months. The shorter the delivery interval, the better .?

The shorter the delivery interval, the more clearly the customer needs. In the waterfall model, we can also guide us to communicate with the requirement introducers and contacts.

4. during the entire project development period, business personnel and developers must work together every day .?

• To ensure the stability of the project, only a stable team can bring about the continuous progress of the project.
• You can also perform a pair test to reduce the amount of communication and ensure the quality through the Module Owner system .?

5. build projects around motivated individuals. Provide them with the required environment and support, and trust them to complete their work .?

The success of the team is inseparable from the support of the project staff and project owners. Provides any required environment and other supporting work to improve the environment reuse rate through environment solidification. Agility is a people-oriented model. it is inseparable from the mutual trust and support of all team members. but this does not mean 100% freedom. Do we still need a spot check mechanism to test the corresponding work results?

6. in the team, the most effective and efficient way to transmit information is face-to-face conversations .?

Reduce invalid communication, improve the quality of communication, and ensure the efficiency of communication. But you don't need to document it. sometimes the project process still requires explicit documents, such as the bug management platform and svn configuration management, to archive, inspect, and perform PDCA .?

7. the software at work is the primary progress measurement standard .?

There are many metric standards for software progress, but don't forget the most important point. we finally want to develop high-quality software that meets customer needs. The requirements can be subdivided into several story, and the build of a function can be considered as completed after the design and test. In addition, the following methods or concepts can be considered for the agile progress: agility can move forward anything that can be done in advance, and Kanban can be used to manage the progress. Doing, done, to do, and so on to understand the tasks that should be completed in a short stage. In fact, such a phenomenon often occurs in projects. a major reason for the above problems is that, I don't know what to do after I finish the previous steps. I can only wait for the owner's arrangement .?

8. the agile process advocates sustainable development speed. Owners, developers, and users should be able to maintain a long-term and constant development speed .?

This must ensure the stability of the project members. this problem cannot occur. the member was called after several days, and the member was called again several days later. In addition, we need to ensure a certain proportion of old and new employees, which not only ensures the sustainable development of personnel, but also ensures the sustainable development of the project .?

9. constantly paying attention to excellent skills and good design will enhance agility .?

Changes are the biggest killer tool of IT and the biggest charm of IT. It is necessary to embrace changes from time to time. what technologies can be used to develop and maintain new features more efficiently.

10. simplicity-the art that maximizes unfinished work-is fundamental .?

Complex things are simple and an art. many times a js page and a cgi are designed by developers to be quite complex. if you can start from a trivial matter, simplicity will not be far away. However, this may require some training and sharing systems.

11. the best architecture, requirements, and design come from self-organizing teams .?

The high coupling of the current code is due to a problem with the software architecture at the beginning. if a company has the same architect (of course, the ability must be up to standard), it has a good architecture, the low coupling of modules may not be empty talk.

12. at regular intervals, the team will reflect on how to work more effectively and adjust their behaviors accordingly .?

In the three provinces of a day, we often need to summarize and reflect on our work, so that we can make better progress at a new starting point. Don't begin to summarize after the project is over. I should always summarize why I didn't find such a bug, why is the test efficiency so low, and only the reflection summary can make progress .?

In fact, there is nothing wrong with the waterfall model. if you want to make sure that the right thing is done correctly for the first time, and then optimize the current work with agile ideas, I believe it will be much better than simply using agile "ism". The most important thing is to understand Agile Ideas. In addition, complete agility requires the strong support of the company's various platforms (automated and public technology platforms). if it cannot be completely agile, it should start from semi-agile, and consider what can be agile at present, yes. start with local agility first .?

This article is available at http://www.nowamagic.net/librarys/veda/detail/2040.