Project management lessons learned

1.The customer's requirements are always changing, and they always think that the changes are small and the development team should accept them;

2.From the very beginning of development, we should prepare for system deployment and be ready to deliver it to customers for trial use at any time, instead of waiting for the final release, it is very likely that the system running well on the development machine cannot run in the actual environment;

3.The development cycle, cost, and project quotation must be multiplied at least by the initial estimate.1.5We are always optimistic about it;

4.Establishing a platform for communication with customers is crucial to ensure that the development team and customers have a unified understanding of the project progress;

5. Design documents andCodeWith the development of the project, some "designs" may change in actual development. The consistency between the two should be maintained, but the document workload should also be controlled within a certain scope, after all, the most important thing is code;

6. problems found during software (module) Functional testing during development should be recorded at any time, for future review and generation of test documents (reports)