Related Content
A Tale of Two Projects Large IT projects are challenging. Complexity is hard to estimate well. Big systems are tough to implement. But when you're staring at a fast-approaching deadline and you know your system will not be functional in time to meet it, there are ways of handling the situation that are better than others. |
||
How to Get People to Read Your Email Busy people—and even those who are not so busy—lack the patience to wade through endless emails, so you have to be clear, concise, and considerate if you want yours to be read. There are many ways you can communicate more easily and effectively, and Naomi Karten compiles some good ideas here. |
||
Six Focus Areas for Effective Test Management For a test manager to be effective, Mukesh Sharma says six important areas must come together: domain focus, test expertise, leadership style, management practices, proactivity quotient, and communication protocols. Read on to learn how to become a well-rounded test manager in these areas. |
||
How to End Disputes Gracefully Given the many points of view in any work effort, disputes may be inevitable. The challenge is to gracefully terminate these disputes with none of the parties suffering black eyes or bruised egos. When you find yourself embroiled in a divisive difference of opinion, here are some things to try. |
||
Using Assessments and Standards to Improve Your Process Process improvement is a fundamental endeavor that any successful organization must embrace. The challenge many companies face is how to effectively implement IT process improvement. A good place to begin is with an assessment of current operations; then measure those findings against good criteria. |
||
Understanding the Pace of Change: How to Stay Relevant in Your Role The rate at which we need to change and the speed of change are much greater than they used to be. We don't have as much time to get as deep in our skills, and we need to be more comfortable being generalists and picking up new skills, technologies, and processes quickly. Read on to stay relevant. |
||
The Ambiguous Sounds of Silence: Why You Should Ask for Input Silence may not be golden when members of a team are trying to reach agreement, resolve an issue, or make a decision. In this setting, silence is often taken to mean that those who haven’t voiced an opinion approve of the matter under discussion—yet they may very well not. You should make sure. |
||
Listen Up, Testers: The Power of an Example for Context How long does it take for a tester to change a light bulb? It sounds like a setup for a joke, but any tester will respond, "Which light fixture? With what light bulb? How high up is the outlet?" All of these questions help the tester explore the context—and examples can go a long way toward helping. |