Related Content
 |
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. |
|
 |
Lessons Learned at the Agile Dev, Better Software & DevOps West Conference The Agile Dev, Better Software & DevOps West conference was held in Las Vegas in early June. Coveros technical manager Gene Gotimer was a speaker at the event, but he also attended as a delegate, getting to experience the keynotes, sessions, Expo, and other parts of the software conference. Here are his takeaways. |
|
 |
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 Risk of Overemphasizing Risks We are trained to identify and evaluate risks. This prevents teams from making decisions that are unlikely to work, saving time and money and helping the team move forward. However, a risk-avoidance mindset can also stop progress. Successful agile teams see risks as ways of starting a conversation, not stopping it. |
|
 |
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. |
|
 |
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. |
