teams

Our society is founded on the importance of meetings, and it seems that the higher on the corporate ladder one climbs, the more meetings he must attend. Indeed, one of Michele Sliger's coworkers calculated that the amount of time she spends arranging meetings, getting to meetings, and in meetings equates to almost her entire workweek-thirty-six hours on average. Even though we may lose track of time in meetings, we all are painfully aware of the time we spend waiting for everyone to show up. In this column, Michele Sliger explains some of the tactics she's seen teams use to ensure that meetings start on time.

Given a choice, most people would rather have happy, satisfied customers than angry, complaining customers. But how to create customer satisfaction is sometimes a mystery. In this column, Naomi Karten describes one person's experience that backfired and taught him some lessons.

What are the attributes of a good tester—of a great tester? As every test manager knows, identifying the right people for a test team can be a struggle. In this column, Fiona Charles describes the qualities of mind she looks for in testers, and the interview questions she asks candidates so that she can evaluate how they think.

When a man suffered a cardiac arrest on a ski slope, a medley of medical personnel from different countries and backgrounds mustered together to take charge of the man's health. Despite language barriers, they were successful in stabilizing the man. While this incident may seem to have little to do with software development, Clarke Ching sees that the makeshift emergency team shared specific characteristics found in all strong software development teams. In this column, he details these characteristics and how applying them can turn your team into a more successful team no matter how dissimilar individual teammates may be.