Related Content
 |
4 Common Mistakes New Managers Make Making the transition into a management role is a huge step—but also one fraught with opportunities to make mistakes. Having an inkling of some of the more common mistakes new managers make might help in avoiding them. Here are four mistakes to be on the lookout for so you don't make them as a new manager. |
|
 |
How to Deal with Crabby Coworkers We've all had to deal with crabby coworkers—the people who have good technical skills but are a pain to work with. They grouse, gripe, and are generally negative. Luckily, there are more things you can do than just hope you don't have to interact with these people. Here are tips for dealing with your crabby coworkers. |
|
 |
3 Mistakes Teams Make When Choosing a ScrumMaster One cause of agile project failure is choosing the wrong person as your ScrumMaster. While a bad ScrumMaster is a problem for any team, it is particularly bad for teams new to agile, as the team won’t know they are being led down the wrong path. Here are three mistakes organizations make when choosing a ScrumMaster. |
|
 |
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. |
|
 |
The Power of a Single Question in Understanding Customer Needs People tend to see their circumstances as more unusual, difficult, or troublesome than anyone else’s. As a result, by asking about their problem, priorities, or responsibilities, you can gain important information about their situation and how they perceive it. Here's one question to learn a lot about your customers. |
|
 |
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. |
|
 |
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. |
