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

We often make some mistakes when dividing iterative versions:

First, be bound by time and fix an iterative period, such as 3 weeks.

Second, pick some functions from the function pool and spell out a version.

This mode of operation often leads to various problems in implementation. This paper recommends two methods of version division, which can ensure that the iteration cycle is divided more effectively and the project schedule is more guaranteed.

First, according to "primary and secondary" division:

This method is suitable for product managers to sort out the main business first and then the auxiliary business when sorting out the requirements.

An iteration period is two to three weeks, if the main business can be completed within three weeks, then the first iteration time will come out, the main business is how many days, iteration 1 is how many days, do not insist that it must be two or three weeks.

If the main business takes more than three weeks, split the main business and put some of the functions into iteration 2, but make sure that the business process of iteration 1 runs smoothly.

Iteration 2 is relatively simple. This iterative version can be determined by picking out other businesses that can be completed in about two weeks and ensuring that all business processes can run through.

The remaining functions are placed in iteration 3, but the saturation of iteration 3 is only about 80% compared with iteration 1 and iteration 2, and if not, squeeze some of the functions into iteration 2. Set aside some time to deal with emergencies or poor cooperation.

About 2 months of the project, send 3 iterative versions, iterative 3 development is completed, all functions are developed, after one or two days of test modification, immediately enter the integration test.

If the project is more than 3 months old, try to make a large and small version, send a large version in two months or so, and a small version in a month or so. This has two advantages:

The boss sees two months of results, then your performance will be stable; people are tired, more than two and a half months of projects, will be less and less confident, the more they do, the more they want to be lazy.

Second, it is divided according to "hierarchy":

Some product managers are in the habit of sorting out requirements according to the level of the interface. For example, first design the first-level page, and then design the second-level page, design the second-level page, run through the main business, leave a few third-level pages, and then design other second-level pages. ......

This design method will bring uncertainty, you do not know which functional modules are complete, which is the actual completion of how much, so it will be uncontrollable. In view of this situation, we can use the principle of "known before unknown" to divide the iterative version.

Engineers with several years of development experience know that first-and second-level pages are relatively simple, mostly lists, so both front and back ends are easy to develop.

Iteration 1, the content of the development includes first-and second-level pages and some functions of the main business. There is a point here, because to do the first-and second-level pages, I feel that I have done a lot of functions, but in fact, his workload will be much less than that of doing the details pages, so iteration 1 needs to press more functions into it.

One advantage of this operation is that iteration 1 development is completed, and the leader takes a look: "Wow, it's almost done." The leader will have a good opinion of the project team.

In iteration 2, the core business should be completed, plus the details of some minor functions. If you can, also press some more functions here, because of this method, the problem is iteration 3.

Iteration 3, the rest of the functions are placed in iteration 3, but the functional distribution of iteration 3 is very fragmented, often missing functions. It is good to do it normally when making the plan, but in the iteration 3 development phase, you should seek the help of the test, and the test gives the functional integrity to ensure that the project is on time.

For more principles and skills in iterative development, please refer to the video course "Project Management from beginner to proficiency: practical experience sharing, practical explanation, project law training".

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.