Related Content
 |
Managing the Turbulence of Organizational Change In times of major change, particularly organizational change, it's normal for people involved to experience turbulence, including anxiety, anger, or uncertainty. If you’re overseeing a change, how you communicate with those affected can significantly decrease—or increase—the duration and intensity of that turbulence. |
|
 |
Agile Testers Shouldn’t Be Enablers Testing has often been seen as the final stage of creating an application. Since we weren’t shifting testing left as much as we do today, a great deal of work was thrown on the testing team at the very end of an exhausting project cycle. But testers shouldn’t be seen as the last line of defense. |
|
 |
The Software World Is Changing—Are You Willing to Change with It? The software landscape is changing. Processes are becoming quicker and leaner, but instead of re-evaluating some of our traditional practices, we sometimes try to make them fit where they don't belong. This holds back continuous improvement. If you want change, you first need to be willing to change. |
|
 |
Speaking the Same Language in Software Testing Arguments in software testing often revolve around language. We use phrases like test case, exploratory testing, and regression testing every day, but we can’t be sure that you and I mean the same thing when we do. Increased communication and detailed discussions can help avoid misunderstandings. |
|
 |
Managing Resistance to Organizational Change Change can be difficult, and some people's reaction is to shut it all down. If they think their concerns aren’t being heard, they get defensive, and your project is on a trajectory for disaster. Don't fire off an email while tempers are running high. Managing expectations thoughtfully is essential to project success. |
|
 |
An Agile Mindset: Learning Early, Not Failing Fast Agile encourages teams to continuously improve through learning. One of the phrases associated with this process is "failing fast"—trying new things and taking lessons from mistakes as you go. But Johanna Rothman thinks "learning early" is a better phrase. That change in terminology can give you a happier mindset. |
|
 |
The Importance of Testing in Conjunction While it is important to have distinction between testing efforts to maintain specialization and core subject matter expertise, having overlap in test efforts—testing in conjunction—is becoming a common practice. |
|
 |
Why Testers and Developers Don’t Have to Be on the Same Page Since software development is highly subjective in nature, different thought processes and assumptions between development and testing teams can positively impact applications and lead to a more successful, well-rounded product. It might not seem like it at the time, but there’s value to dissonance. |
