In the previous article, we highlighted the importance of test documentation review within a testing team. But there are many other interesting insights learned from our practical experience.
Let’s imagine a situation when QA engineers partitioned the functionality or platforms among themselves. Everyone is responsible for his own direction, and it seems like a great scenario. But, all of a sudden, one of the specialists goes on vacation, or even worse, leaves the project.
Logically, all questions and activity get divided among other QA team members, who only in general terms can tell what is happening with this or that functionality or on the specific platform.
Panic, overtime, redistribution of the workload inside the team to minimize risks and stress. Quite an unpleasant situation.
To avoid it, we apply team members repositioning by features. How it works? Read more here.
Have your own suggestions or best practices to showcase? Feel free to share your ideas in the comments below.
コメント