%0 Conference Paper %1 Lucassen2018 %A Lucassen, Garm %A van de Keuken, Maxim %A Dalpiaz, Fabiano %A Brinkkemper, Sjaak %A Sloof, Gijs Willem %A Schlingmann, Johan %B International Working Conference on Requirements Engineering %D 2018 %E Kamsties, Erik %E Horkoff, Jennifer %E Dalpiaz, Fabiano %I Springer %K product.planning %P 227-243 %R 10.1007/978-3-319-77243-1_14 %T Jobs-to-be-done oriented requirements engineering: A method for defining job stories %U http://link.springer.com/10.1007/978-3-319-77243-1_14 %V 10753 %X 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. %@ 9783319772424

@inproceedings{Lucassen2018, abstract = {[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.}, added-at = {2018-08-31T22:18:29.000+0200}, author = {Lucassen, Garm and van de Keuken, Maxim and Dalpiaz, Fabiano and Brinkkemper, Sjaak and Sloof, Gijs Willem and Schlingmann, Johan}, biburl = {https://www.bibsonomy.org/bibtex/27552bce383c30909600bb99157e419e4/andreysaltan}, booktitle = {International Working Conference on Requirements Engineering}, doi = {10.1007/978-3-319-77243-1_14}, editor = {Kamsties, Erik and Horkoff, Jennifer and Dalpiaz, Fabiano}, interhash = {9fda246bf45d68fd924fdf026c26eefc}, intrahash = {7552bce383c30909600bb99157e419e4}, isbn = {9783319772424}, issn = {16113349}, keywords = {product.planning}, mendeley-tags = {Product Planning}, pages = {227-243}, publisher = {Springer}, timestamp = {2018-08-31T22:26:39.000+0200}, title = {Jobs-to-be-done oriented requirements engineering: A method for defining job stories}, url = {http://link.springer.com/10.1007/978-3-319-77243-1_14}, volume = 10753, year = 2018 }