45 Habits of efficient programmers-delivering the software users want (Ⅳ)

The real enemy is the change!!

First, let the customer make the decision:

One of the most important decisions a developer (project manager) can make is to decide which ones you can't decide, and to let users make decisions.

When discussing with the customer, prepare several options to describe the pros and cons of each scenario from a business perspective, as well as the potential costs and benefits, and discuss the impact of each choice on time and budget, and how to weigh it.

Second, let the design guide rather than manipulate the development:

The prophase design belongs to the strategic design, should not specify the procedure method, the parameter and so on details, should play the map role, guides you to the right direction forward;

Tactical design needs to be carried out in the process of specific project development;

CRC (class-duty-collaborator), class name-what it should do-to work with what other objects;

A good design should be correct, not precise, and everything it describes must be correct and should not involve details that are uncertain or may change;

Third, reasonable use of technology:

Select new technologies as needed;

Don't develop what you can download;

Four, keep can publish:

Keep your system ready to compile, run, test and deploy immediately;

Five, early integration, frequent integration:

Code integration is the main source of risk, early integration, continuous and regular integration;

Vi. early implementation of automated deployment:

The installation or deployment of the system should be simple, reliable and repeatable;

(from the outset) implement automated deployment applications;

Vii. Use the demo to get frequent feedback:

In the development, keep the application visible, actively obtain feedback;

Viii. using short iterations, incremental releases:

The best way to deal with big projects is to move in small steps;

Ask the customer, which is the core function that makes the product usable and indispensable;

With short iterations and incremental development, developers can be more focused on their work;

Incremental development, the release of products with the smallest but available function blocks, the incremental release must be available, and can provide users with value, which requires us to ask customers more;

Nine, fixed price means betrayal commitment:

The initiative proposes to build the initial, small and useful parts of the system, enough to pay once, and allow the user to actually use it;

Let the customer choose after the first iteration to continue the next iteration or cancel the contract;

If you move forward, you can predict the next iteration well and let the user make a choice when the next iteration ends;

The advantage of the above three points is that you can control the project, can stop the project at any time without the need to spend more money, but also can control what to do first, and can accurately know how much to spend, so that customers assume a lower risk.

　　　

45 Habits of efficient programmers-delivering the software users want (Ⅳ)