My agile Testing

I have heard of agile testing a long time ago. The current company is said to have been engaged in Agile development before, but I don't know why I didn't continue. Now, the testing department is independent of the R & D department. At present, the testing work is arranged and carried out based on the product planning and development submission plan. In addition, the current test team has more or less problems. Therefore, we would like to take this opportunity to introduce agile testing to improve and improve the test efficiency and team effectiveness of the test team.

The preliminary scheme is as follows:

1. Now the test team has more than 10 members and is divided into two agile groups based on the characteristics of the project. Each group is configured with a team lead, which is managed by teamleader and managed by the team lead.

2. Use the requirement template section of the QC management tool to customize it into the test task Management Section (previously, teambition was used, which is indeed a good tool, but the free version has fewer functions, in addition, teambition also lacks statistical analysis for user-defined data. Therefore, back to QC for Task Management)

The QC management system can be used flexibly. The above is only a part of examples. Every time a task comes, the team lead is required to record the task first, and then update the status and Test Progress of the task list every day after work.

3. implement regular meetings every day. The meeting time is set to the first minute of the working time, which is about 15 minutes. Each person will answer the following three points during the meeting:

• What did you do yesterday?
• What are you doing today?
• Do you need help or assistance?

4. A summary meeting will be held after each version is tested and released. The meeting will take about 30 minutes. Before the meeting, let each project tester write more than three points that he thinks he is doing well and is not doing well in testing this version. Then the meeting summarized the above.

5. Small training within the Department. The meeting will take about 30 minutes. It is mainly for internal organizations to carry out some small trainings on good, new testing methods, business knowledge, technical skills, and tool usage. Training meetings are short and frequently used. However, we need to make a training plan first.

In addition, there are good things in cmme, and the document of process specifications and procedures still need to exist. It is impossible to refer to others and make a proper management mode for your team according to local conditions. Control his white cat, black cat, catch a mouse is a good cat.

My agile Testing