The Impacts of Lack of Testing Process
As I wrap up my series on ‘Lack of Process’ I wanted to call attention to, of course, LACK OF TESTING PROCESS.
As a Test Manager at Olenick & Associates, I’ve had the pleasure of working on projects where processes were followed and the learning experience of working on projects where there was not much in the way of processes, or processes were not followed.
I am a big believer in the idea that more planning at the beginning of the project means the rest of the project will go a lot smoother and faster.
The Testing Process is the final quality check for the final deliverable and defines how your customers will perceive how good or bad the deliverable is. I compiled the list below which highlights some of the impacts to a project if there is no Testing process, or lack of following the process:
- Reduces the amount of time available for test execution
- Not all testing artifacts may be created
- Incomplete Requirements Traceability Matrix
- Less defects found
- Defect resolution takes longer
- Scheduling of test environments may be needed
- Resources confused on what their roles and responsibilities are
- Not known what the test data refresh strategy is
- Full test coverage may not be obtained
- Harder to determine what is included in regression testing
- Not clear on when product is ready
- Makes automation more complex
- Increases cost to the project
- Increases resource effort for the project
- Reduces overall quality of the project
From my five posts on processes, I hope I have shown you the impacts to a project if processes are not followed. The impacts are ALL BAD. Some people may think implementing processes adds to the cost and time to a project, but from my experience, they actually reduce cost and time by reducing the amount of re-work in a project.
All five processes are very important. My advice to you is to implement and follow processes and then improve on them in the next projects. The first time following them will not be perfect, but it is a lot better than the alternative.
This list was collected by consultants based on real experiences from projects they have been on. If you want to avoid these types of issues on your next project, then put together a testing process and follow it throughout the project. Stay tuned to the Olenick blog for more from Ken Stawarz on Processes.
For more from the testers point-of-view please check out my previous posts in this series: