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.
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.
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.
Losing your job is never easy, but the way you handle the experience has a direct impact on the results that you'll be able to achieve. Being laid off can make you question your abilities, but you have to roll with the punches, and enjoy your time off while you're looking for the next opportunity.
How can you achieve the lofty status of being an "indispensable" employee? Elisabeth Hendrickson shares some valuable tips, including how to adjust your attitude, where to invest your time, and how to communicate better.
Cem Kaner tells us why we should not use bug counts to measure testers. Using examples, he illustrates two problems: 1) bug counts are poor measures of individual performance; and 2) the side effects of using bug counts as a measure are serious.
Picture the faces around the conference table at your last project meeting. How many women were in the room? And how many of them were testers? Alyn Wambeke explores whether the traditionally male-dominated landscape of testing is changing.
It's wasteful, more often than not, to reinvent the wheel. Christopher Meisenzahl explains how he solved a high-tech automation challenge through the sharing of resources. When faced with similar problems, this sort of collaboration with others may be your most valuable tool—and one that every tester should take advantage of.