What features of your software do customers use the most? What parts of the software do they find frustrating or completely useless? Wouldn't you like to target these critical areas in your testing? Most organizations get feedback-much later than anyone would like-from customer complaints, product reviews, and online discussion forums. Microsoft employs proactive approaches to gather detailed customer usage data from both beta tests and released products, achieving greater understanding of the experience of its millions of users. Product teams analyze this data to guide improvement efforts, including test planning, throughout the product cycle. Alan Page shares the inner workings of Microsoft's methods for gathering customer data, including how to know what features are used, when they are used, where crashes are occurring, and when customers are feeling pain.

The definition of a "good project manager" varies depending on what skills you value most of this person. In this week's column, Payson Hall explores the root of the definition, highlighting the key characteristic he believes is the true hallmark of a good project manager.

Do your stakeholders use different terms to talk about the same concept or use the same term but in a different way? A domain model can clarify key concepts and the relationships between them, helping your team resolve ambiguous terms and leading to more productive discussions about project requirements.

Great leaders don't always lead the charge, stand in front, or offer direction. They know when to step aside to let others step forward. Yet, this type of leadership is often mistaken for passivity or overlooked entirely. Esther Derby shows how "in front" leadership actually can cause gridlock and loss of productivity and destroy the good spirits of a team. You can avoid these pitfalls by noticing when the most effective leadership means choosing to follow.