Hua Fu small Loan project from 2016-10-26 :30–15:30 after the conference call officially started, the project plan:
2016-10-31 prior to work, contract priority
2016-11-2 UI Design Complete
2016-11-11 Interface Development Completed
2016-11-18 Development Completed
2016-12-2 contract
2016-12-30 Online
Need to develop the interface 28, wherein the forwarding interface 14, hard-coded interface 14. As of today November 13, the forwarding interface 14 interfaces are all complete, hard-coded interface 14 complete 7. The hard-coded interface is only half done.
These are the reasons for the deviations in the project from the plan:
1. The project plan needs to be scientifically evaluated, and the development workload must be sorted out at least, and the evaluation based on the difficulty of the interface may be reliable. Unfortunately, the conference call, a pat on the head gave a November 11 time to complete the development. This is a profound lesson. The project plan must be carefully followed.
The project manager's accusation is to do as much as possible to the needs of the fine, and try to give the project more time and resources, on the actual case, 11 days to develop 14 interfaces, the difficulty is relatively large.
In terms of actual development experience, the time required for development is as follows:
(1) Forwarding interface, development workload (0.25 people/day is mainly resource application)
(2) Simple interface with clear requirements, workload (2-3 people/day, understanding of business and design 1 days, code 1 days, test 1 days)
(3) Complex interfaces with clear requirements, workload (7-10 people/day, understanding of business and Design 2 days, code 3-5 days, test 2-3 days)
(4) Simple interface with unclear requirements, workload (7-14 people/day, preliminary development of 7 days, rework redo once 14 days)
(5) The complex interface with unclear requirements, the workload (14-28 people/day, the initial development of 14 days, rework redo once increased 7 days, rework more than 2 times is basically a failure of the project. )
2. Requirements---design----development---testing, which is an essential four steps of software development, these four steps are interlocking, the previous step is not done, the work will inevitably have problems. The problem with this project is in the demand and design process,
It was not until November 11 that people were urging delivery to communicate with others about uncertain issues. It was a long day, but it was a little late.
3. Don't be afraid to communicate, don't avoid problems. The problem with many software projects is the uncertainty of demand, and the only way to determine demand is to communicate. In fact, this small loan project has a lot of resources, the front-end of the head of the business quite understand, testing can also provide some help. But when the demand is not clear, the problem is easy to let go.
4. Do not assume that you are responsible for all things alone. The most important responsibility of the project manager is to control the project progress, communication and coordination. It is not a matter of the project manager to make a thorough understanding of the requirements and to design all of them. This demand and design, did not let everyone involved in, but want to own a person to all the needs and design, this is too idealistic.
5. There is a little slack and procrastination. The actual situation of the project team is that everyone does not understand the business, and some people do not have enough enthusiasm. In this case, the project cannot be completed until the site supervisor is staring at their progress, controlling and resolving problems in real time.
The last one, remember, the problem is never hide, although we can temporarily avoid the problem, but the problem will eventually appear. No matter what you do, a positive and responsible attitude is the guarantee of success.
Small Loan Project Management summary