For example this month has 2 version plan in March, 0315 version and 0331 version,
Then 0315 is our development submit completed (including development self-test), delivered to the test,
Then on into the 0331 version of the content of the development and design, coding,
0315 version of the test questions at this time, and then into hotfix1 [0315] of the version to come in, for example, that when doing the 0331 version are both 0315 hotfix1 problem, so repeated iteration, what's wrong with the feeling, because after 0315 delivery, actually there no repair test found that the problem of time, but the default think [development should submit code is to ensure the quality of highly, at least in the hotfix content not many]
So this version plan once roll, is a vicious cycle of didn't play didn't, hadn't done the latest version of the hands, on a version of the hotfix problem came out again, multiple versions development at the same time, combined with code, the last little time alignment, point to finish development is good, and lead to poor quality
Don't know everyone development work at ordinary times, what is the version?
CodePudding user response:
It is because work schedule too much, so in this way,As a project manager, must want to control good,
If 03-15 is a milestone, it must be a real node can release without big problems,
Development should be as before so 03-10, 3-10 to 3-15 specially used to test and solve the bug,
If not solve, that will be appropriate delay the release time,
If you cannot solve the short time, delay to 3-31, one dedicated to solve the bug, the other people to do something new,