teams | TechWell


Crab on the beach, photo by Felipe Portella 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.

Naomi Karten's picture
Naomi Karten
Calendar showing some already missed deadlines 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.

Naomi Karten's picture
Naomi Karten
A high-performing QA team holding up a trophy 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.

Amol Adsule's picture
Amol Adsule
A group of people participating in a mob programming session 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.

Woody Zuill's picture
Woody Zuill
Smiling woman holding a large box, photo by bruce mars 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.

Naomi Karten's picture
Naomi Karten
Blue dye merging with a white umbrella 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.

Justin Rohrman's picture
Justin Rohrman
Caution tape stretching across a construction site 5 Pitfalls Agile Coaches Must Avoid

Successful agile teams often have a coach driving continuous improvement. While some coaches are effective initially, many eventually succumb to pitfalls that inhibit their team’s growth and fail to compel any lasting changes. Here are five common pitfalls of agile coaches in most projects that fail to improve.

Alan Crouch's picture
Alan Crouch
Three coworkers laughing in their office, photo by Priscilla Du Preez Why Laughter Is a Sign of Creative, Productive Teams

Laughter is a sign that people feel relaxed and safe. In a workplace, safety leads to environments that enable more idea generation and innovation, so one approach to improving teammates' creativity and connection is to encourage laughter. But how can you do that so it doesn't feel forced? Steve Berczuk has some ideas.

Steve Berczuk's picture
Steve Berczuk