On the Benefits And Problems Related to Using Definition of Done -- A Survey Study

August 08, 2022 Β· Declared Dead Β· πŸ› Journal of Systems and Software

πŸ‘» CAUSE OF DEATH: Ghosted
No code link whatsoever

"No code URL or promise found in abstract"

Evidence collected by the PWNC Scanner

Authors Sylwia Kopczynska, Jakub Piechowiak, Miroslaw Ochodek, Jerzy Nawrocki arXiv ID 2208.04003 Category cs.SE: Software Engineering Citations 3 Venue Journal of Systems and Software Last Checked 4 months ago
Abstract
Context: Definition of Done (DoD) is one of the fundamental concepts of Scrum. It expresses a shared view of a Scrum Team on what makes an increment of their product complete. DoDs are often defined as checklists with items being requirements towards software (e.g., quality requirements) or towards activities performed to make the increment shippable (e.g., code reviews, testing). Unfortunately, the knowledge about the usefulness of DoD is still very limited. Objective: The goal is to study what benefits using the DoD practice can bring to an agile project, what problems it may trigger, and how it is created and maintained. Method: In the survey among members of agile software development projects, 137 practitioners from all over the globe shared their experience with us. Results: 93% of the respondents perceive DoD as at least valuable for their ventures. It helps them to make work items complete, assure product quality, and ensure the needed activities are executed. However, they indicated that every second project struggles with infeasible, incorrect, unavailable, or creeping DoD. Conclusions: It follows from the study that DoD is important but not easy to use and more empirical studies are needed to identify best practices in this area.
Community shame:
Not yet rated
Community Contributions

Found the code? Know the venue? Think something is wrong? Let us know!

πŸ“œ Similar Papers

In the same crypt β€” Software Engineering

Died the same way β€” πŸ‘» Ghosted