Shulou(Shulou.com)06/03 Report--

In the project, there are many skills to ensure the progress of development. I will choose some of the more commonly used ones to share with you.

First, random follow-up

In the course of the project, the project manager and product manager can chat with the engineer at will to understand the situation and control the progress.

For example, when you are very tired at work, or when you go to pour water, talk to the engineer for two minutes and start from the point of view of care and help. In this way, the project manager can find problems in real time, where there is a need to communicate, get rid of things immediately, and save engineers' time.

The product manager can also use this approach to see if the engineer's understanding of the functions being developed is in place and if there are any problems. The engineer has ideas, and the product manager can communicate with him on improvement suggestions, so that there will be less rework and bug.

However, it should be noted that it is casual concern and cannot be deliberately monitored; it should not take too long to deal with things, and no problem can be solved in a few words. Or the engineers will be scared when they see you coming.

Iteration is the true completion of the function.

When we ask the engineer about the progress and finish the interface on the app, he will tell you that the function is done; when the backend writes the interface, he will tell you that the function is done if you ask him about the progress.

But we all have an experience that when it comes to a good function, the test will say that the function doesn't work, or that there are a lot of things missing. For this case, we require an iterative version in which the function can run the test case.

This must be made clear, otherwise the joint adjustment will take a very long time and the progress of the project will be completely out of control. Because you don't know what's really done and what's not. So we need to set a completion standard for the iterative version, that is, the function can run the test case, is the real completion.

III. Daily integrated version of critical stages

When the project is in a hurry or there is a risk of delay, R & D is required to integrate a version at the end of the day. That is, the code is integrated and released to the test environment, and the app end is sent out with a package without additional workload.

This will bring several benefits:

1. The real situation of the project is clear and the time can be controlled.

This is the seventh of the 12 principles of agile development: the working software is the primary progress measure, and this principle is actually used in the project. We must apply these principles flexibly, or it will be meaningless to hang them on the wall.

two。 Engineers will have a certain sense of tension, and the development efficiency will be higher.

3. In this process, engineers will collaborate more efficiently with other engineers, tests, products, UI, etc.

This is very important, teams will run into an efficient collaboration model, this collaboration model will become the norm in future projects, and your project will be more efficient.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.