It's almost a year since I started to work. Here, let's talk about several stages of software development. Companies should have different names, but companies with complete development procedures should have the following stages. The following is my understanding of these product cycle stages ~
Demand Review
At this stage, the product manager (PM) will propose new requirements, such as some new features of the software, describe the motivation of the requirement, and complete the project requirement document) in the future, relevant meetings will be held; R & D personnel (RD) will assess at the meeting whether the new requirements can be met, the work days required, and the impact on product stability, whether there are related functions in existing products, etc. testers (QA) will raise some test questions and opinions to facilitate case reviews in the future. Problems that are prone to at this stage are generally caused by inconsistent opinions of product managers and developers, or problems of trust between the two. I have seen a conflict case like this: a product manager, who once worked on similar products in the previous company, thinks that this design is easy to implement, but what he doesn't know is, the architecture of each company's products is not similar, and the difficulty of implementation is certainly not the same. Therefore, we began to question the RD development capability, and whether we want to be lazy or not, as a result, a conflict occurs. I personally think this situation is actually unsolvable, because it is extremely relevant to the individual characteristics and personality of both sides of the conflict. Only by respecting the work and professionalism of the other party and paying attention to your speech and tone, is the performance of professional.
Development Phase
After the requirements are clarified, RD begins development and implements the relevant functions and completes self-testing before the FC (function complete) deadline. Because of a small function, testers often need to perform several test cases to ensure that their functions are normal. Therefore, developers must leave at least one day of self-testing time for themselves during development, make sure that the operation is normal under normal circumstances, which not only reduces the workload of testers (when a bug is found, after the developer solves the bug, testers need to perform the review). This joint operation also makes their reputation better. So, why not?
Show Case
After the basic functions are developed, other group members are invited to view and comment on the newly developed functions. If necessary, make minor adjustments.
Test Case Review
After completing the test cases compiled by the tester, the tester will call the product manager and R & D personnel to ensure that the case is sufficient to cover the new function and the new function can play its desired effect normally. When conducting a test case review, R & D personnel should consider their own code logic and propose possible situations in the more dynamic code section, make sure that test case fully covers the impact of these changes.
Test phase
After the tester tests each test case and the developer completes the modification of the bug, the developer can enter the RC (release complete) stage. In general, the RC time refers to the deadline for RD to fix all bugs. One thing to note here is that in the pre-RC test phase, the offline test environment is used. After Entering the RC, the online test environment is used for testing. In the test phase, when R & D personnel are prone to conflicts with testers, the common scenarios are as follows:
I. the test case is blocked due to some bugs and cannot be further tested. However, the duration is too long. In this case, you must solve the bug as soon as possible. Otherwise, the release of the new version may be affected. On the one hand, you may also have to pay attention to your tone to ease the mood of the other party, because you have to quarrel with several people, it will not make the progress smoother.
2. Cognition of bugs. In some cases, it is the inevitable result produced by the normal product design. from the user's point of view, the tester naturally thinks it is a bug. At this time, he should discuss and solve the problem with the product manager.
3. self-testing is not completed during development, resulting in a bunch of bugs immediately after entering the testing stage.
4. Bug modification causes problems elsewhere.
In fact, every role is always focused on the team and the product. Therefore, you must restrain yourself from the negative emotions caused by your busy schedule. These negative emotions cannot affect your work. However, if a person cannot control his or her emotions or behaviors, he or she should also stick to his or her own principle of "being a person". What should he do, sometimes it is also necessary to "stand up and fight for your own principles", whether in terms of conversation tone or business mail exchange, is a reasonable way. Sometimes it is precisely because of your persistence in principles that the other party will respect your professionalism.
Grayscale
After this version enters the RC status, after the online environment test is OK, the tester will release the RC report and enter the gray level, gray Scale is mainly used to publish the new version to a small part of users. Due to the differences in platforms and usage behaviors, there may be some product crash and user return problems, depending on the severity of the problem, there may be a gray scale or secondary gray scale, and then the product will be fully released to all users, all users will receive the UPDATE message. The main problem during the gray scale period should be that the feedback bug is generally not easy to solve, and the cause of the problem is mainly that it is not easy to reproduce, for example, platforms used by no users, for example, the operating environment at that time may be very special, and so on. In this case, I want to solve it by experience.
The above is my current experience ~ Thank you for reading ~ Please kindly advise ~
Product development cycle of Internet companies
