Communication and Documentation Practices in Agile Requirements Engineering: A Survey in Polish Software Industry

Jarzębowicz, Aleksander; Sitko, Natalia

doi:10.1007/978-3-030-29608-7_12

Cited by 10 publications

(9 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Nevertheless, we believe that one of the key principles of the original Agile Manifesto, that is, face-to-face conversations being the most productive way of conveying information, 68 became somewhat outmoded despite being held in high esteem. 36,69 This is mainly due to the high efficiency of the virtual communication schemes and environments in place upon their tuning, which at the same time prepared the program to operate in COVID-19 conditions. The joint research effort of practitioners and researchers enabled a number of organizational enhancements, the vast majority of which have found their permanent place in the host company.…”

Section: Discussionmentioning

confidence: 99%

“…Last but not least, the feedback from the conducted study constitutes a voice in opposition to considering additional meetings in terms of a challenge by, for example, Uludağ et al 67 Of course, we would suggest assigning a high priority to a comprehensive review of communication practices and infrastructure in place, as some of them initially felt short of expectations given the considerable responsibility and intensity of communication inherent to scaled‐up Scrum. Nevertheless, we believe that one of the key principles of the original Agile Manifesto, that is, face‐to‐face conversations being the most productive way of conveying information, 68 became somewhat outmoded despite being held in high esteem 36,69 . This is mainly due to the high efficiency of the virtual communication schemes and environments in place upon their tuning, which at the same time prepared the program to operate in COVID‐19 conditions.…”

Section: Discussionmentioning

confidence: 99%

See 1 more Smart Citation

Scaled agile framework. Dealing with software process‐related challenges of a financial group with the action research approach

Kowalczyk

Marcinkowski

Przybyłek

2022

J Software Evolu Process

View full text Add to dashboard Cite

This article reports on a domain-specific software development venture at Nordea. We explore organizational constraints, challenges, and corrective actions undertaken when scaling the agile development approach of their Core Banking Platform program. The fit and required customizations of the rather complex and rigid SAFe framework in a policy-heavy financial institution are audited against the organic growth of the program. In a qualitative study with three cycles using the Action Research method, both organizational and technical restrictions were tackled jointly with the company employees. Thirty-four potential solutions were developed-some of which turned out to be dead-ends. Ultimately, the effectiveness of prior recommendations was tested in a highly challenging implementation environment, and the list of guidelines was extended. We discovered several meeting and collaboration schemes that are not fully aligned with previous reports.

show abstract

Section: Discussionmentioning

confidence: 99%

Section: Discussionmentioning

confidence: 99%

Scaled agile framework. Dealing with software process‐related challenges of a financial group with the action research approach

Kowalczyk

Marcinkowski

Przybyłek

2022

J Software Evolu Process

View full text Add to dashboard Cite

show abstract

“…Recently, several surveys were conducted among Polish and Ukrainian IT specialists on various aspects of Requirements Engineering, such as requirements elicitation [8,9] or specification [10,19,20].…”

Section: Surveys and Experiments With Industrymentioning

confidence: 99%

What Should a Good Software Requirements Specification Include? Results of a Survey

Rączkowska-Gzowska

Walkowiak-Gall

2023

Foundations of Computing and Decision Sciences

View full text Add to dashboard Cite

Software requirements specification is an important foundation of the software development process. It documents the requirements, expectations, and restrictions for a system to be developed. It should describe what the produced system will offer in detail and unambiguously. It should also provide a realistic basis for estimating product costs, risks, and schedules. Still, it is difficult to prepare a useful specification effectively. We want to propose an approach to creating a good specification. We started the work from scratch by determining what the scope of the specification should be. We asked people who work on IT projects what information is and should be included in the specifications with which they work. This paper presents results from a survey conducted with 163 participants who have experience working on commercial software development projects. The main observation is that the content of requirements specification differs with respect to project characteristics, such as industry or financing method. We also noticed that the information about integration with external systems and functionalities most often appears in the SRS.

show abstract

“…Due to their positive impact on productivity, agile methods have become mainstream in the software industry (Cao et al 2009 ; Mundra et al 2013 ; Eloranta et al 2016 ; Schön et al 2017 ; Gaikwad et al 2019 ; Butt et al 2019 ; Jarzębowicz and Sitko 2019 ; Küpper et al 2019 ). Nevertheless, despite numerous agile transformation success stories, most organizations struggle to fully implement an agile method (VersionOne, 2020).…”

Section: Introductionmentioning

confidence: 99%

Game-based Sprint retrospectives: multiple action research

Przybyłek

Albecka²,

Springer

et al. 2021

Empir Software Eng

View full text Add to dashboard Cite

In today’s fast-paced world of rapid technological change, software development teams need to constantly revise their work practices. Not surprisingly, regular reflection on how to become more effective is perceived as one of the most important principles of Agile Software Development. Nevertheless, running an effective and enjoyable retrospective meeting is still a challenge in real environments. As reported by several studies, the Sprint Retrospective is an agile practice most likely to be implemented improperly or sacrificed when teams perform under pressure to deliver. To facilitate the implementation of the practice, some agile coaches have proposed to set up retrospective meetings in the form of retrospective games. However, there has been little research-based evidence to support the positive effects of retrospective games. Our aim is to investigate whether the adoption of retrospective games can improve retrospective meetings in general and lead to positive societal outcomes. In this paper, we report on an Action Research project in which we implemented six retrospective games in six Scrum teams that had experienced common retrospective problems. The received feedback indicates that the approach helped the teams to mitigate many of the “accidental difficulties” pertaining to the Sprint Retrospective, such as lack of structure, dullness, too many complaints, or unequal participation and made the meetings more productive to some degree. Moreover, depending on their individual preferences, different participants perceived different games as having a positive impact on their communication, motivation-and-involvement, and/or creativity, even though there were others, less numerous, who had an opposite view. The advantages and disadvantages of each game as well as eight lessons learned are presented in the paper.

show abstract

Communication and Documentation Practices in Agile Requirements Engineering: A Survey in Polish Software Industry

Cited by 10 publications

References 17 publications

Scaled agile framework. Dealing with software process‐related challenges of a financial group with the action research approach

Scaled agile framework. Dealing with software process‐related challenges of a financial group with the action research approach

What Should a Good Software Requirements Specification Include? Results of a Survey

Game-based Sprint retrospectives: multiple action research

Contact Info

Product

Resources

About