Agile Requirements Engineering for a Social Insurance for Occupational Risks Organization: A Case Study

Pichler, Mario; Rumetshofer, Hildegard; Wahler, Wilhelm

doi:10.1109/re.2006.8

Cited by 17 publications

(19 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…It is vital for the teams to coordinate with each other to develop a common understanding of the requirements, to communicate changes made in the requirements, and to work out what needs to be done. In the requirements engineering process teams usually coordinate in two ways [23] using predefined processes, namely, by requirement management and tracking tools, and by communicating with each other [24] [25]. Communication is widely observed because it replaces documentation, which is one of the advantages of agile methods [15].…”

Section: Mapping Of Social Factors Impacting Requirements-drivenmentioning

confidence: 99%

“…Communication is widely observed because it replaces documentation, which is one of the advantages of agile methods [15]. The awareness of one another's work [24] [26] is a necessary perquisite for coordination and helps in knowledge exchange [27], which leads to a better level of communication. Based on literature review Figure 2 is drawn to show the incorporation of socio-technical aspects in requirements engineering phases.…”

Section: Mapping Of Social Factors Impacting Requirements-drivenmentioning

confidence: 99%

See 1 more Smart Citation

Socio-technical aspects of requirements-driven collaboration (RDC) in agile software development methods

Inayat

Salim

Kasirun

2012

2012 IEEE Conference on Open Systems

View full text Add to dashboard Cite

Requirements engineering is a collaborative process carried out with the mutual cooperation and coordination of stakeholders. Requirements-driven collaboration is of crucial and utmost importance in case of agile methods, especially for geographically distributed teams. Socio technical aspects have been discussed in literature for collaborative design and group work activities. Similarly this paper describes the socio-technical aspects in context of requirements engineering for agile methods. Precisely, in this paper we have twofold objectives; first we have mapped requirements engineering phases with agile methods workflow and secondly explored the socio-technical aspects of requirements-driven collaboration within agile methods. Thus this paper provides a new dimension of reviewing the socio technical aspects for requirements-driven collaboration and their alignment with agile iterations.

show abstract

Section: Mapping Of Social Factors Impacting Requirements-drivenmentioning

confidence: 99%

Section: Mapping Of Social Factors Impacting Requirements-drivenmentioning

confidence: 99%

Socio-technical aspects of requirements-driven collaboration (RDC) in agile software development methods

Inayat

Salim

Kasirun

2012

2012 IEEE Conference on Open Systems

View full text Add to dashboard Cite

show abstract

“…As shown by a growing number of research studies [4], this is particularly the case for Scrum [5], which has been successfully applied to different types of companies and projects [1]. Due to this success, Scrum principles have been adopted in other domains, including product management [1,6].…”

Section: Introductionmentioning

confidence: 99%

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

Pauly

Michalik

Basten

2015

2015 48th Hawaii International Conference on System Sciences

View full text Add to dashboard Cite

Agile development approaches, such as Scrum, continue to gain importance in today's world. Since previous research has predominantly treated development approaches as a black box, we answer the call for empirical research concerning adoption of agile methods. The study's aim is to assess the adoption or adaption of Scrum principles at an e-commerce company. The findings of our in-depth single case study reveal that not all Scrum principles are suitable in each context. By discussing the reasons for adopting or adapting the principles, we contribute to a deeper understanding of agile methods and help to open the black box of development approaches in information systems research. The in-depth insights gained at our case company provide practitioners a useful reference for adapting agile methods to their specific contexts.

show abstract

“…A case study describing the use of agile requirements engineering is described by Pichler et al [23]. However, the paper does not provide details regarding the agile requirements engineering process.…”

Section: Introductionmentioning

confidence: 99%

The agile requirements refinery: Applying SCRUM principles to software product management

Vlaanderen

Jansen

Brinkkemper

et al. 2011

Information and Software Technology

101

View full text Add to dashboard Cite

Agile Requirements Engineering for a Social Insurance for Occupational Risks Organization: A Case Study

Cited by 17 publications

References 3 publications

Socio-technical aspects of requirements-driven collaboration (RDC) in agile software development methods

Socio-technical aspects of requirements-driven collaboration (RDC) in agile software development methods

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

The agile requirements refinery: Applying SCRUM principles to software product management

Contact Info

Product

Resources

About