scholarly journals Dynamic Agile Distributed Development Method

Mathematics ◽  
2019 ◽  
Vol 7 (10) ◽  
pp. 963 ◽  
Author(s):  
Muhammad Asgher Nadeem ◽  
Scott Uk-Jin Lee

“Agile” is an effective software engineering model with a high trust and acceptance rate among its users. The term agility comes from the concept of rapid development and working in a team for better results and a faster competition rate when compared with any other software engineering model. In this study, an assessment of the different patterns, frameworks, and application program interfaces available for distributed development in an agile model is given. After analyzing the state-of-the-art distributed models, a novel framework of a dynamic agile distributed development method (DADDM) is introduced in this paper. Many researchers have worked on global software development using the agile approach; however, we are presenting the idea of incorporating the agile benefits with dynamic distributed software development. The applicability of the proposed model is checked via two selected parameters: a feasibility study and a business study. The complete DADDM development life cycle is presented in the methodology section. The techniques used in DADDM and team members’ roles and responsibilities in DADDM are defined in this study. This study reflects all pillars of planning, controlling, organizing, and management of leadership. The use of DADDM in distributed agile development encourages future researchers to use this proposed framework for comparison and testing of their models and to check the effectiveness through a comparison with DADDM.

Author(s):  
Vinay Kukreja ◽  
Amitoj Singh

In the globalization of fast changing business and technology environment, it becomes very important to respond quickly to changing user requirements. Traditional methodologies are not appropriate for the projects where user requirements are not fixed. Agile methodologies have been developed to cope up with user changing requirements and emphasize more on working software and customer collaboration. Agile is an umbrella term and it is used for many software development methodologies which shares common characteristics. This chapter mainly focuses on the working methodology of agile development and the usage areas of industry where agile development is implemented. Agile software development is difficult in distributed environment as the team members are at distributed locations. This chapter discusses agile industry applicability enablers which are useful for agile software development in distributed environment.


2017 ◽  
Vol 1 (1) ◽  
pp. 1 ◽  
Author(s):  
Mufadhol Mufadhol ◽  
Siswanto Siswanto ◽  
Djarot Dian Susatyono ◽  
Maya Utami Dewi

Progress of science and technology is very influential to development of software engineering. Communication between software developers and prospective users of software engineering by prototype system is very important in the development of software engineering. Research and Development method in research of software engineering is very suitable be used because supports the existence of such communications. But it is found there are several research that use this method with not perfect or not completed, so research results produced less fit with purpose. This paper will be explain how to used the stages must be carried out in research of software engineering with the method of research and development, in order to make the research more be effectively and efficiently as well as software development efforts that simultaneously accompanied by the validation effort for the results to be achieved in accordance with the expected goals.


Software industries have been growing with the rise of automation technologies and looking for change in their software development practices to gain the benefits of automation technologies for achieving their business goals. Agile Business Process Reengineering (ABPR) is trending approach for Software Engineering Management (SEM) in software industries, which helps software development organization in transformation of software development practices. Scrum and Kanban are fascinating Agile methodologies adopted by Software Engineering Management practitioners. Scrumban, a mixture of both Scrum and Kanban, has derived strengths of both frameworks, in formation of a robust framework against challenges of Agile Software Engineering (ASE) methodologies like work flow control, lead time management, product delivery that could not be solved by Scrum or Kanban as a standalone framework. But still some of challenges, which are out of scope of Scrumban like project requirement documentation, planning, scheduling, estimation and clear product vision at initial stage of the project. Such issues have raised a request of research for Software Process Reengineering (SPR) in Scrumban by customizing its structure for to form the next level of hybrid framework. The Traditional SDLC methodology ‘Waterfall’ has answers for such issues. An empirical analysis, for resolution of such issues, with the help of ‘Waterfall’ model and its life cycle protocols is the main goal this research study by integrating Scrum and Kanban with Waterfall to form a hybrid framework ‘Scrumbanfall’ aligning Kanban in center of integration under the boundary of Scrum rules. This research also highlights limitations of Scrumbanfall like team members and their roles and capabilities for the large scaled project having team members in distributed environment, which open the door for next level of research to overcome such challenges using further hybridization of Scrumbanfall.


