Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

What the hell is agile development?

2025-02-14 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Internet Technology >

Share

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

As an engineer, if you haven't heard of agile development, then you may be out. With an attitude of keeping pace with the times, today let's learn what agile development is.

Agile development model has a long history, has been adopted by numerous large companies, such as Google,faceboo and other companies, and recently set off an upsurge of agile development in China. The following is an excerpt from Baidu encyclopedia's explanation of agile development.

Agile development takes the evolution of users' requirements as the core, and adopts an iterative and step-by-step approach to software development. In agile development, the software project is divided into multiple sub-projects at the initial stage of construction, and the results of each sub-project are tested with the characteristics of visualization, integration and operational use. In other words, a large project is divided into several interrelated, but can also be run independently of small projects, and completed separately, in this process the software has been in a state of use.

The core idea is to show the core concept of the product at the lowest possible cost, and to build an available product prototype in the fastest and simplest way. Use this prototype to express the final effect of your product, and then iterate to improve the details.

Suppose your product vision is an advanced travel tool, such as a car. The traditional idea of product design is step by step, starting from a process of wheels, wheels, shell, power plant and interior decoration, and finally get a perfect product. With the idea of agile development, we may first make a scooter or bike to see how much users approve of the travel tool. If users agree with our product concept, we can go on to produce more advanced and perfect motorcycles and even cars.

The traditional product iteration idea has the advantages of high cost, slow speed and high risk, and the product users who spend high cost may not recognize it; the advantage of agile development strategy lies in low trial and error cost, high speed and low risk, which can meet the needs of rapid product iteration.

Agile Development Manifesto:

1. Individuals and interactions take precedence over processes and documents

two。 Working software is higher than detailed documentation.

3. Customer cooperation is higher than contract negotiation.

4. Responding to changes is higher than following the plan

Core values:

1. Communication: it facilitates communication between developers within your team and between your team and your project stakeholder.

two。 Simplicity: drawing one or two diagrams instead of dozens or even hundreds of lines of code, modeling becomes the key to simplifying the software and software (development) process. This is very important for developers-it is simple, easy to find new ideas, and can be easily improved as you deepen your understanding of the software.

3. Feedback: Kent Beck has a very good saying in Extreme Programming Explained: "overconfidence is an occupational hazard in programming, and feedback is its prescription." By communicating your ideas through charts, you can get feedback quickly and be able to follow suggestions.

4. Modesty: the best developers have the virtue of humility, and they always realize that they don't know everything. In fact, both developers and customers, and even all project stakeholder, have their own areas of expertise that can contribute to the project. An effective approach is to assume that everyone involved in the project has the same value and should be respected.

Principles of agile development:

1. Fast iteration: the requirements, development, and testing of small versions are simpler and faster than those of large semi-annual releases. Some companies release only 2 or 3 versions a year, the release process is slow, they still adopt the waterfall development model, and more seriously, there is a misunderstanding of the agile development model.

two。 Involve testers and developers in requirements discussions: requirements discussions are most efficient in the form of seminars. The seminar needs to include testers and developers so that testable requirements can be more easily defined, grouped and prioritized. At the same time, this approach can also make full use of the complementary characteristics among team members. Such identified needs tend to be more efficient, more active and more participatory than the form of a demand discussion meeting.

3. Write testable requirements documentation: start by writing requirements documents using a "user story" (User Story) approach. This approach allows us to focus on requirements rather than on solutions and implementation technologies. Mentioning technical implementation solutions too early can reduce attention to requirements.

4. Communicate more and minimize documentation: communication is a common problem in any project. Good communication is a prerequisite for agile development. The longer you stay in the circle, the more you will emphasize the importance of good and efficient communication. The team should ensure that daily communication, face-to-face communication is much better than e-mail.

5. Prototype the product: it is recommended to use sketches and models to clarify the user interface. Not everyone can understand a complex document, but everyone can read the picture.

6. Think about testing early: thinking about testing early is important in agile development. In traditional software development, test cases are written very late, which leads to the discovery of problems in requirements too late, which makes the cost of improvement too high. Start writing test cases early, and when the requirements are complete, the acceptable test cases are basically completed.

See here, I wonder if the students have some understanding of agile development? Of course, to fully apply this development model to the actual production, we still need to make a lot of efforts, and our students from Ju Media are also actively exploring this new development mode. only in this way can we complete the development work more quickly and efficiently and provide customers with better products.

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.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Internet Technology

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report