test management
Articles
|
When Being Correct Isn't Enough It makes sense that people who are always correct will have the power to influence others. But testers who base their authority on correctness might be in for a rough time. Bret Pettichord explains in this week's column why it's a good idea to show concern as well as correctness. |
||
|
Evaluating a Tester's Effectiveness Test managers are responsible for monitoring the testing program and the people who carry it out. But with all that testing entails, evaluating a tester's performance is often a complicated task. In this week's column, Elfriede Dustin provides some specifics you can use to assess the effectiveness of a tester. |
||
|
Now that the Worse than Worst Case Has Happened QA professionals get paid to envision bad things happening and to make others aware of risk. But the terrorist attacks and all that has followed illuminate what truly horrific things can happen to any of us. As a New York resident and QA professional, Patricia Ensworth shares her perspective on coping and positively focusing on QA issues that can help secure a project, organization, and the community at large. |
Patricia Ensworth
January 4, 2002 |
|
|
Understanding Both Sides of the Test Tool Fence A natural divide exists between those who develop commercial test tools and those who use them. If you're tasked with finding the right test automation technology and tool for your organization, it helps to understand how high this fence is (or should be). This article explains the nature of this fence, how it varies in different types of tools, and what you can look at to get a view of the other side. |
Steve Morton
December 13, 2001 |
|
|
Risk Analysis Basics Have you ever had a challenging time trying to get a manager or coworker to recognize a potentially project-stalling issue? Risk is inherent when creating something valuable and complex (like software), but sometimes it's hard to analyze and explain in a productive way. Here Johanna Rothman shares her method for addressing risks. |
||
|
Software Test Plan Template IEEE 829-1998 Format (template) This Software Test Plan template is based on the IEEE 829-1998 test standard specification and additional information added from various sources—actual test plans, instructor experience, student comments, etc. |
||
|
Master Software Test Plan IEEE 829-1998 Format (template) This Master Software Test Plan template is based on the IEEE 829-1998 test standard specification and additional information added from various sources—actual test plans, instructor experience, student comments, etc. |
||
|
Measuring Performance Against Management Deliverables Prompted by a comment from our sticky-minded audience, this week Johanna shares some ways test managers can assess their performance against specific management deliverables likely to be high on an organization's priority list. |
||
|
Across the Great Divide Many bemoan the strained relationship between testers and developers. But while we can't force testers and developers to see eye to eye on everything, we can reduce some of the tension by making simple changes in the way we communicate. Learn some great tips and tricks in this article. |
Susan Joslyn
June 18, 2001 |
|
|
Testing Justification Checklist (Template) This checklist summarizes the steps for securing an investment in testing. The process is neither sequential, nor automatic. That's part of the point. This is essentially a mechanism for securing investment (resources and commitment) to produce some value for the organization. |
Pages
Recommended Web Seminars
Featured Resources
Visit Our Other Communities
StickyMinds is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.