Articles about planning software testing and managing it.
Point of views:
When testing business critical software, the testers are most often business professionals, people, who test alongside their own work. They are usually not testing professionals. Resources are “bought” from the business for development project. In this post I give tips to make a resource plan that includes valid arguments for the business.
Tester’s work day includes different activities:
In Finland the average office work day is 7.5h/day. Because the other activities take a part of this time, the value I use when planning resources is 5.5h effective testing per day.
Test cases in acceptance testing are all different, but can usually be divided into two main categories: End-to-End test cases and testing a single function.
Counting resources, I usually set basic time for these, since estimating every test case is time consuming. For example:
Part 1/11 I write about the work load caused by testing observations.
In this next calculation of the need of resources, I use 157 as the number of observations. From these the work load for testers is approximately 315h.
When we know the things listed below, we can make calculations of how much resources we need from the business.
What’s important, is that you have a calculation that helps you prove the need for resources. Otherwise you might get into an argument about the necessity of the resources asked.
An Example:
When you make the calculations and look at the calendar, you really need to plan how the testing will go. I close my eyes and imagine the events of the testing day.
When planning new testing, you can go back to your previous plans and see how the plans were realized. Did you put too much or too little in resources the last time? Now you can specify your plan based on observations.
There are usually many projects ongoing at the same time. With good planning, you can have right resources for the strategically critical project.
Don’t make your plans too tight. Every testing day without surprises is a surprise.
The next part will tell you how to make the best use of resources.
Download a guide on software testing in development projects. You’ll avoid many common mistakes and succeed in the implementation.
Improved testing efficiency, 70% less emails and real time reporting
Easily plan and execute even the most challenging development project