The management layer requires that all bugs be tracked and handled through RAID (product studio. This seemingly simple bug management tool is an important guarantee for effective collaboration between employees and other colleagues.
Each product is divided into modules (areas, subarea). Each module has three roles: a clearly defined requirement definer (PM), a Development Engineer (Dev), and a test engineer (tester. If a problem occurs, it will be tracked and handled by a certain person. No primary bug will occur.
The spec written by PM is a contract for this feature to guide development and testing. When Dev and tester dispute over a bug, PM is responsible for providing a clear explanation
Testing is not just about tester, although it is their full-time work. Everyone in the R & D team is obligated to notify the testers in charge of this module to track the bug every time they discover a product problem, or simply create a new bug to track the bug.
You can create a bug and assign it to yourself to track the handling of something. For example Source code A bug is recorded in, and time will be taken to handle it later.
All people in the team can create, assign, and change the bug status.
When you create a bug, the description must be detailed enough so that the following persons who handle the bug and other colleagues who care about the bug can accurately reproduce the problem through the bug description, instead of guessing some steps or running them to ask you in person
Generally, a bug is handled like this:
1. tester finds a problem and creates a bug in raid to describe the details of the Bug, such as repro step, result, and expected change) and run the version. Then, assign the bug to the dev lead responsible for the module.
2. Dev lead assigns this bug to a specific Dev after judgment.
3. Dev processes the bug and returns it to the original tester, or requests the PM to provide a clarification description.
The management layer uses raid to track the overall progress and the contributions of each employee and team.
A dedicated person sends bug status reports to relevant colleagues on a regular basis
You can easily query the distribution and handling of bugs on your own. The bug management system opens the door to all team members without reservation (except that you cannot delete bugs, and all operations are faithfully recorded)
Over time, the management should gradually provide clear guidelines for solving bugs: Which bugs can be ignored (won't fix ), which of the following versions can be postponed to the next version (postponed ). For example, in the weeks before the final build, there may be very serious bugs, such as data loss, Program Crash and other issues must be postponed to the next version.
When frontline employees have disputes and fail to reach an agreement (although this is rare), the management should quickly give a comment.
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.
