A systematic review on the use of Definition of Done on agile software development projects

Silva, Ana; Araújo, Thalles; Nunes, João Paulo de Oliveira; Perkusich, Mirko; Dilorenzo, Ednaldo; Almeida, Hyggo; Perkusich, Angelo

doi:10.1145/3084226.3084262

Cited by 25 publications

(20 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The Definition of Done concept has been studied before [79] and is well-known in a Scrum context. According to the study, the focus of the DoD should be on the systematic requirements that are common for each user story.…”

Section: C1 Standard Development Environmentmentioning

confidence: 99%

Towards an Anatomy of Software Craftsmanship

SundelinAnders

González-Huerta

WnukKrzysztof

et al. 2021

ACM Trans. Softw. Eng. Methodol.

View full text Add to dashboard Cite

Context: The concept of software craftsmanship has early roots in computing, and in 2009, the Manifesto for Software Craftsmanship was formulated as a reaction to how the Agile methods were practiced and taught. But software craftsmanship has seldom been studied from a software engineering perspective. Objective: The objective of this article is to systematize an anatomy of software craftsmanship through literature studies and a longitudinal case study. Method: We performed a snowballing literature review based on an initial set of nine papers, resulting in 18 papers and 11 books. We also performed a case study following seven years of software development of a product for the financial market, eliciting qualitative, and quantitative results. We used thematic coding to synthesize the results into categories. Results: The resulting anatomy is centered around four themes, containing 17 principles and 47 hierarchical practices connected to the principles. We present the identified practices based on the experiences gathered from the case study, triangulating with the literature results. Conclusion: We provide our systematically derived anatomy of software craftsmanship with the goal of inspiring more research into the principles and practices of software craftsmanship and how these relate to other principles within software engineering in general.

show abstract

Section: C1 Standard Development Environmentmentioning

confidence: 99%

Towards an Anatomy of Software Craftsmanship

SundelinAnders

González-Huerta

WnukKrzysztof

et al. 2021

ACM Trans. Softw. Eng. Methodol.

View full text Add to dashboard Cite

show abstract

“…However, students also answered that the requirements, i.e. part of the acceptance criteria [33] within user stories, had gotten more detailed during Kanban usage. This allows work on a user story to be started without having to clarify open questions beforehand and can help efficiency by decreasing the cycle time.…”

Section: B Kanban Surveymentioning

confidence: 99%

Beyond Surveys: Analyzing Software Development Artifacts to Assess Teaching Efforts

Matthies

Teusner

Hesse

2018

2018 IEEE Frontiers in Education Conference (FIE)

View full text Add to dashboard Cite

This Innovative Practice Full Paper presents an approach of using software development artifacts to gauge student behavior and the effectiveness of changes to curriculum design. There is an ongoing need to adapt university courses to changing requirements and shifts in industry. As an educator it is therefore vital to have access to methods, with which to ascertain the effects of curriculum design changes. In this paper, we present our approach of analyzing software repositories in order to gauge student behavior during project work. We evaluate this approach in a case study of a university undergraduate software development course teaching agile development methodologies. Surveys revealed positive attitudes towards the course and the change of employed development methodology from Scrum to Kanban. However, surveys were not usable to ascertain the degree to which students had adapted their workflows and whether they had done so in accordance with course goals. Therefore, we analyzed students' software repository data, which represents information that can be collected by educators to reveal insights into learning successes and detailed student behavior. We analyze the software repositories created during the last five courses, and evaluate differences in workflows between Kanban and Scrum usage.

show abstract

“…The most significant ones were listed as requirement prioritization, documentation, changing and overscoping requirement, organization, process, and progress monitoring and feedback. In a recent review, Silva et al focused on the use of definition of done practice in agile software development and reported that definition of done was currently being used in various ways in Scrum projects.…”

Section: Related Workmentioning

confidence: 99%

Blended Scrum model for software development organizations

Çetin

Durdu

2018

J Software Evolu Process

View full text Add to dashboard Cite

Software organizations have to develop software in a short time, and quickly respond to changing requirements. Recently, organizations have started to implement agile development models to reduce cost and increase productivity and quality. Scrum, one of the most widely used agile methodologies, is often implemented in various ways that depart in an uncontrolled fashion from the original model, resulting in development methods often called “ScrumBut.” Some argue that such incomplete implementations violate Scrum's core practices and philosophy, while others propose that all methodologies should be adapted to organization's unique culture and integrated with their best practices. In this research, a Blended Scrum model was proposed to overcome uncontrolled ScrumBut issues while transitioning to Scrum. The study was organized as a case study in which software professionals working in Scrum teams were interviewed. In addition, a questionnaire was conducted with other software professionals to determine how agile methods, specifically Scrum, were used. The interviews and questionnaire revealed various Scrum practical implementations. The Blended Scrum model was developed by integrating original Scrum with practices that were determined by interviews and questionnaire conducted with software professionals with real‐world Scrum experience. Finally, the Blended Scrum model was evaluated by Scrum professionals and received positive feedback.

show abstract

A systematic review on the use of Definition of Done on agile software development projects

Cited by 25 publications

References 13 publications

Towards an Anatomy of Software Craftsmanship

Towards an Anatomy of Software Craftsmanship

Beyond Surveys: Analyzing Software Development Artifacts to Assess Teaching Efforts

Blended Scrum model for software development organizations

Contact Info

Product

Resources

About