Abstract/Description

According to the Standish group, 64 percent of features in systems are rarely—or never—used. How does this happen? Today, the work of eliciting the customers’ true needs, which remains elusive, can be enhanced using data-driven requirements techniques. Brandon Carlson introduces some of the reasons why identifying customer needs is so difficult and how you can improve them using data collection techniques that you can employ on your projects right away. Find out how to instrument existing applications and develop new requirements based on operational profiles of the current system. Learn to use A/B testing—a technique for trying out and analyzing alternative implementations—on your current system to determine which new features will deliver the most business value. With these tools at hand, you can help users and business stakeholders decide the best approaches and best new features to meet their real needs. Now is the time to take the guesswork out of requirements and get the facts.

You must be a Subscriber to view this post and you are currently not logged in.

You can either log in below or sign up here.