2019
DOI: 10.1093/jamia/ocz123
|View full text |Cite
|
Sign up to set email alerts
|

User stories as lightweight requirements for agile clinical decision support development

Abstract: ObjectiveWe sought to demonstrate applicability of user stories, progressively elaborated by testable acceptance criteria, as lightweight requirements for agile development of clinical decision support (CDS).Materials and MethodsUser stories employed the template: As a [type of user], I want [some goal] so that [some reason]. From the “so that” section, CDS benefit measures were derived. Detailed acceptance criteria were elaborated through ensuing conversations. We estimated user story size with “story points,… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
15
0

Year Published

2020
2020
2024
2024

Publication Types

Select...
7
3

Relationship

0
10

Authors

Journals

citations
Cited by 23 publications
(16 citation statements)
references
References 31 publications
0
15
0
Order By: Relevance
“…However, just as in our study, the authors also mentioned that the “why” of the user stories was not often clear and had to be continuously asked and expanded upon. In the process, a continuous review of the created user stories was crucial to ensure that the final product met their needs [ 34 ]. This is where the iterative DT model proved helpful in our study.…”
Section: Discussionmentioning
confidence: 99%
“…However, just as in our study, the authors also mentioned that the “why” of the user stories was not often clear and had to be continuously asked and expanded upon. In the process, a continuous review of the created user stories was crucial to ensure that the final product met their needs [ 34 ]. This is where the iterative DT model proved helpful in our study.…”
Section: Discussionmentioning
confidence: 99%
“…Acceptability of CDSS is another key point. Kannan et al, [14] propose a method for a CDSS design to best meet a precisely specified and assessable user purpose. Design alerts may also avoid rejection of CDSSs by caregivers.…”
Section: Discussion and Outlookmentioning
confidence: 99%
“…First, we derived user requirements of the ZLM through user stories. A user story describes the features of a software system from the perspective of the user [4], for example: User KJ (who) wants a moving average graph for all fT3 test results from 2019-01-01 to 2019-12-31 (what) in order detect significant shifts in the measurements (goal). After that, we developed a mock-up to ensure to have captured all requirements.…”
Section: Methodsmentioning
confidence: 99%