Author(s):  
Sofiane Sahraoui

Open source software (OSS) development has been a trend parallel to that of agile software development, which is the highly iterative development model following conventional software engineering principles. Striking similarities exist between the two development processes as they seem to follow the same generic phases of software development. Both modes of development have less emphasis on planning and design and a more prominent role for implementation during the software engineering process. This chapter expounds on this connection by adopting an agile perspective on OSS development to emphasize the similarities and dissimilarities between the two models. An attempt is first made to show how OSS development fits into the generic agile development framework. Then, the chapter demonstrates how the development process of Mozilla and Apache as two of the most famous OSS projects can be recast within this framework. The similarity discussed and illustrated between agile and OSS development modes is rather limited to the mechanics of the development processes and do not include the philosophies and motivations behind development.


i-com ◽  
2015 ◽  
Vol 14 (2) ◽  
Author(s):  
Hartmut Schmitt ◽  
Dominik Magin ◽  
Andreas Maier ◽  
Richard Wacker ◽  
Josh Wang

AbstractSmall and medium-sized enterprises (SMEs) increasingly rely on agile software development. However, the majority of established usability methods have been developed with traditional software engineering principles in mind. So, one might assume that these methods and tools might not be applicable to agile development projects. In this paper, a possible approach to systematically adapting traditional usability methods to application in agile projects is introduced and documented as best practices. These best practices can be quickly and dynamically employed by agile development team members and can thus contribute to higher quality of software development outputs. The approach described in this paper was developed in the context of a German research project funded by the German Federal Ministry of Education and Research (BMBF) and conducted by one research institute and three software-developing enterprises and will be evaluated throughout the further course of the project. For this purpose, a number of best practices have been adapted to the context of agile software development and described in detail in order to allow inexperienced software developers of small and medium-sized enterprises to successfully apply these best practices. As two examples of these best practices, we illustrate the best practices ‘Contextual Inquiry’ and ‘Template-Based UI Design’ in this paper.


VINE ◽  
2014 ◽  
Vol 44 (3) ◽  
pp. 394-419 ◽  
Author(s):  
Roopesh Kevin Sungkur ◽  
Mayvin Ramasawmy

Purpose – The purpose of this paper is to propose Knowledge4Scrum, a novel knowledge management tool for agile distributed teams. Agile software development (ASD) refers to a group of software development methodologies based on iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams. The two most widely used methodologies based on the agile philosophy are scrum and extreme programming. Whichever methodology is considered, agile teams usually consist of few members and are collocated under the same roof. However, nowadays, agile practices for distributed development are gaining much momentum. The main reasons behind such practice are cheaper skilled labour, minimizing production cost, reducing time to market and increasing the quality and performance of projects. Along with the benefits obtained through globally distributed development, there are, however, many difficulties faced by various organisations. These problems are caused mostly due to distance, time and cultural differences. To meet up with the level of complexity of projects, ASD also has to keep up with many challenges, especially in cases of distributed teams. Four major challenges have been identified. First, the introduction of global software development entails a number of difficulties, especially related to knowledge sharing. For instance, lack of transparency is frequently observed within such teams, whereby a team member is totally unaware of the activities of his/her colleagues. Second, the unavailability of team members due to time zone differences adds up to the list of problems confronted by distributed teams. Third, there can be misunderstanding amongst the team member due to communication problems, especially in cases where the mother language of the team members is different. Fourth, a common issue faced by distributed teams is the loss of knowledge when an employee resigns from his/her post. Design/methodology/approach – Based on the main problems outlined above, what has been proposed is Knowledge4Scrum, a novel knowledge management tool for agile distributed teams. Knowledge4Scrum will act as a global repository for knowledge sharing in Scrum distributed teams with the possibility of creating new knowledge through data mining techniques. Valid past projects data have been collected to train and test the data mining models. The research also investigates the suitability of knowledge management in Scrum distributed teams to address the various challenges addressed above. Findings – Knowledge4Scrum supports the four knowledge management processes, namely, knowledge creation/acquisition, knowledge storage, knowledge dissemination and knowledge application. It has been found that the aforementioned tool satisfactorily addressed issues of distance, time and cultural differences that crop-up in distributed development teams. Data mining has been the main aspect for the knowledge creation and application processes, whereby new knowledge has been determined by examining and extracting patterns from existing data found in the repository. Originality/value – A major feature of the Knowledge4Scrum tool lies in the knowledge creation and application section, where a number of data mining techniques have been utilised to identify trends and patterns in past data collected. When compared to the COnstructive COst MOdel to estimate project duration, Knowledge4Scrum gives more than satisfactory results. Such functionalities will actually help managers for future project planning and in decision-making.


