Product development organizations that skip or rush through critical preplanning activities run the risk of failure. Organizations that use a more agile approach to product development ensure that the teams work on the right things, have the right amount of dialogue with their business partners, and produce the right amount of value to the product.
Hoarding is an incredibly common—but usually unnamed and invisible—phenomenon in corporate software development. If you’ve been doing agile for a while, you are no doubt aware of the cost of hoarding and you’ve probably removed much of it, but what happens when you aren't doing agile yet? Clarke Ching explains how to counter hoarding by prioritizing the right features.
When applying validation, should you limit yourself to the end-of-sprint review or demo—the practice most people associate with agile validation—or should you utilize other validation types where customers provide feedback? Where do the customers who attend validation sessions come from? In this article, you will learn about the importance of the ACVV and how to establish a vision to benefit the product and each project therein.
Improving customer satisfaction should be a primary goal of process improvement programs. So how satisfied are our customers? One of the best ways to find out is to ask them. Here are techniques for creating a useful survey and interpreting the results.
In this interview, Neeraj Tripathi, vice president of Global QA at Infor, goes over the principles of effective software quality management. He explains how to measure customer satisfaction and how active QA involvement eliminates defects early and shifts quality left.
Satisfying our customers is an essential element to staying in business in this modern world of global competition. We must satisfy and even delight our customers with the value of our software products and services to gain their loyalty and repeat business. Customer satisfaction is therefore a primary goal of process improvement programs. So how satisfied are our customers? One of the best ways to find out is to ask them using Customer Satisfaction Surveys. This paper includes details on designing your own software customer satisfaction questionnaire, tracking survey results and example reports that turn survey data into useful information.
In some organizations, communication flaws are rampant and muddled messages are the norm. Success in software efforts is often hindered by communication that is incomprehensible, ambiguous, misdirected, ill-timed--or lacking when it is most needed. The result? Rocky relationships, topsy-turvy teamwork, precarious projects, and crazed customers. The situation is not hopeless, though. In fact, making changes is surprisingly easy. In a presentation that is both serious and light-hearted, Naomi Karten shares ideas, experiences, and advice to help you detect, correct, and prevent some of the most common communication snafus.