Comparing Agile Software Processes Based on the Software Development Project Requirements

Author(s):  
Malik Qasaimeh ◽  
Hossein Mehrfard ◽  
Abdelwahab Hamou-Lhadj
2021 ◽  
pp. 875697282096030
Author(s):  
Meghann L. Drury-Grogan

This study examines changing team cognition and cognitive artifact use as agile software development iterations progress to better understand team member interactions. The four case studies conducted observed the distributed cognition on the team changing from planning, managing, developing, and concluding tasks in iterations to deliver working functionality. Cognitive artifacts used throughout the iteration also changed. This study provides a clearer understanding of how and when team cognition and artifact use change as agile software development teams use artifacts to manage projects. Interactions between team members and artifacts move from individual to social interactions as the iteration progresses with frequent, short, continuous communication and interactions.


Author(s):  
César Jesús Pardo Calvache ◽  
Piedad Rocío Chilito Gomez ◽  
Daniel Esteban Viveros Meneses ◽  
Francisco José Pino Correa

Nowadays, carrying out a project management is difficult in any situation, even more in global projects of software development, whose environment faces different aspects that make this type of projects even more difficult to manage, for example: lack of coordination, lack of face to face communication, temporary differences, cultural diversity and application of different standards, models and approaches. With the aim of supporting agile global software development (AGSD)  project management when multiple models are present, we have defined Scrum+, which is a guide based on Scrum and defines a set of activities, tasks, roles and criteria to support AGSD projects in multimodel environments. We carried out the harmonization of agile approach Scrum along with project management practices defined in multiple models such as: ISO/IEC 15504, ISO 9001 and CMMI-DEV.  Likewise, the evaluation of the proposal has been conducted through: (i) its application in a focus group with experts in different related areas and (ii) its assessment of the degree of agility by means 4-DAT method. Based on the analysis of the results and the comments obtained in the focus group, Scrum+ seems to be clear, adequate, and agile. The guide proposed here can serve as reference for studying further aspects related to agile software scaled projects.


2022 ◽  
pp. 247-279
Author(s):  
Inger Anne Tøndel ◽  
Martin Gilje Jaatun

Security requirement work plays a key role in achieving cost-effective and adequate security in a software development project. Knowledge about software companies' experiences of security requirement work is important in order to bridge the observed gap between software security practices and security risks in many projects today. Particularly, such knowledge can help researchers improve on available practices and recommendations. This article uses the results of published empirical studies on security requirement work to create a conceptual framework that shows key concepts related to work context, this work itself and the effects of this work. The resulting framework points to the following research challenges: 1) Identifying and understanding factors important for the effect of security requirements work; 2) Understanding what is the importance of the chosen requirements approach itself, and; 3) Properly taking into account contextual factors, especially factors related to individuals and interactions, in planning and analysis of empirical studies on security requirements work.


2021 ◽  
Vol 52 (2) ◽  
pp. 210-222
Author(s):  
Manuel Wiesche

Agile approaches help software development project teams to better meet user needs and ensure flexibility in uncertain environments. But using agile approaches invites changes to the project and increases interactions between team members, which both cause interruptions in the workplace. While interruptions can help in task completion and increase process flexibility, they can also hinder employee productivity. We conducted an exploratory study of four agile software development teams. Our analysis identified (1) programming-related work impediments, (2) interaction-related interruptions, and (3) interruptions imposed by the external environment, which were managed by improved information retrieval and reduced team dependencies.


Author(s):  
Inger Anne Tøndel ◽  
Martin Gilje Jaatun

Security requirement work plays a key role in achieving cost-effective and adequate security in a software development project. Knowledge about software companies' experiences of security requirement work is important in order to bridge the observed gap between software security practices and security risks in many projects today. Particularly, such knowledge can help researchers improve on available practices and recommendations. This article uses the results of published empirical studies on security requirement work to create a conceptual framework that shows key concepts related to work context, this work itself and the effects of this work. The resulting framework points to the following research challenges: 1) Identifying and understanding factors important for the effect of security requirements work; 2) Understanding what is the importance of the chosen requirements approach itself, and; 3) Properly taking into account contextual factors, especially factors related to individuals and interactions, in planning and analysis of empirical studies on security requirements work.


Sign in / Sign up

Export Citation Format

Share Document