Related Content
 |
The Normalization of Deviance Could Be Hurting Your Team Normalization of deviance refers to becoming blasé about counterproductive behavior or activities. The concept applies to processes that become ingrained in a team even though they contribute to negative outcomes, such as slipping deadlines. Employees become so accustomed to the deviance that, to them, it seems normal. |
|
 |
Testing the Tester: Building a High-Impact QA Team Teams don’t always understand the impact their roles have on the business outcome, so their lack of focus can affect software quality and lead to an array of disasters. You can help your existing testers become a high-performing QA team focused on goals. Here’s what you can do to transform how your QA team functions. |
|
 |
3 Ways to Keep Your Test Suite Lean Test automation is useful, but as your tests grow, they require maintenance. Without curation, your test suite can turn messy and uncontrollable. Keeping a lean test suite will ensure your tests remain useful. You can whip your test suite into shape by focusing on always making your tests valuable, reliable, and fast. |
|
 |
Mob Programming: Working Well Together Mob programming is a whole-team approach to creating software where everyone works together on the same thing at the same computer. It's not a bunch of people watching one person write code, but rather everyone thinking, discussing, designing, and collaborating. Sound crazy? Here's how it improves the quality of code. |
|
 |
Automation for the People We tend to contrast automated and manual testing, but really, they should support each other. The key is to define what our testing objectives are, then build the solution needed to achieve them—probably a combination of manual and automated testing. We should not let the method become more important than the results. |
|
 |
Thinking Inside the Box before Venturing Outside It In their rush to solve a problem, teams often overlook conventional methods in favor of out-of-the-box ideas. But sometimes, the old standbys—thinking first, reviewing criteria, and asking questions—work the best. Before jumping to creative tactics, start by examining the possibilities readily available inside the box. |
|
 |
Analyzing the Software Team Generalist There's a recent trend in having generalists on the software team—there are no developers or testers, only "team members." The idea of the two roles learning from each other is a good one, but it's usually a one-way street: Testers learn to write production code or test tooling, but no one focuses on deep testing. |
|
 |
How to Slim Down Your Bloated Email Inbox If you're spending too much time checking and answering your email—and frankly, who doesn't feel that way—you may just need to revamp your email routine. Here are some techniques for getting a handle on your messages, including better prioritization and categorization. You may even get to the coveted inbox zero. |
