|
A Selection of "Our Take" Columns "Our Take" is a regular column from the editors at Software Quality Engineering. It appears in the twice-monthly StickyLetter since its inception in September 2000 (originally "STQe-Letter"). From jazz music, to car troubles, to the Lewis and Clark expedition, Robert Rose-Coutré, former StickyMinds.com Editor, will use anything to make a point about building better software. The editors at Software Quality Engineering have compiled a collection of some of these pieces. Musings from StickyLetter's "Our Take" are presented here.
|
|
|
Make Your Point—Without Pointing a Finger When errors are not detected during testing, somewhere down the line someone has to take responsibility. In this column, Linda Hayes shows you when and how to do so—and you might even be able to turn the situation to your advantage.
|
|
|
Did You Hear What I Said? Software projects are complex endeavors that rely on clear communication for success. If communication methods are mismatched or leave too many gaps, your project could suffer, and you could be highly frustrated. In this column, Karl Wiegers details potential problems to be mindful of, and strategies to use, when communicating about a project.
|
|
|
Testing Your Worth There's no doubt that the current job market is tight and a little shaky for test professionals. In a climate where entire test groups are being laid off or trimmed to the bone, Johanna Rothman notices a trend in test management priorities that you might want to consider. Follow the story of how one test manager determined tester ROI and how testers might approach increasing their value.
|
|
|
The Problem Isn't Always THE Problem When things go awry, sometimes the first problem you see is not The Problem but just a product of its symptoms. But if problems can hide behind other problems, how can you learn to spot the true culprit at the source of your dilemma? Elisabeth Hendrickson shares some lessons she's learned about "The Problem."
|
|
|
7 Keys to Building Great Work Teams Successful projects depend on how well the team works together. Elements that lead to success include commitment, contribution, good communication, and cooperation. Cooperation itself includes factors such as follow-through, timeliness, and others. Conflict management and change management are also important. This article analyzes and explains all of these elements that constitute a productive and successful team.
|
|
|
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.
|
|
|
Conducting a Temperature Reading Negative mindsets and instances are so easy to fall into, and it can be difficult to see the positive in things. By using the "temperature reading" technique, a completely attitude and outlook turnaround time can be achieved in very little time. Learn this easy method for improving your mindset.
|
|
|
What Could Possibly Go Wrong? A software project is a complex thing. It involves many players, many tasks, and lots of things that could go wrong (and often do). If not for dogged optimism, some projects might not be tackled at all. But optimism doesn't mean turning a blind eye to potential pitfalls. In this column, Esther Derby applies a lesson about asking, "What if..."
|
|
|
Getting to the Bottom of Project Troubles It's amazing how many projects, already in a hole, keep sinking deeper. When team members and staff don't have the insight or objectivity to turn things around, an independent consultant can help—or not. In this column, a leading industry consultant gives you "the straight dope" on what to watch out for.
|
|