TY - CHAP
T1 - What is Ready in a DoR? Rationales, Responsibility & Rules in using a Definition of Ready
AU - van Riesen, Mark
AU - Wagenaar, Gerard
PY - 2024/4/8
Y1 - 2024/4/8
N2 - In agile software development, a Definition of Ready (DoR) is used to indicate conditions a Product Backlog Item (PBI) has to meet before accepting it into a Sprint Backlog. This research aims (1) to identify those conditions, (2) to investigate why Scrum teams do or do not use a DoR, and (3) to identify which (Scrum) role is responsible for drafting a DoR. Research questions are answered by a literature review and interviews with Scrum team members. Results show that conditions vary, but common elements are include INVEST criteria, clearly defining, and prioritizing a PBI. Reasons to use a DoR include a positive impact on workflow, like an efficient process or increased quality of software. Teams might not use a DoR, because of overhead of writing it or encouraging a less ‘agile way of thinking’. Both Product Owner and Scrum Master can be involved in defining and maintaining a DoR, and it is considered good practice to involve all team members. Our findings also reveal that use of a DoR is not intuitive per se.
AB - In agile software development, a Definition of Ready (DoR) is used to indicate conditions a Product Backlog Item (PBI) has to meet before accepting it into a Sprint Backlog. This research aims (1) to identify those conditions, (2) to investigate why Scrum teams do or do not use a DoR, and (3) to identify which (Scrum) role is responsible for drafting a DoR. Research questions are answered by a literature review and interviews with Scrum team members. Results show that conditions vary, but common elements are include INVEST criteria, clearly defining, and prioritizing a PBI. Reasons to use a DoR include a positive impact on workflow, like an efficient process or increased quality of software. Teams might not use a DoR, because of overhead of writing it or encouraging a less ‘agile way of thinking’. Both Product Owner and Scrum Master can be involved in defining and maintaining a DoR, and it is considered good practice to involve all team members. Our findings also reveal that use of a DoR is not intuitive per se.
KW - Agile Software Development
KW - Definition of Ready
KW - DoR
KW - Scrum
KW - User story
KW - INVEST criteria 1
UR - http://www.scopus.com/inward/record.url?scp=85193051632&partnerID=8YFLogxK
M3 - Chapter
AN - SCOPUS:85193051632
T3 - CEUR Workshop Proceedings
SP - 1
EP - 5
BT - REFSQ-JP 2024
A2 - Mendez, Daniel
A2 - Moreira, Ana
A2 - Horkoff, Jennifer
A2 - Weyer, Thorsten
A2 - Daneva, Maya
A2 - Unterkalmsteiner, Michael
A2 - Buhne, Stan
A2 - Hehn, Jennifer
A2 - Penzenstadler, Birgit
A2 - Dieste, Oscar
A2 - Condori-Fernandez, Nelly
A2 - Guizzardi, Renata
A2 - Habibullah, Khan Mohammad
A2 - Perini, Anna
A2 - Susi, Angelo
A2 - Abualhaija, Sallam
A2 - Arora, Chetan
A2 - Dell'Anna, Davide
A2 - Ferrari, Alessio
A2 - Ghanavati, Sepideh
A2 - Dalpiaz, Fabiano
A2 - Steghofer, Jan-Philipp
A2 - Rachmann, Alexander
A2 - Gulden, Jens
A2 - Muller, Andrea
A2 - Beck, Martina
A2 - Birkmeier, Dominik
A2 - Herrmann, Andrea
A2 - Mennig, Patrick
A2 - Schneider, Kurt
PB - CEUR WS
T2 - 2024 Joint International Conference on Requirements Engineering: Foundation for Software Quality Workshops, Doctoral Symposium, Posters and Tools Track, and Education and Training Track, REFSQ-JP 2024
Y2 - 8 April 2024 through 11 April 2024
ER -