|
Salary Survey 2002: Are You Weathering the Storm? The results of the third annual STQE magazine/StickyMinds.com salary survey give the temperature of the testing industry. Thanks to our readers' continued participation, we now have three years' worth of data and the ability to start looking for trends.
|
|
|
Karl Wiegers on Software Inspections and Peer Reviews Peer reviews and inspections are among the highest-leverage software quality practices available. Here are some useful sources of guidance on how to perform software inspections and peer reviews, as well as some tools and online resources that can help you jump-start your fledgling review program.
|
|
|
If at First, and Last, You Don't Succeed ... Sometimes, no matter how talented you are and how hard you work, you will not be able to succeed, at least within the constraints you are handed. If your boss says you have to achieve project goals with the resources you have, what can you do? Esther Derby suggests: 1) Start by assuming that a reasonable approach will get reasonable results; 2) If your boss isn't willing or able to hear what you have to say, decide what you are willing to do; and 3) Consider what you might do differently next time.
|
|
|
Delivering Unwelcome News to Developers How well you present a defect to a developer can impact when a defect is resolved–or whether it is resolved at all. Deliver the information abruptly or inappropriately, and you run the risk of alienating a person or creating project hot spots that aren't needed. Deliver news too passively, and your report may be discarded. Karen Johnson describes some ways to soften the blow so that your defects are not only acknowledged, but fixed.
|
|
|
The Art of Influence Abby is a tester who can't seem to make herself heard. She feels invisible in design meetings, and feels like she lacks credibility with the developers on the team. But she learns a few simple changes in her communication approach that improve her chances of being listened to. Elisabeth Hendrickson talks about how testers can learn the art of influence.
|
|
|
All Hands on Deck The challenge: With one week to go before release, the product still needs to be put through its paces. The test team: A few developers, a network engineer, a receptionist, an office manager, and a CTO. In this real-life story, Geordie Keitt explains how one dot-com employed some nontraditional testers to uncover the bugs in their new system.
|
|
|
A Defining Moment People use the word "accountable" a lot lately. But what do they mean? Sometimes "You're accountable" really means "You're to blame for this!" Technical Editor Esther Derby takes a look at what's often the coded meaning behind the word "accountable."
|
|
|
Focused Improvement Improving processes takes planning, time, and effort. A formal improvement project that applies the best practices of development to process improvement can help focus your team and effect real and lasting change.
|
|
|
Managing Technical People (When You're No Techie) There's a lot more to managing software teams than understanding the technology. Do you know how to elicit requirements from users? Do you work well with management? Do you have a knack for asking the right questions at the right time? Not knowing where to put the semicolons in a line of code isn't a big deal. Knowing how to lead people–that's a big deal. Elisabeth Hendrickson explains how to bring your own unique talents and skills to the table.
|
|
|
Should a Manager Know a Language? Knowing C++ or Java can make a manager's job easier. But what about being an expert in spoken language? It's essential to be competent in the use of daily language when you are making the transition to management. Technical Editor Esther Derby gives advice on improving your language, including a warning about the dangers of using absolutes and of leaving out details in conversation.
|
|