To see the other types of publications on this topic, follow the link: Agile systems development methodologies.
Journal articles on the topic 'Agile systems development methodologies'
Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles
Consult the top 50 journal articles for your research on the topic 'Agile systems development methodologies.'
Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.
You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.
Browse journal articles on a wide variety of disciplines and organise your bibliography correctly.
1
Binsaleh, Muazzan, and Shahizan Hassan. "Systems Development Methodology for Mobile Commerce Applications." International Journal of Online Marketing 1, no. 4 (October 2011): 33–47. http://dx.doi.org/10.4018/ijom.2011100103.
Full textAbstract:
There are several systems development methodologies including traditional and agile methodologies being utilized in current systems development. However, it could be argued that when developing mobile commerce applications, suitable development framework should be investigated as these applications are utilized in different contexts from fixed ecommerce applications. This study identifies suitable system development methodology framework for mobile commerce applications. In order to achieve this aim, the practitioners from seven organizations were asked to provide information about their development methodologies by answering the questions regarding mobile commerce application development. The questions were opened and aimed to explore practitioner’s perspectives on the development methodologies. From the practitioner’s perspectives, it was found that there were several development methodologies being used in mobile commerce application development and these can be classified into two different development frameworks which are heavyweight/traditional and lightweight/agile methodologies. The suitable methodology framework for mobile commerce application development thus was identified.
2
Shahzeb Hussain, Namrata Bhadri, and Syed Razauddin Shahlal. "Factors Influencing the Efficacy of Agile Usage." International Journal of Engineering and Management Research 10, no. 5 (October 5, 2020): 1–4. http://dx.doi.org/10.31033/ijemr.10.5.1.
Full textAbstract:
Agile techniques that utilize iterative development are broadly used in various industry projects as a lightweight development technique which can satisfy the continuous changes of requirements. Short repetitions are used that are required for efficient product delivery. Traditional and old software development methods are not much efficient and effective to control the rapid change in requirements. Despite the benefits of Agile, criticism on agile methodology states that it couldn’t succeed to pay attention to architectural and design issues and therefore is bound to produce small design-decisions. The past decade has observed numerous changes in systems development with many organizations accepting agile techniques as a viable methodology for developing systems. An increase in the number of research studies reveals the growing demand and acceptance of agile methodologies. While most research has focused on acceptance rate and adaptation of agile practices, there is very limited knowledge of their post-adoption usage and incorporation within organizations. Several factors explain the effective usage of agile methodologies. A combination of previous research in Agile Methodologies, Diffusion of Innovations, Information Systems implementation, and Systems Development has been carried out to develop a research model that identifies the main factors relevant to the propagation and effective usage of agile methodologies in organizations.
3
Stormi, Kati Tuulikki, Teemu Laine, and Tuomas Korhonen. "Agile performance measurement system development: an answer to the need for adaptability?" Journal of Accounting & Organizational Change 15, no. 2 (June 3, 2019): 231–56. http://dx.doi.org/10.1108/jaoc-09-2017-0076.
Full textAbstract:
Purpose The purpose of this study is to reflect upon the feasibility of agile methodologies, Scrum in particular, to supplement the procedural design and implementation of performance measurement systems (PMS). Design/methodology/approach The study is an interventionist case study that applied agile methodologies in the PMS development. Researchers actively participated in the PMS development, e.g. researchers designed some of the performance measurement prototypes in order to facilitate the agile development. Findings The study outlines an agile approach suitable for PMS development. The paper answers the topical needs for adaptability and agility in management accounting, by applying agile methodologies into PMS development. PMS development does not take place only as a project or process that systematically progresses from the measure selection to measure implementation. Instead, as the requirements for the PMS change during the development project, management may reject some measures and new measures emerge as the understanding about changing situations increase. Agile methodologies are a methodological way to respond to the inevitable change and to enhance management accounting adaptability. Research limitations/implications This study contributes to the PMS literature by proposing that agile development methodologies can advance organizational features that increase management accounting adaptability. As a result, the study proposes a new approach for PMS development to supplement existing ones. Agile methodologies are especially suitable for extending the PMS in new, yet relatively immature areas of performance measurement. The new approach applies Scrum principles in PMS development. By drawing from the theories of performance measurement (system) development and enabling PMS, the paper furthers academic understanding about agile development of accounting information systems. Practical implications Companies can use the proposed approach in PMS development, particularly after the initial system implementation in redesigning the system. The approach may increase the PMS impact in organizations and prevent PMS implementation failures. Originality/value The paper identifies the potential of using agile methodologies to enhance PMS adaptability and provides preliminary evidence of the potential of such approach in supplementing processual PMS development frameworks.
4
Khan, Rashid Ali, Muhammad Faisal Abrar, Samad Baseer, Muhammad Faran Majeed, Muhammad Usman, Shams Ur Rahman, and You-Ze Cho. "Practices of Motivators in Adopting Agile Software Development at Large Scale Development Team from Management Perspective." Electronics 10, no. 19 (September 24, 2021): 2341. http://dx.doi.org/10.3390/electronics10192341.
Full textAbstract:
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.
5
Madadipouy, Kasra. "An Examination and Evaluation of Agile Methodologies for Systems Development." Australasian Journal of Computer Science 2, no. 1 (January 15, 2014): 1–17. http://dx.doi.org/10.3923/aujcs.2015.1.17.
Full text
6
Bushuyev, S., S. Murzabekova, and M. Khussainova. "COMPETENCE APPROACH IN AGILE TRANSFORMATION OF EDUCATION ESTABLISHMENT." Scientific Journal of Astana IT University, no. 5 (July 27, 2021): 52–62. http://dx.doi.org/10.37943/aitu.2021.97.75.005.
Full textAbstract:
The subject of the article is development of project, programs and project portfolios management systems with drivers of innovation in Agile transformation of Education Establishment is considered. Substantial changes in the environment require further research into the effectiveness of the application of existing agile methodologies, knowledge systems and competencies of project managers and their leadership. The foundations of environmental change lie in changing the decision-making paradigm in innovation project and programs management in Agile transformation of Education Establishment. The goal is to explore modern approaches to leadership formation when applying agile methodologies of its specificity from the point of view of decision-making processes in project management. The problems of leadership creation and development in the application of agile project management methodologies for the implementation of information and communication systems are considered. The results of studies were conducted on the basis of a competency-based approach modelled by the International Project Management Association. The content model of competency of the leader applying agile management is presented. Conclusion: The Agile leadership and leadership behaviour patterns are formed in a project management behavioural competency system based on agile technology methods and tools. These competencies included: Self-reflection and self-management, Personal integrity and reliability, Personal communication, Relationships and interaction, Leadership, Teamwork, Conflicts and crises, Inventiveness, Reconciliation, and Orientation to results. The patterns of project managers' behaviour as agile leaders in project product creation and agile project management are explored. The differences in the behaviour patterns of leaders and agile leaders were examined by behavioural competencies within the identified key competency indicators. Such patterns allowed the authors to identify bottlenecks in the application of agile project management methodologies in the context of the development of innovative products of innovation systems.
7
Ríos, Jimmy Molina, and Nieves Pedreira-Souto. "Approach of Agile Methodologies in the Development of Web-Based Software." Information 10, no. 10 (October 13, 2019): 314. http://dx.doi.org/10.3390/info10100314.
Full textAbstract:
The current inclusion of agile methodologies in web-oriented projects has been considered on a large-scale by software developers. However, the benefits and limitations go beyond the comforts that project managers delimit when choosing them. Selecting a methodology involves more than only the associated processes or some documentation. Based on the above, we could define as the main concerns the approach with which we identify the methodology, the needs of the company, the size, and qualities of the project, and especially the characteristics of agile development that they possess. However, there are several difficulties in selecting the most appropriate methodology due to the features in common; Will it be suitable for my project? What challenges will be presented in the process? Will my team understand each stage? Will I be able to deliver software that satisfies the client? Project managers create these questions, which seem manageable but have huge effects. This paper presents a systematic literature review based on the analysis of the approaches of six web development methodologies. The aim of the study is to analyze the approaches presented by relevant methodologies, identifying their common agile characteristics and managing to contrast both its benefits and limitations during a project. As a result, we could itemize five common features, which are presented within the processes; (1) flexibility, (2) constant communication of the workgroup, (3) use of UML, (4) the inclusion of the end-user and (5) some documentation.
8
Binsaleh, Muazzan, and Shahizan Hassan. "Systems Development Methodology for Mobile Commerce Applications." International Journal of Mobile Computing and Multimedia Communications 3, no. 4 (October 2011): 36–52. http://dx.doi.org/10.4018/jmcmc.2011100103.
Full textAbstract:
There are several methodologies, including traditional and agile methodologies, being utilized in current systems development. However, it could be argued that existing development methodologies may not be suitable for mobile commerce applications, as these applications are utilized in different contexts from fixed e-commerce applications. This study proposes a system development methodology for mobile commerce applications. In order to achieve this aim, four objectives are proposed: investigating existing systems development methodologies used to develop mobile commence applications, identifying strengths and weaknesses of existing development methodologies, construction of a suitable methodology for mobile commerce applications, and testing for its applicability and practicality. The research methodology used in the study is the design research, which includes the steps of awareness of problems, suggestion, development, evaluation and conclusion. However, this paper only focuses on the first two phases of the whole study, which are awareness of the problem and making suggestions, while the evaluation and conclusion will be conducted as future works.
9
Kendall, Kenneth E., Sue Kong, and Julie E. Kendall. "The Impact of Agile Methodologies on the Quality of Information Systems." International Journal of Strategic Decision Sciences 1, no. 1 (January 2010): 41–56. http://dx.doi.org/10.4018/jsds.2010103003.
Full textAbstract:
Systems developers and IT project managers who apply agile methods for developing information systems (IS) subscribe to a set of values and principles. This adherence to a set of values and principles, along with a passion or fervor surrounding the agile philosophy, made us question whether the adoption of agile methodologies has an effect on information systems built, and in particular, the quality of the IS developed. In this paper we construct a conceptual model, conduct a survey of software developers, and analyze our results, which support our hypotheses about the importance of the strategic selection of a development methodology. We conclude that practicing project managers should consider the decision to use certain methodologies as part of the strategic process.
10
Onokoy, L. S. "Flexible approaches to the development of software: evolution and prospects of development." Quality. Innovation. Education, no. 1 (2021): 57–67. http://dx.doi.org/10.31145/1999-513x-2021-1-56-66.
Full textAbstract:
The article is devoted to the study of fiexible approaches (Agile) to the design of information systems software. Much attention is paid to the comparative analysis of currently popular fiexible methodologies, including the DevOps (Development and Operation) methodology [4], [5], which covers the entire life cycle of creating a software product. In conclusion, based on the conducted research, the author reveals the global and Russian trends in the development of Agile and formulates their development prospects.
11
Sun, Zhi Wei. "The Role of Modelling in Agile Methodologies." Applied Mechanics and Materials 380-384 (August 2013): 1333–37. http://dx.doi.org/10.4028/www.scientific.net/amm.380-384.1333.
Full textAbstract:
Modelling as a technique continually keeps important place in information system development (ISD) methodologies and is adopted for implementing systems effectively. Contrasting to modelling, agile methodology is a new concept. It aims to overcome shortcomings of early ISD methodologies. It welcomes changes and adapt to them. Meanwhile it is people-oriented. Used in the new methodologies, besides traditional roles, modelling has more critical roles in ISD methodologies.The report illustrates main roles of modelling, including traditional and new ones. Meanwhile, it also addresses idea of ISD is social with the roles of modelling.
12
Rodriguez-Martinez, Laura, Hector Duran-Limon, Manuel Mora, and Francisco Rodriguez. "SOCA-DSEM: A well-structured SOCA development systems engineering methodology." Computer Science and Information Systems 16, no. 1 (2019): 19–44. http://dx.doi.org/10.2298/csis170703035r.
Full textAbstract:
Service-oriented Software Engineering (SOSE) is a software engineering paradigm focused on Service-oriented Computing Applications (SOCAs), for what SOCA development methodologies are required. Recent studies on SOCA development methodologies revealed theoretical and practical deficiencies. Thus, academicians and practitioners must adapt development methodologies from other paradigms or use the available partial SOCA development methodologies. Also, since the high acceptance of agile approaches, we claim new well-structured and balanced agility-rigor methodologies are required. Then, this paper proposes a new SOCA Development Systems Engineering Methodology, including its description, the explanation of its theoretical foundations and the illustration of its use with a prototype of a running example. Two pilot empirical evaluations on usability metrics are also reported. Findings support both theoretical adequacy and positive perceptions from the evaluators. While further empirical tests are required for gaining more conclusive evidences our preliminary results are encouraging.
13
Ahimbisibwe, Arthur, Urs Daellenbach, and Robert Y. Cavana. "Empirical comparison of traditional plan-based and agile methodologies." Journal of Enterprise Information Management 30, no. 3 (April 10, 2017): 400–453. http://dx.doi.org/10.1108/jeim-06-2015-0056.
Full textAbstract:
Purpose Aligning the project management methodology (PMM) to a particular project is considered to be essential for project success. Many outsourced software projects fail to deliver on time, budget or do not give value to the client due to inappropriate choice of a PMM. Despite the increasing range of available choices, project managers frequently fail to seriously consider their alternatives. They tend to narrowly tailor project categorization systems and categorization criterion is often not logically linked with project objectives. The purpose of this paper is to develop and test a contingency fit model comparing the differences between critical success factors (CSFs) for outsourced software development projects in the current context of traditional plan-based and agile methodologies. Design/methodology/approach A theoretical model and 54 hypotheses were developed from a literature review. An online Qualtrics survey was used to collect data to test the proposed model. The survey was administered to a large sample of senior software project managers and practitioners who were involved in international outsourced software development projects across the globe with 984 valid responses. Findings Results indicate that various CSFs differ significantly across agile and traditional plan-based methodologies, and in different ways for various project success measures. Research limitations/implications This study is cross-sectional in nature and data for all variables were obtained from the same sources, meaning that common method bias remains a potential threat. Further refinement of the instrument using different sources of data for variables and future replication using longitudinal approach is highly recommended. Practical implications Practical implications of these results suggest project managers should tailor PMMs according to various organizational, team, customer and project factors to reduce project failure rates. Originality/value Unlike previous studies this paper develops and empirically validates a contingency fit model comparing the differences between CSFs for outsourced software development projects in the context of PMMs.
14
Saeed, Kiran, Yaser Hafeez, Sadia Ali, Muhammad Usman Shahid, and Naila Iqbal. "Enabling the Usability Heuristics of Agile Base Systems to Improve Quality of Local Software Industry." Mehran University Research Journal of Engineering and Technology 38, no. 2 (April 1, 2019): 341–50. http://dx.doi.org/10.22581/muet1982.1902.09.
Full textAbstract:
Many agile software development practices are promoted to improve the quality of software products. In recent years agile software development overlooked the usability features that effected system productivity.Usability is a main feature of interaction. Interaction is a way of a farming relationship between people and designed objects. An interactive model provides the way to band application together to achieve target user’s need. Usability gained attention of researchers and engineers because of its own importance. Agile software methods and usability engineering played a major role for producing better and reliable products, because both of them are concepts of methods as well as practices. The purpose of this research was to highlight the need of usability practices. The proposed model demonstrates that usability heuristics were much compatible with agile methodologies and would help to improve its productivity by reducing time and cost. Action research was applied for the development of framework proposed. The framework was evaluated using case study and further results were compared with existing related work.
15
Gann, Alex. "IT and Business Can Succeed in BI by Embracing Agile Methodologies." International Journal of Business Intelligence Research 2, no. 3 (July 2011): 36–51. http://dx.doi.org/10.4018/jbir.2011070103.
Full textAbstract:
While the potential benefits from BI are vast, organizations have struggled to successfully deploy it. BI applies myriad advanced techniques, performed by the firm’s Information Technology (IT) group, to fulfill the reporting, analysis, and decision-support needs of the Lines of Business. Two of the greatest challenges in BI are accurately and continuously communicating requirements from the business to IT and quickly yet affordably delivering the requested functionality from IT to the business. Companies can overcome these challenges by embracing a prescribed set of Agile development methodologies for BI. This paper examines the history of selected systems development approaches, weighs the advantages and disadvantages of prevailing practices, and ultimately recommends a path forward to succeeding in BI through the application of Agile methodologies.
16
Suteeca, Kittitouch, and Sakgasit Ramingwong. "The Visualization of ISO/IEC29110 on SCRUM under EPF Composer." Information 12, no. 5 (April 28, 2021): 190. http://dx.doi.org/10.3390/info12050190.
Full textAbstract:
In the midst of an increasingly competitive software industry, very small entities (VSEs) have inevitably faced many challenges. High user expectations, frequent changes of user requirements, and the need for rapid deployment are classic examples of these challenges. Many software companies attempt to implement measures for preventing or solving the aforementioned problems. The use of agile methodologies and the implementation of software development standards are usually perceived to be promising solutions to improve the quality of the software development process. Nevertheless, there are several strong incompatibilities between standards and the Agile approach to software development. For example, the need identified in the standards to create many quality artifacts does not conform to agility philosophies. Since Agile focuses on the working software over the documentation, the use of the Agile with standards can be difficult to implement. Additionally, there has been none guidelines for VSE therefore, an external consultant is usually required. This research analyzes various cases of implementing ISO/IEC29110, a software development standard developed especially for VSEs in Scrum environments. The results of this study provide an Eclipse Process Framework (EPF) for effectively and conveniently implementing this standard in Scrum software development.
17
Balijepally, VenuGopal, Gerald DeHondt, Vijayan Sugumaran, and Sridhar Nerur. "Agility in Software Development and Project Value." Journal of Database Management 28, no. 4 (October 2017): 40–59. http://dx.doi.org/10.4018/jdm.2017100103.
Full textAbstract:
Agile Development Methods, considered as an alternative to the traditional plan-based methods, have received much attention since their inception. These practices have evolved and developed over time, culminating in 2001 with the Agile Manifesto. Since that time, preferred methodologies, implementations, and best practices have continued to evolve with a focus on doing what works best for the individual company or project. However, the concept of agility in software development has remained quite nebulous, lacking in clarity particularly about its underlying dimensions. In this research the authors conceive agility in terms of four distinct dimensions. Drawing from the theoretical perspective of holographic organization, they develop a model explaining how each of these underlying dimensions of agility contributes to project value in software teams. The authors test the model using survey data collected from industry practitioners and discuss findings.
18
Strenge, Benjamin, and Thomas Schack. "AWOSE - A Process Model for Incorporating Ethical Analyses in Agile Systems Engineering." Science and Engineering Ethics 26, no. 2 (October 7, 2019): 851–70. http://dx.doi.org/10.1007/s11948-019-00133-z.
Full textAbstract:
Abstract Ethical, legal and social implications are widely regarded as important considerations with respect to technological developments. Agile Worth-Oriented Systems Engineering (AWOSE) is an innovative approach to incorporating ethically relevant criteria during agile development processes through a flexibly applicable methodology. First, a predefined model for the ethical evaluation of socio-technical systems is used to assess ethical issues according to different dimensions. The second part of AWOSE ensures that ethical issues are not only identified, but also systematically considered during the design of systems based on information and communication technology. For this purpose, the findings from the first step are integrated with approaches from worth-centered development into a process model that, unlike previous approaches to ethical system development, is thoroughly compatible with agile methodologies like Scrum or Extreme Programming. Artifacts of worth-centered development called Worth Maps have been improved to guide the prioritization of development tasks as well as choices among design alternatives with respect to ethical implications. Furthermore, the improved Worth Maps facilitate the identification of suitable criteria for system evaluations in association to ethical concerns and desired positive outcomes of system usage. The potential of the AWOSE methodology has been demonstrated in the context of a technical system (smart glasses for cognitive assistance) that supports elderly and people with particular handicaps.
19
Fotache, Marin, Gabriela Mesnita, Florin Dumitriu, and Georgiana Olaru. "A Few Insights Into Romanian Information Systems Analysts and Designers Toolbox." Timisoara Journal of Economics and Business 10, no. 1 (June 1, 2017): 1–18. http://dx.doi.org/10.1515/tjeb-2017-0001.
Full textAbstract:
Abstract Information Systems (IS) analysts and designers have been key members in software development teams. From waterfall to Rational Unified Process, from UML to agile development, IS modelers have faced many trends and buzzwords. Even if the topic of models and modeling tools in software development is important, there are no many detailed studies to identify for what the developers, customers and managers decide to use the modeling and specific tools. Despite the popularity of the subject, studies showing what tools the IS modelers prefer are scarce, and quasi-non-existent, when talking about Romanian market. As Romania is an important IT outsourcing market, this paper investigated what methods and tools Romanian IS analysts and designers apply. In this context, the starting question of our research focuses on the preference of the developers to choose between agile or non-agile methods in IT projects. As a result, the research questions targeted the main drivers in choosing specific methods and tools for IT projects deployed in Romanian companies. Also, one of the main objectives of this paper was to approach the relationship between the methodologies (agile or non-agile), diagrams and other tools (we refer in our study to the CASE features) with other variables/metrics of the system/software development project. The observational study was conducted based on a survey filled by IS modelers in Romanian IT companies. The data collected were processed and analyzed using Exploratory Data Analysis. The platform for data visualization and analysis was R.
20
Ahimbisibwe, Arthur, Robert Y. Cavana, and Urs Daellenbach. "A contingency fit model of critical success factors for software development projects." Journal of Enterprise Information Management 28, no. 1 (February 9, 2015): 7–33. http://dx.doi.org/10.1108/jeim-08-2013-0060.
Full textAbstract:
Purpose – While the choices available for project management methodologies have increased significantly, questions remain on whether project managers fully consider their alternatives. When project categorization systems and criteria are not logically matched with project objectives, characteristics and environment, this may provide the key reason for why many software projects are reported to fail to deliver on time, budget or do not give value to the client. The purpose of this paper is to identify and categorize critical success factors (CSFs) and develop a contingency fit model contrasting perspectives of traditional plan-based and agile methodologies. Design/methodology/approach – By systematically reviewing the previous literature, a total of 37 CSFs for software development projects are identified from 148 articles, and then categorized into three major CSFs: organizational, team and customer factors. A contingency fit model augments this by highlighting the necessity to match project characteristics and project management methodology to these CSFs. Findings – Within the three major categories of CSFs, individual factors are ranked based on how frequently they have been cited in previous studies, overall as well as across the two main project management methodologies (traditional, agile). Differences in these rankings as well as mixed empirical support suggest that previous research may not have adequately theorized when particular CSFs will affect project success and lend support for the hypothesized contingency model between CSFs, project characteristics and project success criteria. Research limitations/implications – This research is conceptual and meta-analytic in its focus. A crucial task for future research should be to test the contingency fit model developed using empirical data. There is no broad consensus among researchers and practitioners in categorizing CSFs for software development projects. However, through an extensive search and analysis of the literature on CSFs for software development projects, the research provides greater clarity on the categories of CSFs and how their direct, indirect and moderated effects on project success can be modelled. Practical implications – This study proposes a contingency fit model and contributes towards developing a theory for assessing the role of CSFs for project success. While future empirical testing of this conceptual model is essential, it provides an initial step for guiding quantitative data collection, specifies detailed empirical analysis for comparative studies, and is likely to improve clarity in debate. Since previous studies have not rigorously assessed the impact of fit between project characteristics, project environment and project management methodology on project success, additional empirically robust studies will help to clarify contradictory findings that have limited theory development for CSFs of software development projects to date. Originality/value – Previous research for software development projects has frequently not fully incorporated contingency as moderation or contingency as fit (traditional vs agile). This research sets out to develop fully a contingency fit perspective on software development project success, through contrasting traditional plan-driven and agile methodologies. To do this, the paper systematically identifies and ranks 37 CSFs for software projects from 148 journal publications and holistically categorizes them as organizational, team, customer and project factors.
21
Chan, Frank K. Y., and James Y. L. Thong. "Acceptance of agile methodologies: A critical review and conceptual framework." Decision Support Systems 46, no. 4 (March 2009): 803–14. http://dx.doi.org/10.1016/j.dss.2008.11.009.
Full text
22
Cowling, James Austin, and Wendy K. Ivins. "Assessing the Potential Improvement an Open Systems Development Perspective Could Offer to the Software Evolution Paradigm." International Journal of Information Technologies and Systems Approach 9, no. 2 (July 2016): 68–87. http://dx.doi.org/10.4018/ijitsa.2016070105.
Full textAbstract:
Emerging stakeholder needs and a changing environment drive increasing demands for the constant adaption of software through maintenance and new capability development. A more evolutionary software engineering approach is sought to improve engineering responsiveness; Open System Development appears to offer a partial contribution but presents many challenges. This exploratory research proposes a new definition of the evolution of complex engineered systems, building on the essential features of ‘openness' described by Cowling et al (2014) and Lehman's (1980) ideas of evolutionary software. Using Checkland's (1999) Soft System Methodology enabled a structured literature review and analysis of the relative contributions of three divergent methodologies to the success of systems outcomes. These methodologies are: Plan-Driven, Agile, and Open Source Software Development. The analysis reveals several opportunities and highlights the critical issue of determining return on investment which needs to be overcome if an open approach is to contribute to evolutionary software engineering.
23
LÓPEZ-NORES, MARTÍN, JOSÉ J. PAZOS-ARIAS, JORGE GARCÍA-DUQUE, YOLANDA BLANCO-FERNÁNDEZ, REBECA P. DÍAZ-REDONDO, ANA FERNÁNDEZ-VILAS, ALBERTO GIL-SOLLA, and MANUEL RAMOS-CABRER. "BRINGING THE AGILE PHILOSOPHY TO FORMAL SPECIFICATION SETTINGS." International Journal of Software Engineering and Knowledge Engineering 16, no. 06 (December 2006): 951–86. http://dx.doi.org/10.1142/s0218194006003075.
Full textAbstract:
Software development can be seen as a process of knowledge acquisition, in which human beings progressively learn about the intended behavior of the desired systems. Thereby, development is subject to considerable amounts of uncertainty and variability, that make it impossible to proceed in a purely incremental fashion — at some points, the need always arises to reconsider part of the accumulated knowledge. With this problem in mind, agile development methodologies have been gaining popularity in recent years as a means to enhance productivity, and there have been attempts to supplement them with formal techniques for better reliability. However, the existing approaches to agile formal methods have practically limited themselves to adopting recommended practices of agile development, with no particular contribution from the employed formalisms. Compared to that, this paper advocates the use of formalisms intended for evolutionary development, with a two-fold objective: first, to exploit the knowledge acquired up to any given stage as a means to cope with frequent and numerous changes; and, second, to introduce support for the creative development tasks through an interactive procedure that helps taking steps forward.
24
MOSHIRPOUR, MOHAMMAD, ABDOLMAJID MOUSAVI, and BEHROUZ H. FAR. "DETECTING EMERGENT BEHAVIOR IN DISTRIBUTED SYSTEMS USING SCENARIO-BASED SPECIFICATIONS." International Journal of Software Engineering and Knowledge Engineering 22, no. 06 (September 2012): 729–46. http://dx.doi.org/10.1142/s0218194012400104.
Full textAbstract:
Emergent behavior is an important issue in distributed systems' design. Detecting and removing emergent behavior during the design phase will lead to huge savings in deployment costs of such systems. An effective approach for the design of distributed systems is to describe system requirements using scenarios. A scenario, commonly known as a message sequence chart or a sequence diagram, is a temporal sequence of messages sent between system components. However, scenario-based specifications are prone to subtle deficiencies with respect to analysis and validation known as incompleteness and partial description. In this research, a method for detecting emergent behavior of scenario-based specification is proposed. The method is demonstrated and verified using a mine-sweeping robot as an example. Furthermore it has been demonstrated in this paper that scenario-based specifications can be used in agile software development and that the proposed methodologies in this research can be utilized effectively in agile approaches.
25
Poma Lojano, Juan Pablo, Edilberto Antonio Llanes Cedeño, Diana Belen Peralta Zurita, and Jaime Vinici Molina Osejos. "Agile methodologies in the fundamental stages of industrial design." Universidad Ciencia y Tecnología 25, no. 110 (August 25, 2021): 87–96. http://dx.doi.org/10.47460/uct.v25i110.479.
Full textAbstract:
This document reflects an analysis on the evolution of industrial design and agile methodologies, in order to identify their main characteristics and find those points in common that allow to conclude on the applicability of these methodologies, initially created for software development. , in a process as important as that of industrial design. According to what has been explored, and considering the values that agile methodologies support since their creation in 2001, it is determined that they can guide the design process to a functional, sustainable, useful, aesthetic, economic and formal result, creating a fundamental basis for a specific review of the methodologies that best apply and how to implement them within the field of industrial design.
Keywords: Agile Methodologies, Industrial Design, Agile.
References
[1]J. S. Rial Huerta, «Aplicación de Metodologías Ágiles a Desarrollo de Proyectos,» Sevilla, España, 2019.
[2]A. Bramanti, «Estrategias de Innovación en los Procesos Productivos y su Relación con el Diseño Industrial,» 2020.
[3]L. De Caicedo, «Diseño Industrial,» Coyontura Económica , vol. 10, nº 4, pp. 141-153, 1980.
[4]A. Gay y L. Samar , El diseño industrial en la historia (reimpr.), Ediciones Tec, 2007.
[5]G. Vasquez Cabo y C. Amiama Ares, «Métodos ágiles en gestión de proyectos. Aplicación a la explotación y conservación de infraestructuras varias.,» Creative Commons, p. 13, 2018.
[6]F. Arroyo y D. Bravo, «El Proceso del Diseño Industrial como Herramienta de la Gestión de la Empresa,» INGENIO, vol. 3, nº 1, pp. 71-83, 2020.
[7]C. Riba Romeva, Diseño concurrente, Primera edición: abril 2002 ed., Barcelona, 2002: Ediciones UPC, 2002, p. 226.
[8]E. Uribe y L. Ayala, «Del manifiesto ágil sus valores y principios.,» Scientia et technica, vol. 13, nº 34, pp. 381-386, 2007.
[9]P. Rodríguez y D. Agustín, «Adopción de metodologías ágiles: un estudio comparativo entre España y Europa,» Revista Española de Innovación, Calidad e Ingeniería del Software, vol. 6, nº 4, pp. 6-28, 2010.
[10]D. Cárdenas y P. Quintana, «Aplicabilidad de metodologías ágiles en proyectos competitivos de la industria plástica,» Revista Investigación en Desarrollo y Gerencia Integral de Proyectos, vol. 3, nº 3, pp. 41-63, 2020.
[11]M. Gutiérrez, C. Pérez de Celis y G. Cossío , «Aplicación de las metodologías ágiles en el proceso de producción de piezas de arte de nuevos medios: Bio-lenciacomo caso de estudio,» Journal of Information Systems and Technology Management, vol. 8, nº 2, pp. 407-424, 2011.
[12]D. Moher, A. Liberati, J. Tetzlaff y D. Altman, «Preferred Reporting Items for Systematic Reviews and Meta-Analyses: the PRISMA statement,» PLoS Medicine , vol. 8, nº 7716, pp. 336-341, 2009.
26
Erturk, Emre. "Implementing Enterprise Content Management Services with an Agile Approach." Business and Management Research 8, no. 3 (August 18, 2019): 16. http://dx.doi.org/10.5430/bmr.v8n3p16.
Full textAbstract:
Every organisation needs access to fast online data in order to meet increasing customer demands. As a result, the information architecture of a company, how it is designed, and how information is managed are very important. Because the amount of content is growing at a precipitous rate, in order to manage it with the greatest efficacy, an online content management system is recommended. The challenge for organisations is to implement and manage a dynamic content management system that is responsive to changing requirements, while providing a structure that contributes to organisational efficiencies. How a content management system is designed and implemented (e.g. with Office 365, SharePoint, G Suite, or SAP OpenText) determines its success. This paper discusses using Agile approaches for business content management systems, to ensure that they will be used to their full potential.This conceptual research paper looks into the current context of Enterprise Content Management (ECM) and the desirable qualities of an Agile approach. First, the literature review explores the definitions, elements, benefits, and recent trends around ECM. Then, the paper discusses Agile project management (APM) with some major characteristics and typical features. Thirdly, the paper describes how an Agile ECM system should be (e.g., takes advantage of the growing Internet, cloud services, and mobile computing). An Agile ECM can be developed with an APM or a hybrid approach (i.e. using an Agile software development process to create an Agile end product).This paper covers possible methodologies based on traditional and Agile software development approaches. These encourage a flexible development approach to ECM implementation, and promoting end user involvement and their needs. An ECM system should be dynamic enough to meet the demands of future organisational growth and the business environment. It should allow integration with other new software, including those in the organisation and those in the Cloud. Two methodologies (Scrum and MIKE2.0) are explained, along with their strengths and weaknesses. The recommendation is to synthesize them so that future implementations may take advantage of techniques from both. MIKE2.0 can ensure good information governance, while Scrum can provide an innovative team-based approach and user empowerment, which are highly useful for implementing Content Services rapidly.
27
Ficco, Massimo, Roberto Pietrantuono, and Stefano Russo. "Bug Localization in Test-Driven Development." Advances in Software Engineering 2011 (June 15, 2011): 1–18. http://dx.doi.org/10.1155/2011/492757.
Full textAbstract:
Software development teams that use agile methodologies are increasingly adopting the test-driven development practice (TDD). TDD allows to produce software by iterative and incremental work cycle, and with a strict control over the process, favouring an early detection of bugs. However, when applied to large and complex systems, TDD benefits are not so obvious; manually locating and fixing bugs introduced during the iterative development steps is a nontrivial task. In such systems, the propagation chains following the bugs activation can be unacceptably long and intricate, and the size of the code to be analyzed is often too large. In this paper, a bug localization technique specifically tailored to TDD is presented. The technique is embedded in the TDD cycle, and it aims to improve developers' ability to locate bugs as soon as possible. It is implemented in a tool and experimentally evaluated on newly developed Java programs.
28
Khuat, Thanh Tung, and My Hanh Le. "A Novel Hybrid ABC-PSO Algorithm for Effort Estimation of Software Projects Using Agile Methodologies." Journal of Intelligent Systems 27, no. 3 (July 26, 2018): 489–506. http://dx.doi.org/10.1515/jisys-2016-0294.
Full textAbstract:
Abstract In modern software development processes, software effort estimation plays a crucial role. The success or failure of projects depends greatly on the accuracy of effort estimation and schedule results. Many studies focused on proposing novel models to enhance the accuracy of predicted results; however, the question of accurate estimation of effort has been a challenging issue with regards to researchers and practitioners, especially when it comes to projects using agile methodologies. This study aims at introducing a novel formula based on team velocity and story point factors. The parameters of this formula are then optimized by employing swarm optimization algorithms. We also propose an improved algorithm combining the advantages of the artificial bee colony and particle swarm optimization algorithms. The experimental results indicated that our approaches outperformed methods in other studies in terms of the accuracy of predicted results.
29
Ferreira Martins, Hugo, Antônio Carvalho de Oliveira Junior, Edna Dias Canedo, Ricardo Ajax Dias Kosloski, Roberto Ávila Paldês, and Edgard Costa Oliveira. "Design Thinking: Challenges for Software Requirements Elicitation." Information 10, no. 12 (November 28, 2019): 371. http://dx.doi.org/10.3390/info10120371.
Full textAbstract:
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.
30
Arora, Mohit, Dr Sahil Verma, and Dr Kavita. "An efficient effort and cost estimation framework for Scrum Based Projects." International Journal of Engineering & Technology 7, no. 4.12 (October 4, 2018): 52. http://dx.doi.org/10.14419/ijet.v7i4.12.20992.
Full textAbstract:
Software Process Models from its inception instill standardization and creates a generic culture of developing software for various IT industries. A great paradigm shift has been observed in terms of embracing Agile Development methodology as a viable development methodology in cross key business units. There is a buffet of agile methodologies comes under the umbrella of ASD, out of which Scrum got the highest popularity and acceptability index. Agile based software development is the need of immediate environment. There is an increasing demand for significant changes to software systems to meet ever-changing user requirements and specifications. As Agile is volatile, so effort estimation is challenging and still striving for perfection to decide size, effort, cost, duration and schedule of projects with minimum error. This cause sensitizes potential researchers all across the globe to start working on addressing the issue of inaccurate predication of efforts. The gap between estimated and actual effort is because of limited or no inclusion of various estimation factors like people and project related factors, inappropriate use of size metric and cost drivers, ignorance of testing effort, team member’s inability to understand user story size and complexity etc. This paper attempts to bridge the gap of estimated and actual effort by the use of soft computing techniques thus taking the research to advance frontier area in terms of estimation.
31
Ильина, Ольга, and Olga Ilina. "Cyber-Physical Systems: Project Management Approach: the introduction of BIM." Scientific Research and Development. Russian Journal of Project Management 6, no. 4 (December 26, 2017): 44–49. http://dx.doi.org/10.12737/article_5a3274bfe88435.61894803.
Full textAbstract:
In the era of the digital economy, the task of developing approaches to project management, the subject area of which is at the intersection of IT and real production processes, becomes especially urgent. This clearly demonstrates the challenges of the construction industry, where today the tasks of complex development of territories, the construction of unique facilities and structures are being solved, all based on modern information technologies. In fact, we are talking about a new era in construction — the era of cyber-physical systems. All this predetermines the need to change the methodology of project management in this area. As a methodological basis of project management for the creation of cyber-physical systems in the design, construction and operation of construction sites, an integrated methodological solution is proposed, formed on the basis of the synthesis of methodologies existing in project management. A scheme for the formation of the project management system for the creation of cyber-physical systems is developed on the basis of the project management methodology, which includes elements of project management methodologies such as PMBOK, P2M, PRINCE2, Agile (SCRUM).
32
Fernandi Wijaya, Santo, and Angelina Ervina Jeanette Egeten. "Breaking through unravel problems in ERP implementation using agile." Journal of Advanced Computer Science & Technology 8, no. 2 (August 25, 2019): 16. http://dx.doi.org/10.14419/jacst.v8i2.16236.
Full textAbstract:
Demand for the industry to enhance competitive advantage. For that, the industry is required to make a breaking through in order to enhance the organizational performance. This is a reason for addressing the inefficiencies in managing people, processes, organizations, and technology. One of the efforts in improving organization performance is the development in the field of Information Systems as an effort to improve the agility of the organization. ERP system is one solution that can be employed in order to improve organization performance. However, in reality, industrial companies face problems in ERP implementation. This is a challenge to solve the problems of implementing an ERP system for industry. In this opportunity, researchers intend to conduct a re-search to identify the problems of factors in the ERP implementation, namely by proposing agile methods as one of the new methodologies in the effort to solve the problems in the ERP implementation for an industry. The results of this study will result in an agile model of implementing ERP for improving the capacity of ERP systems. This study idea is to analyze the agile method as a solution alternative to make changes for the ERP implementation success. This study is using Structural Equation Modeling as a quantitative data analysis approach of an industry as a case study.
33
Wijaya, Santo Fernandi. "Agile Methodology: Solution to Unravel Complexities in the Implementation of ERP System." International Journal of Information Technology and Business 1, no. 1 (October 31, 2018): 1–9. http://dx.doi.org/10.24246/ijiteb.112018.1-9.
Full textAbstract:
Improving productivity is a demand for the industry in order to enhance competitive advantage, especially in the manufacturing industry. For that, the industry is required to make a breakthrough in order to improve organizational performance, such as addressing the inefficiencies in managing business processes, so as to improve the way work becomes more effective and efficient. One of the efforts in improving the performance is the development in the field of Information Communication Technology (ICT), the development of technology as an effort to improve the agility of the organization. ERP system is one solution that can be employed in order to improve company performance. However, in reality, industrial companies face the complexity of implementing ERP systems. This is a challenge, that is how effective for a company in order to solve the complexity of implementing an ERP system for an industry?. In this opportunity, researchers intend to conduct a research to identify the complexity of factors in the ERP implementation, namely by proposing agile methods as one of the new methodologies in the effort to solve the complexity in the ERP implementation for an industry. The results of this study will result in an agile modeling of ERP systems, which is expected to solve the complexity of implementation and improve the capacity of ERP systems for an Industry.
34
Tarhini, Abbas, Manal Yunis, and Abdul-Nasser El-Kassar. "Innovative sustainable methodology for managing in-house software development in SMEs." Benchmarking: An International Journal 25, no. 3 (April 3, 2018): 1085–103. http://dx.doi.org/10.1108/bij-05-2017-0103.
Full textAbstract:
Purpose The purpose of this paper is to present an innovative agile methodology that proposes fundamental changes in managing the development of in-house information systems in small- and medium-sized enterprises (SMEs) and benchmarks it with one of two database technologies enabling these systems to be both efficient and competitive. Design/methodology/approach The objectives are achieved by presenting an elaborated design of the agile methodology that manages the system development process by addressing three basic components: roles played by system players, process needed to fulfill the system development, and artifacts to document the project. A case study is conducted as a proof of the effectiveness of the proposed methodology and measures whether the selection of the database technology affects the effectiveness of the system development process. Findings Results show that, compared with traditional methodologies, the proposed methodology reduced the cost of system development and testing by 30 percent and enhanced the IT – business alliance. Further, this work found that the selection of a suitable database technology is strongly related to the complexity and interrelationships between the data used. Originality/value Such research did not receive the needed attention (Hunter, 2004) even in the past decade. Successful adoption of IT by companies could be in the form of customized IS which could be expensive for SMEs to adopt due to a lack in technical expertise and financial resources. The proposed methodology has the potential to promote sustainable development through helping SMEs in reducing the time and cost of IT project development.
35
Bushuiev, Serhii D., Denys A. Bushuiev, Victoriia B. Bushuieva, and Borys Yu Kozyr. "ЛІДЕРСТВО В ЗАСТОСУВАННІ ГНУЧКИХ МЕТОДОЛОГІЙ СТВОРЕННЯ ІНФОРМАЦІЙНИХ ТЕХНОЛОГІЙ." Information Technologies and Learning Tools 70, no. 2 (April 27, 2019): 1. http://dx.doi.org/10.33407/itlt.v70i2.2761.
Full textAbstract:
The development of project, project and portfolio management systems supports the global acceleration of innovation. Significant changes in the environment require additional research on the effectiveness of the use of existing flexible methodologies, knowledge systems, the competency of project managers and their leadership. The foundation of environmental change lies in changing the decision-making paradigm to flexible project management and innovation development programs. The article examines modern approaches to leadership formation in the application of flexible methodologies, their specificity in terms of decision-making processes in project management. The problems of formation and maintenance of leadership in application of flexible methodologies of project management of creation and introduction of information and communication systems are considered. The research was conducted on the basis of the application of a competency approach under the model of the International Association for Project Management. The patterns of behavior of flexible leaders and leaders are formed in the system of behavioral competencies in project management based on Agile technology methods and tools. These competencies were: Self-reflation and self-government, Personal integrity and reliability, Personal communication, Relationships and interaction, Leadership, Teamwork, Conflicts and crises, Inventiveness, Harmonization, and Orientation to the result. The content model of competency of the leader, which applies flexible control, is given. The patterns of behavior of project managers as flexible leaders in project product creation and flexible project management were studied. Differences in patterns of behavior of managers and flexible leaders on elements of behavioral competencies within certain key competency indicators are studied. Such patterns allowed the authors to identify bottlenecks in applying flexible project management methodologies in the context of the dynamics of the development of innovative products and information and communication systems.
36
Bushuyev, Sergiy D., Denis A. Bushuev, Natalia S. Bushuyeva, and Boris Yu Kozyr. "ІНФОРМАЦІЙНІ ТЕХНОЛОГІЇ РОЗВИТКУ КОМПЕТЕНЦІЙ МЕНЕДЖЕРІВ З УПРАВЛІННЯ ПРОЕКТАМИ НА ОСНОВІ ГЛОБАЛЬНИХ ТРЕНДІВ." Information Technologies and Learning Tools 68, no. 6 (December 27, 2018): 218. http://dx.doi.org/10.33407/itlt.v68i6.2684.
Full textAbstract:
Global processes and their trends taking place in various fields of knowledge with a significant acceleration affect the development of information and communication technologies and project management competences, programs and project portfolios. The purpose of the article is to develop and investigate the mechanisms for assessing the project managers’ competences for their development based on global trends and Agile's flexible methodology in project management in creating modern information and communication technologies in the field of project management. Global trends that create challenges in developing project management competences and programs are related to global acceleration, digitalization of society, development of block chains, cloud and fog technologies, active introduction of intelligent systems, transition from "rational economy" to "behavioural economy". The convergence of these trends creates a new platform for the effectiveness of applying existing methodologies, knowledge systems and methods for evaluating the competence of project managers. On the basis of convergence, integration and harmonization of methodologies for project and program management, a step-by-step approach to research has been identified. The formation of an updated system of competences based on global trends lies in the replacement of paradigms from traditional life cycle project models to flexible models such as Agile. Decision-making in the conditions of uncertainty on the basis of datamining become more justified. The article deals with modern information models of projects and programs, changing system of project managers’ competences, bringing together decision-making models and methods. At the same time, the change of competences, as actions or functions that project managers must perform, affects the model of competency and the assessment system, including key indicators of competency. The informative model of diagnostics application of competency models and methods of project management in digital and "behavioural economics" is based on the use of flexible methodologies. Some key indicators of competency are defined that are applied in the assessment of the project manager competency based on his competences in the project team. Patterns of project managers' behaviour when designing product and project management have been studied. The patterns allowed authors to identify bottlenecks in applying Agile project management methodologies in the convergence of trend information models and technologies. An example of information technology for managing the competency assessment of project managers by the IPMA ICB4 model is given.
37
Thomas, Ashish. "Developing an integrated quality network for lean operations systems." Business Process Management Journal 24, no. 6 (November 5, 2018): 1367–80. http://dx.doi.org/10.1108/bpmj-02-2018-0041.
Full textAbstract:
Purpose Most successful companies have adopted some type of improvement methodology to achieve optimum performance, high quality, lower costs and productivity. Some of the structured methodologies employed indiscriminately are total quality management, quality control, agile, lean and Six Sigma which yield varied results. The purpose of this paper is to explore how to harness the power of an integrated system of quality tools and techniques to create operational excellence. An integrated framework involves matching quality tools and techniques to the multi-phases (input, transformation and output) of lean manufacturing or service ecosystem. Design/methodology/approach Current research of lean quality systems provides a conceptual understanding of core tools employed by manufacturing and service organizations. Interviewing domain experts from a series of manufacturing and service organizations highlighted a common challenge. The challenge was lean tools and methodologies were selected and employed arbitrarily for the different operational phases, which resulted in selective synergies of tools between operational phases. This limitation resulted in rework and duplication of quality efforts through the diverse phases of the transformation system. This study is based on the hypothesis that all phases of an operational system must be linked by common tools and methodologies which enables harnessing quality benefits and synergies throughout the entire operational system. The study methodology trailed through cooperative inquiry using a case study approach to design an integrated framework of tools that facilitates a common platform for manufacturing or service ecosystems. Findings This study suggests that quality systems in a complex competitive environment must consider an integrated iterative approach. An iterative development of lean quality tools for multiple phases produces an integrated quality system. Such systems employ blending and extending of lean quality tools to multiple phases of the transformation system to synthesize agile and versatile quality system. Research limitations/implications A limitation of this study is that the research of integrated framework is based on repertory grid technique only; it should be supplemented by other methods. Second, the proposed framework does not consider the complexity added by the internal and external stakeholders as they interface with the integrated system at different points with reference to phases of the system. Practical implications One of the advantages of this method is its generality, instead of delivering a monolithic system at the culmination of long transformation process we rely on smaller quality sprints which are implemented sequentially at each stage or phase of the transformation system. The phenomena of incremental clustering of time-series of quality sprints for different phases results in true integration from end to end for a transformation system. Social implications This study helps investigate the personal constructs that users and managers employ to interpret and select quality tools or methodologies for the different phases of lean transformational system. Originality/value This study aims to understand the impact of blending quality and business process improvement tools and methodologies to enhance outcomes. The basis of this study is “the power of multiplicity” through which a diverse collection of improvement paths is pooled into an integrated framework of quality tools for lean and efficient operations.
38
Kovács, Attila, and Kristóf Szabados. "Internal quality evolution of a large test system – an industrial study." Acta Universitatis Sapientiae, Informatica 8, no. 2 (December 1, 2016): 216–40. http://dx.doi.org/10.1515/ausi-2016-0010.
Full textAbstract:
AbstractThis paper presents our empirical observations related to the evolution of a large automated test system. The system observed is used in the industry as a test tool for complex telecommunication systems, itself consisting of more than one million lines of source code. This study evaluates how different changes during the development have changed the number of observed Code Smells in the test system. We have monitored the development of the test scripts and measured the code quality characteristics over a five years period.The observations show that the introduction of continuous integration, the existence of tool support for quality improvements in itself, changing the development methodologies (from waterfall to agile), changing technical and line management structure and personnel caused no measurable change in the trends of the observed Code Smells. Internal quality improvements were achieved mainly by individuals intrinsic motivation. Our measurements show similarities with earlier results on software systems evolutions presented by Lehman.
39
Mohammed, Yakubu Bala, and Damla Karagozlu. "A Review of Human-Computer Interaction Design Approaches towards Information Systems Development." BRAIN. BROAD RESEARCH IN ARTIFICIAL INTELLIGENCE AND NEUROSCIENCE 12, no. 1 (March 29, 2021): 229–50. http://dx.doi.org/10.18662/brain/12.1/180.
Full textAbstract:
Nowadays modern information systems (emerging technologies) are increasingly becoming an integral part of our daily lives and has begun to pose a serious challenge for human-computer interaction (HCI) professionals, as emerging technologies in the area of mobile and cloud computing, and internet of things (IoT), are calling for more devotion from HCI experts in terms of systems interface design. As the number of mobile platforms users, nowadays comprises of children’s, elderly people, and people with disabilities or disorders, all demanding for an effective user interface that can meet their diverse needs, even on the move, at anytime and anywhere. This paper, review current articles (43) related to HCI interface design approaches to modern information systems design with the aim of identifying and determining the effectiveness of these methods. The study found that the current HCI design approaches were based on desktop paradigm which falls short of providing location-based services to mobile platforms users. The study also discovered that almost all the current interface design standard used by HCI experts for the design of user’s interface were not effective & supportive of emerging technologies due to the flexibility nature of these technologies. Based on the review findings, the study suggested the combination of Human-centred design with agile methodologies for interface design, and call on future works to use qualitative or quantitative approach to further investigate HCI methods of interface design with much emphasis on cloud-based technologies and other organizational information systems.
40
Bortnik, Olena. "Agile and Lean approaches: possibilities of application in local self-government bodies of Ukraine." Public administration aspects 8, no. 6 (December 30, 2020): 70–80. http://dx.doi.org/10.15421/1020107.
Full textAbstract:
The article considers the concepts and history of Agile and Lean, the possibility of application in local self-government in Ukraine, analysis of the experience of local government in other countries. The aim of the article is to find ways to learn the best experience to improve the work of local self-government in Ukraine.Foreign publications related to the possibility of implementing the Agile methodology in the field of public administration and local self-government are analyzed. Examples of interaction and mutual influence of Agile and Lean are given. Demonstrates how references in international ISO standards to the above-mentioned methodologies, values and ways of thinking are used. ISO standards for management systems are universal and can be applied by both private and public sector organizations. One of the main ideas behind the standards is continuous improvement based on the PDCA cycle, and organizations that have implemented management systems such as ISO 9001 can use international best practices, tools and techniques to improve efficiency and effectiveness, satisfaction of customers and other interested parties and reduce unwanted losses. Such methods are those which are considered in this article. Historically, most management practices have emerged in the private sector, driven by a competitive environment. And then adapts to public administration and local government. In Ukraine, the process of decentralization of local self-government is gaining momentum. Sustainable development of local self-government is the basis for ensuring the comfort and quality of life of the local communities. In a rapidly changing environment, there is a need to find new management approaches. It is proposed to conduct short-term pilot projects to test the Agile method in local governments. It is advisable to include consideration of the methods specified in the article in training and retraining of employees. Continuous improvement requires, first of all, a change in organizational culture and awareness and involvement of staff for the most effective implementation of world best practices.
41
Alsaadi, Mahmood, Malik Qasaimeh, Sara Tedmori, and Khaled Almakadmeh. "HIPAA Security and Privacy Rules Auditing in Extreme Programming Environments." International Journal of Information Systems in the Service Sector 9, no. 1 (January 2017): 1–21. http://dx.doi.org/10.4018/ijisss.2017010101.
Full textAbstract:
Healthcare business is responsible of keeping patient data safe and secure by following the rules of the federal Health Insurance Portability and Accountability Act of 1996, (HIPAA). Agile software organizations that deal with healthcare software system face a number of challenges to demonstrate that their process activities conform to the rules of HIPAA. Such organizations must establish a software process life cycle and develop procedures, tools, and methodologies that can manage the HIPAA requirements during the different stages of system development, and also must provide evidences of HIPAA conformity. This paper proposes an auditing model for HIPAA security and privacy rules in XP environments. The design of the proposed model is based on an evaluation theory which takes as its input the work of Lopez ATAM, and the standards of common criteria (CC) concepts. The proposed auditing model has been assessed based on four case studies. The auditing result shows that the proposed model is capable of capturing the auditing evidences in most of the selected case studies.
42
Isern, Germinal. "Intercultural Communication and Management Factors and Their Impact to the Process of Global Software Development for Virtual and Non-Virtual Teams." Journal of Intercultural Management 6, no. 1 (March 1, 2014): 5–16. http://dx.doi.org/10.2478/joim-2014-0001.
Full textAbstract:
Abstract This position paper presents the factors involved in the successful software development and what is the impact of some methodologies like Agile in this process. Global software development projects may be a total success or an anticipated disaster for simple reasons that usually have nothing to do with the technology involved, with the time differences, or the product being built, but because of subtle intercultural factors. How do the language, the race, the gender, the religion, and the location affects the software development process from analysis and design to implementation, testing and maintenance? Do all these factors impact in the same way if we are working with a local team, and offshore development team or even a global virtual team? Is any specific software development methodology better suited for your particular case? How could you decide what’s the better approach? What will be the results and what our goals? The issues at stake are not superficial matters of the ways how people dress, or how clear do they speak in our local language, or what they like to eat, or their small daily behaviors, but are based in the fundamental differences in the systems of values that govern our lives. So institutions, corporations and global companies have to raise the level of awareness of their employees worldwide on the cultural differences, through various programs for intercultural or diversity training. But this poor model of cultural awareness is not enough to overcome some of the obstacles that intercultural differences bring to the table. So this paper will list and describe this important intercultural factors that directly impact in the software development process and how certain software development methodologies could be used in order to have a more systematic look or set of guidelines that would allow the team managers to evaluate and to decide how theuse of each one of these software development methodologies for local teams, non local teams and virtual teams will affect positively or negatively the outcomes of software development practices.
43
Kadykova, I., and V. Khvostichenko. "CONCEPTUAL MODEL OF SYSTEM DEVELOPMENT STRATEGY MANAGEMENT FROM THE POSI-TION OF PROJECT APPROACH." Municipal economy of cities 3, no. 156 (July 1, 2020): 69–79. http://dx.doi.org/10.33042/2522-1809-2020-3-156-69-79.
Full textAbstract:
The purpose of the article is to build a conceptual model of strategic project management through the prism of a multidisciplinary approach. Project management methodologies for the place of strategic management of complex nonlinear system development are analyzed. Standardized, adaptive and combined project and program management methodologies (PMBoK, P2M, PRINCE2, MSP, Agile) are considered. The authors pay special atten-tion to the study of the influence of the external environment on a complex nonlinear system in the context of a synergetic approach. The main part describes the process of expanding the scope of project management and inte-gration of project management with modern methods and tools of other management disciplines. Elements of the theory of synergetics and the classical theory of the design approach to the management of the development of a complex nonlinear system are synthesized. The necessity of clear definition by the team of the project of the struc-tural attractor, ie the direction of strategic development of the system is substantiated. The tool for determining compliance with the contextual requirements of SMART-goals of alternative scenarios for strategic development projects is considered. The tool of the Ishikawa diagram is used to determine the most influential factors on possi-ble deviations of the project from the strategic development of a complex nonlinear system. The conducted theoret-ical research allowed the authors to build a conceptual model of system development strategy management from the standpoint of the project approach. The conceptual model of strategic project management is constructed, the principles of its work and its use in discrete systems for actualization of administrative decisions in the conditions of risk and uncertainty are resulted. The expediency of using this conceptual model in managing the integration of strategic development projects is substantiated. Keywords: strategy, project management, program, project, synergetic, bifurcation.
44
Lysenko, D., and Y. Fediai. "THE AGILE EARNED VALUE MANAGEMENT METHOD AS A COST MANAGEMENT TOOL IN SCRUM PROJECTS." Municipal economy of cities 3, no. 163 (June 29, 2021): 159–64. http://dx.doi.org/10.33042/2522-1809-2021-3-163-159-164.
Full textAbstract:
According to the statistics, the majority of IT projects run 50–150 percent over budget, which indicates the importance of managing its cost. In agile methodologies which are widely used in software development, little attention is given to cost management. Lack of specialized cost management tools in agile practices raises the question of the feasibility of adapting traditional project management methods and techniques. The purpose of the research is to improve the quality of IT projects cost control processes by developing a project cost management model using the Agile Earned Value Management method. The paper discusses the EVM techniques which have been adopted to provide the benefits of traditional EVM in Agile projects. There are some misconceptions that EVM techniques are too difficult to perform effectively on projects implemented using agile approaches (i.e. Scrum framework). The challenges are primarily associated with the fact that the EVM method requires creating a complete description of project tasks and a detailed schedule of their execution at the initial stage allowing accurate estimates of the actual data and monitoring the project progress from start to completion. On the other hand, Scrum emphasizes the need for incremental, multi-level planning and discourages planning software projects down to the lowest level of decomposition in the early stages. The reason for this is the high degree of ambiguity inherent in complex software systems, and the high probability of changes that make fully defining the requirements up front nearly impossible. However, upon closer examination of Sprint attributes, such as fixed duration, fixed backlog, cost measurement of sprint tasks, the ultimate goal of delivering a minimum viable product – leads us to the conclusion that Sprint can be considered as a subproject to which the mechanism of the EVM method can be applied using the same metrics. The paper further summarizes the main provisions and guidelines of the AgileEVM method, based on which its process model is developed. The inputs of the model are initial release baseline parameters and data captured at the completion of each Sprint: Planned Sprints (PS); Planned Release Points (PRP); Budget at Complete (BAC); Points Completed (PC), Points Added (PA), and Sprint Cost (SC). The controls are the AgileEVM method guidelines. The mechanisms are project manager and necessary software (MS Excel, MS Project). At the output of the model we obtain forecast indicators: Estimate to Complete (ETC), Estimate at Complete (EAC), Number of Total Sprints (N), and Release Date (RD). The final conclusion of the conducted research is that the application of the Earned Value Management method to projects implemented with Scrum enables the project manager and the project team with a valuable tool to monitor the progress of their work and to take appropriate measures.
45
Kammergruber, Roland, and Jürgen Durner. "Laboratory information system and necessary improvements in function and programming." LaboratoriumsMedizin 42, no. 6 (December 19, 2018): 277–87. http://dx.doi.org/10.1515/labmed-2018-0038.
Full textAbstract:
AbstractSince the 1970s, computer supported data processing has been implemented in the laboratory and laboratory information systems (LIS) are being developed. In the following years, the programs were expanded and new laboratory requirements were inserted to the LIS. In the last few years, the requirements have grown more and more. The current tasks of the LIS are not only the management of laboratory requirements but also management of processes, data security and data transfer and they have become very important. Therefore, the current monolithic architecture of LIS has reached its limits. New methodologies like service oriented architecture, e.g. microservices, should be implemented. Thereby different specialized manufacturers provide software for one or a few tasks. These tasks can be more easily actualized like in the new field of agile software development. This new concept has been designed to provide updates and customer requirements according to its new organization structure in program development in a short time. For efficient data transfer, new interfaces and a standardization of master data like logical observation identifier names and codes (LOINC®) are advisable. With the growing data transfer, data security plays an increasingly important role. New concepts like blockchain programming (e.g. Medrec) are currently tested in (laboratory) medicine. To get an overview of the requirements of the own LIS, an Ishikawa diagram should be created. The main points of an Ishikawa diagram are shown and discussed. Based on the today-collected data, expert systems will be developed. For this kind of data mining, a structured data exchange is necessary.
46
Alsaqqa, Samar, Samer Sawalha, and Heba Abdel-Nabi. "Agile Software Development: Methodologies and Trends." International Journal of Interactive Mobile Technologies (iJIM) 14, no. 11 (July 10, 2020): 246. http://dx.doi.org/10.3991/ijim.v14i11.13269.
Full textAbstract:
<p>Software engineering is a discipline that undergone many improvements that aims to keep up with the new advancements in technologies and the modern business requirements through developing effective approaches to reach the final software product, agile software development is one of these successful approaches. Agile software development is a lightweight approach that was proposed to overcome the convolutional development methods’ limitations and to reduce the overhead and the cost while providing flexibility to adopt the changes in requirements at any stage, this is done by managing the tasks and their coordination through a certain set of values and principles.</p><p>In this work, a comprehensive review that outlines the main agile values and principles, and states the key differences that distinguish agile methods over the traditional ones are presented. Then a discussion of the most popular agile methodologies; their life cycles, their roles, and their advantages and disadvantages are outlined. The recent state of art trends that adopts agile development especially in cloud computing, big data, and coordination are also explored. And finally, this work highlights how to choose the best suitable agile methodology that must be selected according to the task at hand, how sensitive the product is and the organization structure.</p>
47
Kumar, Rakesh, Priti Maheshwary, and Timothy Malche. "Inside Agile Family Software Development Methodologies." International Journal of Computer Sciences and Engineering 7, no. 6 (June 30, 2019): 650–60. http://dx.doi.org/10.26438/ijcse/v7i6.650660.
Full text
48
Nerur, Sridhar, and VenuGopal Balijepally. "Theoretical reflections on agile development methodologies." Communications of the ACM 50, no. 3 (March 2007): 79–83. http://dx.doi.org/10.1145/1226736.1226739.
Full text
49
(Simi) Bajaj,, Kamini, and Tressa Rai. "Survey on Agile Implementation of the BI Systems." International Journal of Engineering & Technology 7, no. 4.38 (December 3, 2018): 898. http://dx.doi.org/10.14419/ijet.v7i4.38.27604.
Full textAbstract:
Business intelligence (BI) is a technique that helps organisations to effectively analyse, manipulate and store data. It takes historical and present data from various sources and presents the data to the users anytime, anywhere to help them make smart and effective decisions. However, the cross functional nature of BI systems that covers the length and breadth of the organization, pose an issue with effective implementation. Various Traditional methodologies have been used to implement BI systems however have encountered countless failures leading the practitioners to look up to Agile methodologies to overcome the shortcomings. Since different companies have different requirements, out of the box Agile solutions do not address the requirements effectively. As a result, use of Agile methodologies for BI implementation also face lot of issues. To justify this claim we conducted a survey of agile practitioners doing BI implementation. This paper aims at presenting the findings of the study focused on identifying the gaps in implementing BI systems using Agile methodologies. It also presents the results for the survey conducted to capture the methodologies used by the organisations and practitioners and issues in BI implementation. In future, this captured information would be utilised into formulating a framework that can work along with Agile methodology to help address the issues faced with Agile methodologies for BI Implementations.
50
Dingsøyr, Torgeir, Sridhar Nerur, VenuGopal Balijepally, and Nils Brede Moe. "A decade of agile methodologies: Towards explaining agile software development." Journal of Systems and Software 85, no. 6 (June 2012): 1213–21. http://dx.doi.org/10.1016/j.jss.2012.02.033.
Full text