TY - GEN
T1 - Feature performance metrics for software as a service offering
AU - Latner, Avi
AU - Valerdi, Ricardo
PY - 2011
Y1 - 2011
N2 - This paper provides a framework to measure the performance of software as a service (SaaS) product features to prioritize development efforts. Firstly, relative value is measured by the impact of each feature on customer acquisition and retention. Secondly, feature value is compared to feature cost and specifically development investment to determine feature profitability. Thirdly, feature sensitivity is measured. Feature sensitivity is defined as the effect a fixed amount of development investment has on value in a given time. Fourthly, features are segmented according to their location relative to the value to cost trend line into most valuable features, outperforming, underperforming and fledglings. Finally, results are analyzed to determine future action. Maintenance and bug fixes are prioritized according to feature value. Product enhancements are prioritized according to sensitivity with special attention to fledglings. Underperforming features are either put on "life-support," terminated or overhauled. This framework is applicable to SaaS companies for the purpose of prioritizing features, an important consideration for concurrent engineering of software systems.
AB - This paper provides a framework to measure the performance of software as a service (SaaS) product features to prioritize development efforts. Firstly, relative value is measured by the impact of each feature on customer acquisition and retention. Secondly, feature value is compared to feature cost and specifically development investment to determine feature profitability. Thirdly, feature sensitivity is measured. Feature sensitivity is defined as the effect a fixed amount of development investment has on value in a given time. Fourthly, features are segmented according to their location relative to the value to cost trend line into most valuable features, outperforming, underperforming and fledglings. Finally, results are analyzed to determine future action. Maintenance and bug fixes are prioritized according to feature value. Product enhancements are prioritized according to sensitivity with special attention to fledglings. Underperforming features are either put on "life-support," terminated or overhauled. This framework is applicable to SaaS companies for the purpose of prioritizing features, an important consideration for concurrent engineering of software systems.
KW - Customer value
KW - Performance metrics
KW - Product development
KW - Software as a service
UR - http://www.scopus.com/inward/record.url?scp=84870180560&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=84870180560&partnerID=8YFLogxK
U2 - 10.1007/978-0-85729-799-0_17
DO - 10.1007/978-0-85729-799-0_17
M3 - Conference contribution
AN - SCOPUS:84870180560
SN - 9780857297983
T3 - Advanced Concurrent Engineering
SP - 151
EP - 158
BT - Improving Complex Systems Today - Proceedings of the 18th ISPE International Conference on Concurrent Engineering
T2 - 18th ISPE International Conference on Concurrent Engineering, CE 2011
Y2 - 4 July 2011 through 8 July 2011
ER -