Project, to ensure that there is a lot of skill development progress, I picked a few of the more commonly used techniques and share.
First, random follow-up
Project progress, project managers, product managers, engineers are free to chat and get to understand the situation, to control progress.
For example, when tired at work, or to pour, it is very casual look for engineers to talk for two minutes, with care, help perspective. Such real-time project manager will be able to find problems where there need to communicate, immediately dispose of the matter, save time engineers.
Product managers can use this method, we look engineers are developing the function of understanding is not in place, there is no problem encountered. Engineers have an idea, product managers can communicate with him and other improvements, this will be less rework and bug.
Note, however, that casual interest, can not be made deliberately monitoring; time not too long, there are things that deal, no problem to get a few words. Otherwise, do you see engineers are afraid to come.
Second, the real function of iteration is complete
We asked engineers to progress, app interface laid end, he will tell you that this feature is done; the background to write the interface, you ask him progress, he will tell you that this feature is done.
But we have a experience that do a good job function, said function test will run feedback unreasonable, or missing a lot of things. For in this case, we require iterative version, you can run a functional test cases.
This must be clear, otherwise the FBI later time will be very long, the project schedule is completely uncontrollable. Because you do not know what is real to complete, which is not completed. So we have to set a completion of the iterative version of the standard is to run the function test is complete true.
Third, the integration of key stage daily version
Project Time Compare rush or there is a time delay project risk, requiring research and development every day after work to integrate a version. Is the code to do the integration, publish to the test environment is like, app hit a packet is sent to the end, no additional workload.
This will bring several advantages:
1. Project the real situation is very clear, time controlled.
This is Agile Article 7 of the 12 principles: the software work is the primary measure of progress, this principle is actually used in the project. We need to utilize these principles together, or hang them on the wall, on the point of no meaning.
2. The engineer will have some sense of tension, development efficiency will be higher.
3. In the process, engineers collaborate with other engineers, test, product, UI, etc. will be more efficient.
This is important, inter-team running a highly efficient collaboration model, this collaborative model in future projects will become the norm, it will improve the efficiency of your project.