Over a period of three weeks we are looking at creating software test plans that actually make a difference, in an easy step-by-step formula. We are covering the three main areas you need to consider as part of software test planning, as well as 12 checklist points that should be addressed in every software test plan. In this third installment we consider how you get people to act based on the information you write in your test plan.
~~//~~
How do I get people to act?
All too often a test plan will be written and then forgotten about. Without action, however, you’ll never achieve the goals you set out to accomplish.
In order to get going you need to tell people what action they need to be taking. And you can’t do that unless you proactively circulate the information in the test plan.
Approaches for improving the distribution of the information in the test plan include:
#7 Identify responsibilities
In each area of the test plan, list the people who will find that section most relevant. When you identify the sections that are most pertinent for specific team members, then they only need to read that particular section. This will save your team time and frustration (because they won’t be forced to read information that doesn’t apply to them). For example, the test task section may only be applicable to the test analysts and testers.
#8 Hold regular update meetings
When you have completed the test plan draft, or when you make significant updates to the test plan, hold review meetings to go over the updated information. With the amount of information people are expected to absorb these days it’s not unusual for a 30-page document to go unread by most people.
Holding update meetings means that your team is forced to take some time out to process the information you’re trying to get across.
#9 Refer to the test plan regularly
When in project meetings, team meetings, or casual conversations make sure you regularly talk about the test plan and what will need to happen to get it done. This helps increase the visibility of the plan and emphasizes the importance of the information it contains.
#10 Increase the visibility on your intranet
Get a link to your test plan placed prominently on the project web page and ensure that each time the test plan is updated that the link gets highlighted again. Increasing the visibility of the test plan so that people have easy access to it is essential. Don’t just leave it in an anonymous directory on a server somewhere and expect people to find it.
#11 Translate the plan into a To-Do list
Turn all the possible pieces of information in the test plan into a To-Do list that you can reference on a regular basis. Assigning completion dates and owners to each action helps ensure that each task is assigned to a single person with the aim of completing the action by a certain date.
For example, you might have identified a certain risk area within the application. What you should do is assign a tester to review that risk on a monthly basis with the appropriate developer. This is something that would go on your To-Do list.
Review and update your To-Do list on a regular basis.
#12 Consider outside help
Use an application like QaTraq to organize all of your information in one place, and to help keep your test plan in front of your team on a daily basis. QaTraq can help you and your team:
- Improve the quality of your product releases. Because you can report on and track your testing against the test plan, your products will be of higher quality. This means you’ll improve the reputation of your company and increase your product credibility.
- Reduce support cost. When you can identify quality issues earlier in the development process, you don’t have to spend as much time mired down fixing problems that customers report.
- Reduce the time to market. With QaTraq, it’s easier to prioritize the testing so you don’t waste time testing the functions that really won’t make a difference.
- Easily pull together information to support the release decision. We can provide you with reports to identify the quality of your product and the coverage of the testing.
- Quickly see who is responsible for testing what, and see the progress they are making. With QaTraq you can clearly assign work to testers and track their progress, which saves you time and frustration.
~~//~~
Conclusion
Writing a test plan isn’t always easy. Many people struggle with the process. You might have started one in the past, only to stop because no one was reading it, let alone using it to guide their day to day testing efforts.
If it’s not done right then yes, a test plan can be a huge waste of time. But, it doesn’t have to be. If you can put the right information in the test plan, get the information from the right sources, and inspire people to act then a test plan can be well worth the time you put into its creation.
Finally, don’t forget that the test plan should be a living document. Update it on a regular basis, and keep your team in the loop every time there is a significant change. Don’t expect everyone to just read the test plan when you email them a copy; talk to your team about the changes, keep the test plan accessible and follow up with them to make sure they’re staying up to date.
What to do next
Traq Software have developed QaTraq Professional to help test teams take control of their testing, to help you keep your test plan in front of your team and to get your test team following your test plan. QaTraq Professional is one of the leading test planning tools available today, providing the foundation that teams need to create and track test cases, test plans and test results.
To sign up for a free 30 day hosted trial account for QaTraq Professional just click the link below, sign up and we’ll send you your account details in an email. This 30 day free trial gives you immediate access to one of the leading test plan management applications.