Misfit or Misuse? Lessons from Implementation of Scrum in Radical Product Innovation

Hosbond, Jens Henrik; Nielsen, Peter Axel

doi:10.1007/978-3-540-68255-4_3

Cited by 4 publications

(4 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Simply adopting agile development practices on their own is insufficient to ensure that a company remains innovative. This is consistent with Hosbond and Nielsen [23]. Developers need to feel that the environment supports and is open to innovation before they will make a contribution [8,32].…”

Section: Discussionsupporting

confidence: 83%

Fostering and Sustaining Innovation in a Fast Growing Agile Company

Moe

Barney

Aurum

et al. 2012

Product-Focused Software Process Improvement

View full text Add to dashboard Cite

Abstract. Sustaining innovation in a fast growing software development company is difficult. As organisations grow, peoples' focus often changes from the big picture of the product being developed to the specific role they fill. This paper presents two complementary approaches that were successfully used to support continued developer-driven innovation in a rapidly growing Australian agile software development company. The method "FedEx™ Day" gives developers one day to showcase a proof of concept they believe should be part of the product, while the method "20% Time" allows more ambitious projects to be undertaken. Given the right setting and management support, the two approaches can support and improve bottom-up innovation in organizations.

show abstract

Section: Discussionsupporting

confidence: 83%

Fostering and Sustaining Innovation in a Fast Growing Agile Company

Moe

Barney

Aurum

et al. 2012

Product-Focused Software Process Improvement

View full text Add to dashboard Cite

show abstract

“…Agile Methodologies have already proven beneficial as regards reducing the delivery time of working software, improving customer collaboration, estimating time and handling defects processes [25]. Some studies, however, suggest that the existing agile approaches, when used during the requirements analysis phase, are prone to focus only on scoping and simplicity rather than on problem solving and discovery [91,37]. Considering that requirements elicitation plays a determining role in the development process and that it is characterized by ambiguity, uncertainty, and unpredictability [75], it has been proposed that agile processes be extended with creative techniques in order to manage complex software developments [35,54,52,49].…”

Section: Objective Of the Systematic Review And Definition Of Researc...mentioning

confidence: 99%

“…Some studies suggest that the existing agile approaches employed during the requirements analysis phase tend to focus solely on scoping and simplicity rather than on problem solving and discovery [91,37]. This results in the inability to develop innovative solutions.…”

Section: Introductionmentioning

confidence: 99%

Leveraging creativity in requirements elicitation within agile software development: A systematic literature review

Aldave

Vara

Granada

et al. 2019

Journal of Systems and Software

View full text Add to dashboard Cite

Agile approaches tend to focus solely on scoping and simplicity rather than on problem solving and discovery. This hampers the development of innovative solutions. Additionally, little has been said about how to capture and represent the real user needs. To fill this gap, some authors argue in favor of the application of "Creative thinking" for requirements elicitation within agile software development. This synergy between creativeness and agility has arisen as a new means of bringing innovation and flexibility to increasingly demanding software.The aim of the present study is therefore to employ a systematic review to investigate the state-of-the-art of those approaches that leverage creativity in requirements elicitation within Agile Software Development, as well as the benefits, limitations and strength of evidence of these approaches.The review was carried out by following the guidelines proposed by Dr. Kitchenham. The search strategy identified 1451 studies, 17 of which were eventually classified as primary studies. The selected studies contained 13 different and unique proposals. These approaches provide evidence that enhanced creativity in requirements elicitation can be successfully implemented in real software projects. We specifically observed that projects related to user interface development, such as those for mobile or web applica-

show abstract

“…Although Sutherland (2001), who is one of the originators of the method, describes how the Scrum method has evolved over years in practical setting, the details of these settings and the data are not disclosed. More recently, however, real life empirical studies on Scrum have increased substantially (Rising and Janoff 2000;Jensen and Zilmer 2003;Dingsøyr et al 2006;Hosbond et al 2008;Marchenko and Abrahamsson, 2008).…”

Section: Empirical Evidencementioning

confidence: 99%

Agile Software Development Methods: A Comparative Review1

Abrahamsson

Oza

Siponen

2010

Agile Software Development

125

138

View full text Add to dashboard Cite

Although agile software development methods have caught the attention of software engineers and researchers worldwide, scientific research still remains quite scarce. The aim of this study is to order and make sense of the different agile approaches that have been proposed. This comparative review is performed from the standpoint of using the following features as the analytical perspectives: project management support, life-cycle coverage, type of practical guidance, adaptability in actual use, type of research objectives and existence of empirical evidence. The results show that agile software development methods cover, without offering any rationale, different phases of the software development life-cycle and that most of these methods fail to provide adequate project management support. Moreover, quite a few methods continue to offer little concrete guidance on how to use their solutions or how to adapt them in different development situations. Empirical evidence after ten years of application remains quite limited. Based on the results, new directions on agile methods are outlined.

show abstract

Misfit or Misuse? Lessons from Implementation of Scrum in Radical Product Innovation

Cited by 4 publications

References 11 publications

Fostering and Sustaining Innovation in a Fast Growing Agile Company

Fostering and Sustaining Innovation in a Fast Growing Agile Company

Leveraging creativity in requirements elicitation within agile software development: A systematic literature review

Agile Software Development Methods: A Comparative Review1

Contact Info

Product

Resources

About