Author(s):  
Ali Sever

In distributed agile software development, to conquer the problems raised by rapid development of complex products with ever changing technological advances and risks, there is a need of a model with specific tools and technology supported approaches to manage them. Distributed environment has challenges and complexities in many ways of over collocated teams. However, they seem to enhance the basic principles in which agile methodology thrives on. Agile projects and distributed projects are compatible and therefore practices, principles, tools, and techniques for distributed agile software development are introduced to the distributed teams to ensure that the agile projects become successful. Although cloud computing is well established for software system developments, its effect on agile methodology has not been extensively studied. This study outlines how agile projects can be modeled in the cloud-computing era, namely, seamless agile-cloud integration. We propose a model to improve Agile Methodology in distributed computing platform. This model has uncovered a gap between the distributed agile development phases that are overemphasized and the phases that require actual attention. In addition to this, emphasis on appropriate phases would help build desired software that can exploit the benefits of cloud computing in numerous ways.


Electronics ◽  
2021 ◽  
Vol 10 (19) ◽  
pp. 2341
Author(s):  
Rashid Ali Khan ◽  
Muhammad Faisal Abrar ◽  
Samad Baseer ◽  
Muhammad Faran Majeed ◽  
Muhammad Usman ◽  
...  

Agile software development methodologies have become the most popular software development methods in the last few years. These methodologies facilitate rapid development. The low cost and prioritized user satisfaction make these methodologies more attractive. These methodologies were also intended for small scale developmental teams. Therefore, challenges were encountered when these methodologies were used in large-scale development teams. This study was based on the identification of factors which were discovered in our previous study. Some of the factors included “leadership strong commitment and team autonomy”, “cooperative organizational culture”, and “team competency—agile development expertise”. A total of 147 practices were identified in this study via a systematic literature review. These practices will help practitioners and project managers to adopt agile software methodologies and encourage them to the enhance them.


2020 ◽  
Vol 9 (2) ◽  
pp. 264
Author(s):  
Kharis Anwar ◽  
Lilik Dwi Kurniawan ◽  
M. Ijur Rahman ◽  
Nur Ani

Competition in sports field leasing is quite fast these days, making sports field managers improve facilities and provide competitive prices to attract sports field tenants. However, this progress was not accompanied by advances in technology so that sports field managers still had to do the manual method for field operations and promotion. On the side of the tenants of the sports field also still have to go to the sports field to find out the availability of schedules, facilities, and prices offered. Then many tenants who have an interest in exercising more than one branch of sport, therefore researchers use the concept of a marketplace that can bring together the managers of sports fields with field tenants in one container. In the application development process, it is done by using the agile method application development method because in its development it can be possible to collaborate and correct each other among team members to increase the customer satisfaction ratio. The application implementation uses the Laravel framework, PHP for programming language, and the MySQL for Database Management System. The results of the study can be concluded that the use of the marketplace concept can bring together prospective field tenants with many field managers and the ease of finding a sports field following the wishes of tenants by selecting the category of field, price and closest location and the manager of the sports field can promote the sports field by registering the field.


Sign in / Sign up

Export Citation Format

Share Document