Jobs-to-be-Done Oriented Requirements Engineering: A Method for Defining Job Stories

[Context and motivation] Goal orientation is an unrealized promise in the practice of requirements engineering (RE). Conversely, lightweight approaches such as user stories have gained substantial adoption. As critics highlight the limitations of user stories, Job Stories are emerging as an alternative that embeds goal-oriented principles by emphasizing situation, motivation and expected outcome. This new approach has not been studied in research yet. [Question/Problem] Scientific foundations are lacking for the job story artifact and there are no actionable methods for effectively applying job stories. Thus, practitioners may end up creating their own flavor of job stories that may fail to deliver the promised value of the Jobs-to-be-Done theory. [Principal ideas/results] We integrate multiple approaches based on job stories to create a conceptual model of job stories and to construct a generic method for Jobs-to-be-Done Oriented RE. Applying our job story method to an industry case study, we highlight benefits and limitations. [Contribution] Our method aims to bring job stories from craft to discipline, and to provide systematic means for applying Jobs-to-be-Done orientation in practice and for assessing its effectiveness.

[1]  Anthony W. Ulwick,et al.  Giving Customers a Fair Hearing , 2008 .

[2]  Frank Maurer,et al.  Requirements engineering and agile software development , 2003, WET ICE 2003. Proceedings. Twelfth IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises, 2003..

[3]  Alan J. Dix.  Human-Computer Interaction , 2018, Encyclopedia of Database Systems.

[4]  Inge van de Weerd,et al.  Meta-Modeling for Situational Analysis and Design Methods , 2009 .

[5]  Clayton M. Christensen,et al.  Marketing malpractice: the cause and the cure. , 2005, Harvard business review.

[6]  Anthony W. Ulwick,et al.  The customer-centered innovation map. , 2008, Harvard business review.

[7]  Kathleen M. Eisenhardt,et al.  Theory Building From Cases: Opportunities And Challenges , 2007 .

[8]  Karen Dillon,et al.  Competing Against Luck: The Story of Innovation and Customer Choice , 2016 .

[9]  Karen Dillon,et al.  Know your customers' "jobs to be done" , 2016 .

[10]  Sjaak Brinkkemper,et al.  The Use and Effectiveness of User Stories in Practice , 2016, REFSQ.

[11]  Søren Lauesen,et al.  Task Descriptions as Functional Requirements , 2003, IEEE Softw..

[12]  J. Schumpeter,et al.  Capitalism, Socialism and Democracy , 1943 .

[13]  Mike Cohn,et al.  User Stories Applied: For Agile Software Development , 2004 .

[14]  Jeremy Kitchen,et al.  User Centered Design , 2015 .

[15]  チャ-ルズ ハンディ-,et al.  BRAIN FOOD : CORPORATE GOVERNANCE 企業組織は、より透明で実体のある存在へ , 2013 .

[16]  Sjaak Brinkkemper,et al.  Extracting conceptual models from user stories with Visual Narrator , 2017, Requirements Engineering.

[17]  Clayton M. Christensen,et al.  Finding the Right Job for Your Product , 2007 .

[18]  Mica R. Endsley,et al.  Designing for Situation Awareness : An Approach to User-Centered Design , 2003 .

[19]  Anthony W. Ulwick.  Turn customer input into innovation. , 2002, Harvard business review.

[20]  Sjaak Brinkkemper,et al.  Improving agile requirements: the Quality User Story framework and tool , 2016, Requirements Engineering.

[21]  Xavier Franch,et al.  iStar 2.0 Language Guide , 2016, ArXiv.

[22]  Chris Chapman,et al.  The Personas' New Clothes: Methodological and Practical Arguments against a Popular Method , 2006 .

[23]  Mohamad Kassab,et al.  The changing landscape of requirements engineering practices over the past decade , 2015, 2015 IEEE Fifth International Workshop on Empirical Requirements Engineering (EmpiRE).

[24]  S. Macstravic.  Marketing myopia. , 1998, The Healthcare Forum journal.

[25]  John Mylopoulos,et al.  Understanding "why" in software process modelling, analysis, and design , 1994, Proceedings of 16th International Conference on Software Engineering.

[26]  Colin Potts,et al.  Recording the reasons for design decisions , 1988, Proceedings. [1989] 11th International Conference on Software Engineering.

[27]  Michael Jackson,et al.  Four dark corners of requirements engineering , 1997, TSEM.