analysis - not for placing blame but for figuring out how it could have been prevented. These incidents should also be tracked for trends - is production becoming more or less stable over time? Are process improvements having any effect? One of the most successful test managers I know of consistently receives his requested budget by demonstrating a direct impact on production incidents.
What is the culture in your company? Is everyone so focused on how things look that they are ignoring how they really are, or is honesty permitted, even encouraged, as a means of improvement? Does your management really grasp the risks of cutting quality corners along the way, or do they think they are getting away with it?
Pages
About the author
Linda G. Hayes is a founder of Worksoft, Inc., developer of next-generation test automation solutions. Linda is a frequent industry speaker and award-winning author on software quality. She has been named as one of Fortune magazine's People to Watch and one of the Top 40 Under 40 by Dallas Business Journal. She is a regular columnist and contributor to StickyMinds.com and Better Software magazine, as well as a columnist for Computerworld and Datamation, author of the Automated Testing Handbook and co-editor Dare To Be Excellent with Alka Jarvis on best practices in the software industry. You can contact Linda at lhayes@worksoft.com.
