scholarly journals Design Thinking: Challenges for Software Requirements Elicitation

Information ◽  
2019 ◽  
Vol 10 (12) ◽  
pp. 371 ◽  
Author(s):  
Hugo Ferreira Martins ◽  
Antônio Carvalho de Oliveira Junior ◽  
Edna Dias Canedo ◽  
Ricardo Ajax Dias Kosloski ◽  
Roberto Ávila Paldês ◽  
...  
Keyword(s):  
Design Thinking ◽  
Requirements Elicitation ◽  
Software Requirements ◽  
Agile Methods ◽  
Software Project ◽  
Functional Requirements ◽  
Use Of Data ◽  
Development Teams ◽  
Software Development Teams ◽  
User Workshop

Agile methods fit well for software development teams in the requirements elicitation activities. It has brought challenges to organizations in adopting the existing traditional methods, as well as new ones. Design Thinking has been used as a requirements elicitation technique and immersion in the process areas, which brings the client closer to the software project team and enables the creation of better projects. With the use of data triangulation, this paper brings a literature review that collected the challenges in software requirements elicitation in agile methodologies and the use of Design Thinking. The result gave way to a case study in a Brazilian public organization project, via user workshop questionnaire with 20 items, applied during the study, in order to identify the practice of Design Thinking in this context. We propose here an overview of 13 studied challenges, from which eight presented strong evidence of contribution (stakeholders involvement, requirements definition and validation, schedule, planning, requirement details and prioritization, and interdependence), three presented partial evidence of contribution and two were not eligible for conclusions (non-functional requirements, use of artifacts, and change of requirements). The main output of this work is to present an analysis of the use of Design Thinking to see if it fits properly to be used as a means of solving the challenges of elicitation of software requirements when using agile methods.

Design Thinking and Scrum in Software Requirements Elicitation: A Case Study

2019 ◽  
pp. 179-194
Author(s):  
Rafael dos Santos Braz ◽  
José Reinaldo Merlin ◽  
Daniela Freitas Guilhermino Trindade ◽  
Carlos Eduardo Ribeiro ◽  
Ederson Marcos Sgarbi ◽  
...  
Keyword(s):  
Design Thinking ◽  
Requirements Elicitation ◽  
Software Requirements

The effects of the relational dimension of social capital on tacit and explicit knowledge sharing: a mixed-methods approach

2021 ◽  
Vol ahead-of-print (ahead-of-print) ◽  
Author(s):  
Rosangela F. Santos ◽  
Mírian Oliveira ◽  
Carla Curado
Keyword(s):  
Social Capital ◽  
Mixed Methods ◽  
Knowledge Sharing ◽  
Explicit Knowledge ◽  
Agile Methods ◽  
Sufficient Condition ◽  
Content Type ◽  
Mixed Methods Approach ◽  
Development Teams ◽  
Software Development Teams

Purpose Knowledge sharing among individuals from different teams is rare. Agile methods encourage only the exchange of tacit knowledge within teams. This study aims to analyse the influence of trust, norms of cooperation and reciprocity on tacit and explicit knowledge sharing among individuals from different software development teams. Design/methodology/approach Data were collected using a cross-sectional survey involving 205 individuals working in software development teams. The authors adopted a mixed-methods approach involving partial least squares structural equation modelling (PLS-SEM) and fuzzy-set qualitative comparative analysis (fsQCA). Findings PLS-SEM shows: the antecedents have different influence in tacit knowledge sharing (TKS) and in explicit knowledge sharing (EKS); trust influences directly TKS, and it only influences EKS indirectly, while reciprocity influences TKS directly and EKS both directly and indirectly; norms of cooperation directly influence TKS, and they only influence EKS indirectly. Overall, the fsQCA findings support PLS-SEM results: TKS contributes to EKS; reciprocity or trust is a sufficient condition for TKS and EKS; norms of cooperation are a sufficient condition for TKS; larger firms without high levels of reciprocity and trust cannot expect TKS and EKS. The quantitative and qualitative results are aligned. Research limitations/implications The results cannot be generalisable because snowball sampling was used, and most of the respondents were Brazilians. Practical implications This study should help managers and scholars: to appreciate the relevancy of TKS among individuals using agile methods to nurture EKS and to understand the different effects of reciprocity, trust and norms of cooperation on both TKS and EKS. Originality/value Considering three constructs, this study uses a mixed-methods approach to investigate the potential of the relational dimension of social capital theory to leverage TKS and EKS, to overcome the limitations of agile methods. The originality of this study regards that it shows the constructs of relational social capital influencing TKS and EKS differently.

scholarly journals Analysing Time-Stamped Co-Editing Networks in Software Development Teams using git2net

2021 ◽  
Vol 26 (4) ◽  
Author(s):  
Christoph Gote ◽  
Ingo Scholtes ◽  
Frank Schweitzer
Keyword(s):  
Software Engineering ◽  
Computational Social Science ◽  
Software Project ◽  
High Resolution Data ◽  
Software Repositories ◽  
Fine Grained ◽  
Development Teams ◽  
History Of ◽  
Software Development Teams ◽  
Advance Theory

AbstractData from software repositories have become an important foundation for the empirical study of software engineering processes. A recurring theme in the repository mining literature is the inference of developer networks capturing e.g. collaboration, coordination, or communication from the commit history of projects. Many works in this area studied networks of co-authorship of software artefacts, neglecting detailed information on code changes and code ownership available in software repositories. To address this issue, we introduce , a scalable software that facilitates the extraction of fine-grained co-editing networks in large repositories. It uses text mining techniques to analyse the detailed history of textual modifications within files. We apply our tool in two case studies using repositories of multiple Open Source as well as a proprietary software project. Specifically, we use data on more than 1.2 million commits and more than 25,000 developers to test a hypothesis on the relation between developer productivity and co-editing patterns in software teams. We argue that opens up an important new source of high-resolution data on human collaboration patterns that can be used to advance theory in empirical software engineering, computational social science, and organisational studies.

