Agile development practices study Note 3: deliver the software you want

There are no plans that can be continued after an attack.

Our real enemy is change.

Allow Users and customers to participate in developmentImportant.

Habit 10: let customers make decisions

One of the most important decisions that developers (project managers) can make is to determine which ones cannot be decided by themselves and let the business owners make decisions. You don't need to make decisions on key business issues. After all, that's not what you do.

When discussing with customers, we should not introduce the advantages and disadvantages of each solution from the technical perspective, but also the potential costs and benefits from the business perspective.

Habit 11: give design guidance instead of manipulating Development

Design Documents should be as detailed as possible. At the higher level, the relationship between objects is described in detail. at the lower level, interaction between objects is described in detail.

Draw a key work diagram (using UML) Because classes and their interactions are used to describe how the system is organized. Then start encoding.

Do not waste time designing specific details before coding..

Card design method: Class Name, responsibility (What should it do), co-author (to complete the work, he wants to work with other objects)

A good design should be correct, rather than accurate.

Habit 12: rational use of technology

Select technology as needed. Do not blindly select technology and framework.

Can this technical framework really solve this problem?

Will it hold you down?

What is the maintenance cost?

Any technology has advantages and disadvantages and must be clear about its advantages and disadvantages.

Do not develop things that you can easily download

Habit 13: Keep Publishing

At any time, as long as you are not ready, it is the best time for the enemy to attack you.

When working in a team, you must be cautious when modifying things. Every change affects the system status and the efficiency of the entire team.

Preventive Measure: perform a test locally; check out the latestCode; Submit code

Version Control Management: CVs, subversion, git

Habit 14: early integration and frequent Integration

The main risk source during code integration. To avoid this risk, only early integration, continuous and regular integration is required.

Habit 15: automated deployment in advance

Habit 16: Use the demo to get frequent feedback

Inconsistency is a major cause of misunderstanding.Clear and visible development

Habit 17: use short iterations and incremental releases

Iterative developmentYes. In a small and repetitive cycle, you have completed various development tasks: analysis, design, implementation, testing, and feedback. This is called iteration. The end of the iteration marks a milestone.

Software development is not a fine manufacturing industry, but an innovative activity.

The best way to deal with large projects is to move forward with small steps, which is also the core of agile methods.

Ask the customer about the core functions that make the product available and indispensable. Don't be distracted by all the gorgeous functions that may be needed, don't indulge in your imagination, and do those flashy user interfaces.

With short iterations and incremental development, developers can focus more on their work.

Habit 18: a fixed price means a breach of commitment

Method: We propose to first build the initial, small, and useful parts of the system. After the first iteration, let the user choose.