Stories Vs. User Stories: A Terminological Clarification
Uložené v:
| Názov: | Stories Vs. User Stories: A Terminological Clarification |
|---|---|
| Autori: | Franch Gutiérrez, Javier, Steffe, Hans-Jörg, Bühne, Stan, López Cuesta, Lidia, Sturm, Stefan |
| Zdroj: | Lecture Notes in Business Information Processing ISBN: 9783031727801 UPCommons. Portal del coneixement obert de la UPC Universitat Politècnica de Catalunya (UPC) |
| Informácie o vydavateľovi: | Springer Nature Switzerland, 2025. |
| Rok vydania: | 2025 |
| Predmety: | Àrees temàtiques de la UPC::Informàtica::Enginyeria del software, Template, User story, Story, Agile methodologies |
| Popis: | User stories are the main vehicle to describe user needs in Agile projects and Agile project developments. But being this concept universally agreed, we may find that not all work increments have a clear user-centric view. In this paper, we focus on the distinction between user-centric “user stories” and other type of simple narratives, which may be simply called “stories”, which can be at the same level of abstraction. We propose a conceptual model in the form of UML diagram, and associated definitions, to clarify this distinction. The model also makes clearer the distinction among (user) story and (user) story template, which is not always kept clear. |
| Druh dokumentu: | Part of book or chapter of book Conference object |
| Popis súboru: | application/pdf |
| Jazyk: | English |
| DOI: | 10.1007/978-3-031-72781-8_28 |
| Rights: | CC BY |
| Prístupové číslo: | edsair.doi.dedup.....a5e31dd83a9c0b30e13fa78bba29b28e |
| Databáza: | OpenAIRE |
Nájsť tento článok vo Web of Science | Abstrakt: | User stories are the main vehicle to describe user needs in Agile projects and Agile project developments. But being this concept universally agreed, we may find that not all work increments have a clear user-centric view. In this paper, we focus on the distinction between user-centric “user stories” and other type of simple narratives, which may be simply called “stories”, which can be at the same level of abstraction. We propose a conceptual model in the form of UML diagram, and associated definitions, to clarify this distinction. The model also makes clearer the distinction among (user) story and (user) story template, which is not always kept clear. |
|---|---|
| DOI: | 10.1007/978-3-031-72781-8_28 |