scholarly journals Towards Scrum Based Agile Framework for Global Software Development Teams

2019 ◽  
Vol 38 (4) ◽  
pp. 979-998
Author(s):  
Shagufta Shafiq ◽  
Yaser Hafeez ◽  
Sadia Ali ◽  
Naila Iqbal ◽  
Muhammad Jamal
Keyword(s):  
Software Development ◽  
Development Process ◽  
Empirical Evaluation ◽  
Distributed Teams ◽  
Agile Methods ◽  
Functional Development ◽  
Development Teams ◽  
Software Development Teams ◽  
Communication And Coordination ◽  
Framework Development

Organizations are moving their workforce to guarantee matters of trade and profit where accounts are expected to be less expensive and provide better quality products with the accessibility of skilled labor. With the evident benefits, distributed teams often face challenges with reliable and efficient communication coordination patterns that lead towards project failure. In the rapidly growing software industry, it becomes critical for any business to have better management activities to acquire right processes and practices. Agile methods are considered as a remedy for mitigating distributed teams’ challenges, with their consistent focus on communication. Here, we intend to propose a tailored Scrum based solution for distributed teams that empowers anticipated communication and coordination throughout the development process. In the first phase of framework development we have evaluated the state of agile practices from both literature and industry; based on collected evidence and suggestive guidelines a scrum based agile framework was formulated. The Scrum is a project management method in Agile Methods family. Scrum is an iterative process that asks for incremental development of the product, includes cross functional development and testing teams. Evaluation results show that the proposed framework contributes positively to improve development process quality. We have performed theoretical as well as empirical evaluation to validate proposed framework. We have eight project managing rising aspects in DSD (Distributed Software Development) to evaluate the proposed framework.

Knowledge at Work in Software Development

2005 ◽  
pp. 312-342
Author(s):  
Luca Iandoli ◽  
Giuseppe Zollo
Keyword(s):  
Knowledge Management ◽  
Software Development ◽  
Management Practices ◽  
Field Analysis ◽  
Software Project ◽  
Software Life Cycle ◽  
Software Applications ◽  
Development Teams ◽  
Software Development Teams ◽  
Methodological Aspects

Knowledge management practices in software development and engineering have been focused mainly on knowledge sharing and maintenance whereas less attention has been devoted to knowledge elicitation and codification issues. In this chapter we present a methodology based on causal mapping for the investigation and management of knowledge created and elaborated by software development teams in the production of new software applications. The chapter focuses on the early stages of the process when development teams have to make a choice regarding the software life cycle model that best fits, given constraints concerning ambiguity of the requirements, risks, costs evaluation and scheduling. A step-by-step application of the proposed methodology to a case study in a software company is presented to provide the reader with examples drawn from the field analysis and illustrates critical methodological aspects. Implications for knowledge management in software project development are then outlined and discussed.

scholarly journals Empirical and Statistical Study of Elicitation Complications

2016 ◽  
Vol 15 (7) ◽  
pp. 6940-6946
Author(s):  
Sidra Arshad ◽  
Hafiza Tahira Fazal ◽  
Tahir Nawaz
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Development Process ◽  
Statistical Study ◽  
Requirement Engineering ◽  
Requirements Elicitation ◽  
Software Requirements ◽  
Software Development Process ◽  
Functional Requirements ◽  
Statistical Software

The performance of Requirement Engineering is like framework for software development process. All-inclusive software has four mainstays of requirement engineering processes i.e. Functional and non-functional requirements, design,implementation and testing build the complete software fortification on top of the mainstays. Requirement engineers have to face numerous challenges to develop successful and impressive software. Requirements Engineering (RE) leads software development process. Different constraints and needs of users are explored as well as hitches in previous system are depicted. The scope of this study is to exemplify the difficulties faced by users in the utmost maiden phase of RE Requirements Elicitation and a framework is presented as well. A survey was conducted in different campuses of Universities in Pakistan for this purpose. Questionnaire was distributed among project development students of various disciplines to gather and highlighted the problems during Requirements Elicitation. Finally the predictive statistical software SPSS was used to input the collected data for more precise calculations, the results of which are discussed in section 3.

scholarly journals Cherry Picking - Agile Software Development Teams Applying Design Thinking Tools

2021 ◽  
pp. 201-206
Author(s):  
Franziska Dobrigkeit ◽  
Christoph Matthies ◽  
Philipp Pajak ◽  
Ralf Teusner
Keyword(s):  
Software Development ◽  
Design Thinking ◽  
Agile Software Development ◽  
Agile Development ◽  
Daily Work ◽  
Software Products ◽  
Development Teams ◽  
Software Development Teams ◽  
Agile Software ◽  
Support Software

AbstractDesign Thinking (DT) is an established approach to conceptualize software products before starting the product development work. Research suggests that software development can benefit from a continuous integration of DT throughout Agile development processes. However, practitioners and researchers lack an in-depth understanding of which tools from the ever-growing DT toolbox are suited to support software development teams and their processes and how these tools can be applied to the teams’ daily work. As initial steps towards closing this knowledge gap, we present our experiences from testing five different DT tools from a previously developed toolbox with four Agile software development teams. Each team chose three tools to apply to their product, problem, and context during a workshop. We present summarised findings regarding the use cases, benefits, and challenges of these tools as experienced by the participants. Overall, the teams welcomed the DT tools and were able to independently apply them to achieve the desired effects, e.g., to highlight user needs, find product issues, and discover team challenges.

Sign in / Sign up

Export Citation Format

Share Document