Do Daily Scrums Have to Take Place Each Day? A Case Study of Customized Scrum Principles at an E-commerce Company

Pauly, Daniel F.; Michalik, Bjoern; Basten, Dirk

doi:10.1109/hicss.2015.601

Cited by 16 publications

(5 citation statements)

References 25 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…For instance, time pressure that resulted from external decisions to change the size of the Development Team, introduce new requirements during a Sprint, or determine deadlines in advance contrast the roles, events, artifacts, and rules defined in the Scrum Guide. While previous research has shown the benefits of customizing agile methods [11,29], we contribute to a better understanding of customizing agile methods by revealing that -while customizing methods might be a necessity to fit prevailing organizational structures -the changes applied to the frameworks can also lead to negative effects (i.e., time pressure and related consequence in our context).…”

Section: Theoretical Contributionsmentioning

confidence: 82%

Antecedents and Consequences of Time Pressure in Scrum Projects: Insights from a Qualitative Study

Linßen¹,

Basten²,

Richter³

2018

Proceedings of the 51st Hawaii International Conference on System Sciences

Self Cite

View full text Add to dashboard Cite

Time pressure represents one of the most critical factors associated with software development project failure. However, its role in previous research is limited to traditional development approaches and is also inconclusive, suggesting both negative and positive effects, while others argue for dependence on the level of time pressure. In the context of agile software development projects, particularly Scrum, we seek to analyze the role of time pressure in software development projects and aim to develop a better understanding of its antecedents and consequences. We apply an exploratory, interview-based research approach grounded in data and complemented by thematic analysis. Our findings support a differentiated picture of time pressure, revealing that not all antecedents equally lead to negative consequences and that effects are dependent not only on intensity but also on temporality of time pressure. Understanding antecedents and consequences serves organizations to advantageously manage time pressure.

show abstract

Section: Theoretical Contributionsmentioning

confidence: 82%

Antecedents and Consequences of Time Pressure in Scrum Projects: Insights from a Qualitative Study

Linßen¹,

Basten²,

Richter³

2018

Proceedings of the 51st Hawaii International Conference on System Sciences

Self Cite

View full text Add to dashboard Cite

show abstract

“…20 However, these retrospectives are generally seen as extra workload in organizations. 62 Therefore, sprint retrospective meeting is omitted and the activities from this meeting are integrated into the sprint review meeting, 64 which is conducted at the end of a 4-week sprint. This is intended to make it so that the activities related to the sprint retrospective will be seen as indispensable in the Scrum team so that the team can be more productive.…”

Section: Scrum Meetingsmentioning

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

“…The authors presented an in-depth single case study, which in turn revealed that not all scrum principles are suitable in each context [51].…”

Section: Scrummentioning

confidence: 99%

Agile Software Development Methodologies: Survey of Surveys

Al-Zewairi¹,

Biltawi²,

Etaiwi³

et al. 2017

JCC

View full text Add to dashboard Cite

Agile software design and development methodologies have been gaining rigorous attention in the software engineering research community since their early introduction in the mid-nineties in addition to being highly adopted by the software development industry. In the last 15 years, an excessive number of research studies have been conducted on agile methods, a great number of notable methods have been proposed and various surveys have been presented by many researchers. In this study, the authors intend to conduct a literature survey study of the surveys of the different agile methodologies ranging from January 2000 to December 2015 using an intuitive research methodology called "Compare and Review" (CR). Furthermore, these survey papers were classified into four major categories according to their area of study. Additionally, the newly proposed agile methodologies that have not been addressed yet in any other literature review were reviewed and compared in terms of where the changes that they proposed lay on the SDLC.

show abstract

Do Daily Scrums Have to Take Place Each Day? A Case Study of Customized Scrum Principles at an E-commerce Company

Cited by 16 publications

References 25 publications

Antecedents and Consequences of Time Pressure in Scrum Projects: Insights from a Qualitative Study

Antecedents and Consequences of Time Pressure in Scrum Projects: Insights from a Qualitative Study

Blended Scrum model for software development organizations

Agile Software Development Methodologies: Survey of Surveys

Contact Info

Product

Resources

About