Related Content
For Distributed Team Success, Think Differently about When For distributed teams, activities usually get scheduled based on constraints such as availability and time zone, but people don’t often take into account when the most effective time to meet would be. Neglecting people’s work tendencies and schedule preferences could make it harder for the team to be successful. |
||
Handling the Emotional Turmoil of Organizational Change Chaos, confusion, and emotional turmoil are not unusual during major organizational change. Nevertheless, even people at the top sometimes minimize the impact of the change on employees—and on themselves. Worse, they sometimes do so dismissively. It's important not to underestimate the challenge of managing change. |
||
How Testers Can Collaborate with the ScrumMaster ScrumMasters serve the team by providing facilitation and coaching, but they also have many challenges. Those in testing roles are in a good position to collaborate with the ScrumMaster to improve agile processes. Here are some ways testers can partner with, support, and assist the ScrumMaster—and the rest of the team. |
||
How Face-to-Face Meetings Can Heal Team Conflicts When distributed teams have a conflict, it's easy for one team to place the blame entirely on the other and even start to think of them as disagreeable, incompetent, and worse. This fault-finding can be especially bad when the parties have never met. Face-to-face meetings can make all the difference in improving trust. |
||
The Hidden Benefit of One-on-One Manager Meetings Managers may frame one-on-one meetings as a way to “support employees” and check to see if the employee “needs to meet this week.” Supporting an employee is a primary goal of these meetings, but the value of one-on-one time to managers—and the importance of building trust with employees—also should be prioritized. |
||
Testing in a Pair Programming Environment If a development team does pair programming, where does testing fit in? You don't have to wait until the programming is done—testers can be part of the whole process, from code design to reviewing changes to production. Pair programming plus a good automation strategy mean quality is built in throughout development. |
||
Why Agile Is a Double-Edged Sword When It Comes to Quality When it comes to quality, agile very often leads to better applications and just stronger testing overall. However, the rapidity of agile can make it even more difficult to keep up with bugs since you’re iterating at speeds teams often just aren’t used to. |
||
During Times of Major Change, Keep People Informed During times of major change, readily available information can help reduce the fears of those affected about what it means for them. If you’re involved in implementing change, it’s wise to keep people informed—not just about the change itself, but also about its impact on processes, responsibilities, and expectations. |