Retrospective Based on Data-Driven Persona Significance in B-to-B Software Development

A Business-to-Business (B-to-B) software development company develops services to satisfy their customers' requirements. Developers should prioritize customer satisfaction because customers greatly influence on agile software development. However, it is possible that a B-to-B software development company has following issues: 1) failure to understand actual users because the requirements are not often derived from actual users and 2) failure to satisfy the future customers' requirements when only satisfying current customers. Although many previous works proposed methods to elicit the requirements based on actual quantitative data, these works had not considered customers and end-users simultaneously. Herein we proposed Retrospective based on Data-Driven Persona Significance (ReD2PS) to help developers to plan future releases. ReD2PS includes Persona Significance Index (PerSiI) to reflect the correspondence between target users, which developers assume based on requirements in releases, and end-users' personas. A case study involving a Japanese cloud application shows that PerSiI reflects the relationship between target users and end-users to discuss about the validity and effectiveness of ReD2PS.

[1]  Erin Friess,et al.  Personas and decision making in the design process: an ethnographic case study , 2012, CHI.

[2]  Jonathan Grudin,et al.  Personas: practice and theory , 2003, DUX '03.

[3]  Mikio Aoyama,et al.  Persona-Scenario-Goal Methodology for User-Centered Requirements Engineering , 2007, 15th IEEE International Requirements Engineering Conference (RE 2007).

[4]  Ali Selamat,et al.  A systematic literature review of software requirements prioritization research , 2014, Inf. Softw. Technol..

[5]  Steve Whittaker,et al.  How do designers and user experience professionals actually perceive and use personas? , 2012, CHI.

[6]  Hironori Washizaki,et al.  GO-MUC: A Strategy Design Method Considering Requirements of User and Business by Goal-Oriented Measurement , 2016, 2016 IEEE/ACM Cooperative and Human Aspects of Software Engineering (CHASE).

[7]  Yasuhiro Watanabe,et al.  ID3P: Iterative Data-Driven Development of Persona Based on Quantitative Evaluation and Revision , 2017, 2017 IEEE/ACM 10th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE).

[8]  Jürgen Münch,et al.  Transitioning Towards Continuous Delivery in the B2B Domain: A Case Study , 2015, XP.

[9]  Jane Cleland-Huang,et al.  A Persona-Based Approach for Exploring Architecturally Significant Requirements in Agile Projects , 2013, REFSQ.

[10]  Yvonne Dittrich,et al.  Personas is not applicable: local remedies interpreted in a wider context , 2004, PDC 04.

[11]  Xiang Zhang,et al.  Data-driven Personas: Constructing Archetypal Users with Clickstreams and User Telemetry , 2016, CHI.

[12]  Xavier Franch,et al.  A Survey on Software Release Planning Models , 2016, PROFES.

[13]  Marjo Kauppinen,et al.  Linking business and requirements engineering: is solution planning a missing activity in software product companies? , 2009, Requirements Engineering.

[14]  Maleknaz Nayebi,et al.  Toward Data-Driven Requirements Engineering , 2016, IEEE Software.

[15]  Jane Cleland-Huang,et al.  Personas in the middle: automated support for creating personas as focal points in feature gathering forums , 2014, ASE.