Several project experiences summarized by PPP projects

These are basically learned from the boss and play a positive role in the PPP project. I think they are at least suitable for small projects of about six people. Some are not regarded as experience or recognized best practices.

1. obtain detailed requirements as much as possible. It is best to draw the interface first for the customer to confirm and form a document. After all, modify static InterfacesProgramIt's much faster.

2. A dedicated person is responsible for keeping in touch with the customer throughout the process. This person is neither designed nor programmed. If the customer's personnel are allowed to participate in the project, the maintenance work after the project is completed can save a lot of effort.

3. Establish two sets of version control and one set is responsibleCode, A set of documents. Before delivery, you must completely simulate the customer environment for testing, starting from installation.

4. It is very important to establish a bug tracking system and conduct tests by dedicated personnel. Most of the time for the PPP project is five-person code. For one test, testers do not feel enough at every day.

5. If you believe that the changes made by the customer should not be modified, submit the reasons. However, you cannot reject all such requirements. You can modify those that do not affect the model.