Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Smarter product management and development prioritization with direct customer feedback analytics

IP.com Disclosure Number: IPCOM000242180D
Publication Date: 2015-Jun-23
Document File: 6 page(s) / 300K

Publishing Venue

The IP.com Prior Art Database

Abstract

A system and method for smarter product management and development prioritization with direct customer feedback analytics.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 26% of the total text.

Page 01 of 6

Smarter product management and development prioritization with direct customer feedback analytics

Disclosed is a system and method for smarter product management and development prioritization with direct customer feedback analytics.

Software product test, development, and support teams often struggle with the question of how to accurately model their test or support environments to reflect real customer configurations during a test cycle. Given limited personnel and equipment resources, configuration of test environments is often based on anecdotal knowledge of customer configurations and behavior. An accurate, methodical representation of "general" classes of customer environments is typically left wanting. This situation is only exacerbated by the recent move to the Agile development methodology and the Continuous Delivery Model of software development by many development teams. Test cycles may be compressed or are more continuos and nebulous in nature. For sufficiently complex software systems that feature many settings, options, and "tuneables" - as well as ways in which and on what platforms it may be deployed - test coverage is hampered. This may lead to problem reports and "test escapes". In addition, there is limited ability to convey test findings relevantly to customers of a particular "type" since characterizations of customers is left wanting. Additionally, sufficient data on customer configurations and usage patterns is left wanting when it comes to defining or prioritizing feature enhancements from a product management standpoint.

The problem being addressed in this article is that of how to effectively architect test hardware/software environments to accurately exercise a software product in a manner similar to targeted, realistic customer configurations given limited resources. A

secondary problem addressed is that of how to effectively supply feedback to "types" of customers once test results are known. What is needed is, given a large customer base, a way to generalize groupings of customers into similar "clusters" or "types" so that the limited resources of a test organization may be optimized to mimic some subset of those environments to enhance test coverage. An optimization of test resources is

needed to successfully coexist with an Agile development schedule while still exposing software/hardware configurations, platforms, and workloads and most accurately model the largest percentage of a target customer base. A mechanism is also needed to

supply guidance to customers in an effective manner based on test findings after exploring these "types". A corollary benefit of addressing these problem is also to

address the issue of limited product management visibility to customer needs and usage patterns.

An embodiment of the disclosed system is a feedback loop through which product

usage and configuration information necessary to identify parameterized customer "types" is transmitted to a centralized repository,...