To see the other types of publications on this topic, follow the link: Agile system development methodology.
Journal articles on the topic 'Agile system development methodology'
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 system development methodology.'
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
Buchalcevova, Alena. "Application of Methodology Evaluation System on Current IS Development Methodologies." International Journal of Information Technologies and Systems Approach 11, no. 2 (July 2018): 71–87. http://dx.doi.org/10.4018/ijitsa.2018070105.
Full textAbstract:
This article focuses on IS development methodologies, especially on new agile scaling frameworks. A significant need for large-scale agile is presented together with the evidence of its usage in companies. The aim of this article is to examine selected agile scaling methodologies and frameworks, and compare them to each other and with other IS development methodologies. To do so, the Methodology Evaluation System METES is utilized for the assessment and comparison. Assessed IS development methodologies can be then used by companies for the selection of the appropriate methodology. Furthermore, presenting the results of the assessment especially in the graphical form supports better understanding of these methodologies.
2
Riesener, Michael, Christian Doelle, Stefan Perau, Philipp Lossie, and Guenther Schuh. "Methodology for iterative system modeling in agile product development." Procedia CIRP 100 (2021): 439–44. http://dx.doi.org/10.1016/j.procir.2021.05.101.
Full text
3
Rathore, Manvender, and Deepa Jose. "Software Upgradation Model Based on Agile Methodology." Oriental journal of computer science and technology 10, no. 2 (April 6, 2017): 352–58. http://dx.doi.org/10.13005/ojcst/10.02.14.
Full textAbstract:
Agile software development work on twelve principle for software development which implies requirements and solutions evolved through the combined teamwork of disciplined and interdisciplinary teams. The objective of this paper is to connect agile methodology with Version Control System for more efficient and effective utilization of resources. In this proposed model based on agile methodology, the Version Control System plays a vital role to make work done faster as compared to SCRUM. This paper compares various existing agile methodologies. The efficiency of the proposed model is proved through comparative analysis with existing agile methods and using ANOVA mathematical model. Bitbucket as Version Control System is used as web based hosting service and the proposed model is compared by maintaining similar sprints in SCRUM and VSprint model. VCS and previous SRS documents are the important components of this proposed model which helps in increasing the work speed at different phases of software development which the existing models does not consider.
4
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.
5
Fateev, Nikolai, and Iryna Zaporozhets. "AGILE-METHODOLOGY IN SHIPBUILDING PROJECT MANAGEMENT IN CONDITIONS OF CLUSTER INTEGRATION." Scientific Journal of Polonia University 43, no. 6 (June 18, 2021): 307–11. http://dx.doi.org/10.23856/4339.
Full textAbstract:
The aim of the article is to study the features of the development of cluster systems for the construction of transport vessels and develop on this basis recommendations for the use of agile methodology in the mechanisms of effective management in cluster integrations. The characteristic features of a project-oriented operating system with a matrix organizational structure have been determined. The principles of the agile methodology have been adapted to the management mechanisms of the shipbuilding cluster system. The examples of the use of agile approaches that complement and strengthen the existing matrix management structure in the shipbuilding cluster system are given. The agile approaches are implemented through: maintaining stable links in the supply chain at all stages of the life cycle of the cluster; focusing the cluster system as a whole on customer needs; creation of cross-functional teams for support and development of human resources; creation of a logistics center in accordance with the agile methodology, which is implemented through short feedback cycles and regular adaptation of supply processes; lean production ‒ from design to production at all stages. It is proposed to develop a corporate information system in business processes and supply chains of the shipbuilding cluster. Information flows connect cluster members, functions, supply chain management tasks, as well as different levels of management decision-making. Team cooperation between representatives of project organizations and the project management office of shipbuilding enterprises will ensure the development of the information system as a whole, as well as the integrity and consistency of individual elements. This confirms that the agile methodology provides flexibility in management and operational adaptation to changes in order to achieve the main goal ‒ the competitiveness of cluster integration and its elements.
6
Lee, Yong-Hee, and Gun-Ho Lee. "Development Process Improvement of Open-market System by using Agile Methodology." KIPS Transactions:PartD 17D, no. 3 (June 30, 2010): 203–8. http://dx.doi.org/10.3745/kipstd.2010.17d.3.203.
Full text
7
Hassan, Ali, Soayba Younas, and Amiya Bhaumik. "Agile Methodology in an SaaS Deployment Project." International Journal of Information Technology Project Management 12, no. 2 (April 2021): 1–29. http://dx.doi.org/10.4018/ijitpm.2021040101.
Full textAbstract:
Agile manifesto has proven its ability in managing and execution of projects in multiple industry sectors. Many researches have been conducted on the advantages and applicability of agile practices in software development and information technology industry. In this paper, empirical research has been conducted to identify the differences in agile management practices between software development and software as a service (SaaS) deployment projects. Case studies of a payment card industry (PCI) organization have been presented to identify key characteristics, tools, and methods of agile project management practices practically followed while implementing and managing of SaaS-based projects. Moreover, best suited agile management practices for pre- and post-deployment projects have also been discussed.
8
Rodríguez-Hernández, V., M. C. Espino-Gudiño, J. L. González-Pérez, J. Gudiño-Bazaldúa, and Victor Castano. "Assessing quality in software development: An agile methodology approach." Journal of Advanced Computer Science & Technology 4, no. 2 (June 9, 2015): 225. http://dx.doi.org/10.14419/jacst.v4i2.4173.
Full textAbstract:
<p>A novel methodology, result of 10 years of in-field testing, which makes possible the convergence of different types of models and quality standards for Engineering and Computer Science Faculties, is presented. Since most software-developing companies are small and medium sized, the projects developed must focuson SCRUM and Extreme Programming (XP), opposed to a RUP, which is quite heavy, as well as on Personal Software Process (PSP) and Team Software Process (TSP), which provide students with competences and a structured framework. ISO 90003:2004 norm is employed to define the processes by means of a quality system without new requirements or changing the existing ones. Also, the model is based on ISO/IEC 25000 (ISO (IEC 9126 – ISO/IEC 14598)) to allow comparing software built by different metrics.</p>
9
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.
10
Hanan Yulianto and Aries F. Firman. "Agile Project Management: Implementattion of Agile Working System in Bank Daya Usaha Sharia." Jurnal Indonesia Sosial Teknologi 2, no. 2 (February 21, 2021): 171–85. http://dx.doi.org/10.36418/jist.v2i2.91.
Full textAbstract:
Bank Daya Usaha Sharia as one of player in banking industry, experiencing with intense competition along with digitalization trend in banking industry so that competitor not only came from other bank but also come from internet and telecommunication industry. Bank Daya Usaha Sharia internally have treat which is slow to access or penetrate the market so that selected agile project management as working system because the methodology or approach already proven. Research questions related to condition Bank Daya Usaha Sharia are which working unit can implementation agile project management, what kind of agile methodology that is relevance and how agile project management can be implemented or what kind of factor influenced. Based on those questions, this research have objective to find out which working unit can implemented agile project management with relevance agile methodology and find out factors influenced that implementation. This research using qualitative research approach through interview, interview has conducted for eight (8) respondents, which is employee at Bank Daya Usaha Sharia at many level of position from department head, division head and director. With this interview, expected discover information about type project, project characteristic, project strategy and factors influenced in implementation agile project management. To determine type of project and project characteristic, use an approach Project Characteristic Quadrants by Goal and Solution Uncertainty, while to determine project strategy using approach Project Management Strategies Based on Complexity and Uncertainty. This research only conducted for four (4) working unit, among others Human Capital, Internal Audit, Business Risk & Development and Business Planning. Based on interview result and analysis, there are conclusions, such as working unit that possible implemented Agile Project Management are Human Capital, Business Risk & Development and Business Planning with Agile Methodology SCRUM, while Internal Audit more appropriate to implemented traditional project management. Thirteen (13) factors influenced in Agile Project Management implementation such as requirement, goals, solutions, team members, collaborative, directions, adapt to change, empowerment, agile mindset and organization drive. While reason why Bank Daya Usaha Sharia selected Agile Project Management as working system and implemented at current are competition, investment and best practice.
11
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.
12
Silas, Faki Agebee, Musa Yusuf, and Anah Hassan Bijik. "Hybridization of Class Responsibility Collaborators Model (HCRCM) with Function Point to enhance Project Estimation Cost in Agile Software Development." Circulation in Computer Science 2, no. 6 (July 20, 2017): 20–24. http://dx.doi.org/10.22632/ccs-2017-252-32.
Full textAbstract:
Estimating software cost in an agile system in terms of effort is very challenging. This is because the traditional models of software cost estimation do not completely fit in the agile development process. This paper presents a methodology to enhance the cost of project estimation in agile development. The hybridization adopts Class Responsibility Collaborators models with function point thereby boosting the agile software development estimation process. The study found out that adopting the Hybridized Class Responsibility Collaborator with function point has great improvement on cost estimation in agile software development.
13
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.
14
Dewi, Irma Amelia, Yusup Miftahuddin, Muhammad Assidiq Fattah, Cikal Bingah Palenda, and Syahrul Fathurrahman Erawan. "Point of Sales System in InHome Café Website using Agile Methodology." Journal of Innovation and Community Engagement 1, no. 1 (March 10, 2021): 01–19. http://dx.doi.org/10.28932/jice.v1i1.3321.
Full textAbstract:
The Point of Sales (POS) system is a system that supports sales transactions where POS is currently evolving because it can record sales, record inventory, print invoices, calculate profits and improve services for businesspeople and entrepreneurs. InHome Café is one of the growing cafe in Subang, Bandung. Ease of access to purchase products through online services led to an increase in transactions. At InHome Café Subang, data management, data processing, and sales transaction processing used to rely on a manual system or paper-based recording, which open to risks in data management and security. Therefore, to solve the problem, a website-based Point of Sales System was developed to record sales, collect inventory, print invoices, calculate profits using the PHP programming language with the CodeIgniter framework, and MySQL. The system was developed using the Agile development system with a reasoning that a short-term system development that emphasizes client satisfaction was required. The system functionality testing resulted in a success rate of 96.15%.
Keywords: agile, café, point of sales, scrum, website
15
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.
16
Salehi, Vahid, and Shirui Wang. "Munich Agile MBSE Concept (MAGIC)." Proceedings of the Design Society: International Conference on Engineering Design 1, no. 1 (July 2019): 3701–10. http://dx.doi.org/10.1017/dsi.2019.377.
Full textAbstract:
AbstractModel-based systems engineering (MBSE) is well-known in gaining the control over the complexity of systems and the development processes, while agile is a project management methodology originally from software development that uses short development cycles to focus on continuous improvement in the development of a product or service. In this paper, we adopt the concept of agile into MBSE and then proposed the new approach - Munich Agile MBSE Concept (MAGIC). The highlights of the MAGIC approach can be concluded as 1) the requirements which have been defined in the first stage will be examined and traced at each following stages; 2) communication between every 2 stages always exists in order to have a close connection during each system development phase; 3) the idea of Industry 4.0 has been included and reflected to achieve automation and data exchange with manufacturing technologies; 4) the concept of IOT (Internet of Things) is also considered when it comes to the usage and service of the system to satisfy the customer's needs; 5) the whole spirit of agile is reflected as the iterative and incremental design and development
17
Mitsuyuki, Taiga, Kazuo Hiekata, Takuya Goto, and Bryan Moser. "Evaluation of Project Architecture in Software Development Mixing Waterfall and Agile by Using Process Simulation." Journal of Industrial Integration and Management 02, no. 02 (June 2017): 1750007. http://dx.doi.org/10.1142/s2424862217500075.
Full textAbstract:
For software development, especially massive software systems, a waterfall process is used traditionally. A waterfall process can be highly effective on the condition that a master plan is fixed and the possibility of changes and uncertain rework is low. However, in software development projects, many kinds of reworks occur corresponding to uncertain requirement changes and program bugs. In addition, with the advent of cloud-based software platforms and continuous development operations, it is possible to develop a software system while operating the system. To respond to this situation, software development projects often adopt an agile process. Agility may allow conditional response to uncertain rework, yet at the same time it may be difficult to control the achievement of known project targets. Recently, many cases of adopting mixed processes including waterfall and agile have been reported in the massive software development projects. In this paper, we argue that the mixed process architecture should be designed, considering the scale of the targeted software project, the culture of organization, the probability of uncertain requirement changes, and so on. This paper proposes a methodology of evaluating the impact of waterfall, agile, and mixed project architectures by using process simulation. A project architectural approach is evaluated with a simulator which includes a software reliability growth model and uncertain rework driven by requirement change and error propagation. The proposed methodology was applied to a development project for a simple shopping website. The results showed that the proposed methodology allows exploration of partial agile adoption depending on the nature of the system development project, including its scale and chances of change. For example, in this paper, if the scale of the project is small, the positive effect of increasing agility by adopting agile processes is low. On the other hand, if the scale of the project is large, the effect of increasing agility by adopting agile process can increase. Furthermore, it became clear that it is important to not apply an agile process blindly, but instead to design a mixed project architecture considering the number of errors and development schedule targets across the project scope.
18
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.
19
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.
20
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.
21
Leite, Marco, and Vanessa Braz. "Agile manufacturing practices for new product development: industrial case studies." Journal of Manufacturing Technology Management 27, no. 4 (May 3, 2016): 560–76. http://dx.doi.org/10.1108/jmtm-09-2015-0073.
Full textAbstract:
Purpose – For decades multiple management philosophies directed toward lean production and mass were assumed as to respond to process inefficiencies and rampant consumerism, optimizing operation costs. However, new customization and flexible productions philosophies have been gaining ground in some industries, such as the agile manufacturing. From a literature review that addresses the history of this philosophy, it is clear that agile manufacturing is not fully comprehended, with very scarce information about practical cases. The paper aims to discuss these issues. Design/methodology/approach – In this paper the authors describe an exploratory methodology approach, with three semi-structured case study interviews. The goal is to study which of agile manufacturing practices are being applied in the studied companies and what is the perceived effect that these have on operational performance. Since most of these companies develop highly customized products, the role of agility on new product development can have a huge impact on their operational performance. Findings – Agile manufacturing is not yet a widespread philosophy of managing for the companies studied, being virtually unknown as a global concept. However, it was found that many of the practices of agile manufacturing are already implemented in these companies without association with this philosophy. It was also concluded, by the finding through respondents opinions, that agile practices contribute positively to the studied companies operating performance. Originality/value – The novelty of this research derives from observation of agile manufacturing practices in SMEs. This research is useful to SMEs implementing agile manufacturing principles.
22
Vaseva, E. S., D. F. Teregulov, and N. V. Buzhinskaya. "APPLICATION OF SCRUM AND KANBAN APPROACHES IN DISTANCE LEARNING OF FUTURE IT-SPECIALISTS." Vektor nauki Tol'yattinskogo gosudarstvennogo universiteta. Seriya Pedagogika i psihologiya, no. 2 (2021): 7–14. http://dx.doi.org/10.18323/2221-5662-2021-2-7-14.
Full textAbstract:
The online form of implementation of educational programs in a higher education institution should not affect the quality of competencies of a future graduate. For future successful employment and professional activity, an IT graduate should have skills and work styles associated with the application of modern software development technologies underlying the agile methodology. The goal of the study is to present an approach to introducing the ideas of the agile methodology into the educational process of a future IT specialist in the context of distance learning, comparing the possibilities of implementing two popular technologies of agile methodology – scrum and kanban, using the example of the Moodle distance learning system. To achieve this goal, the authors applied the following methods: the collection and analysis of scientific publications related to the study of features of agile technologies; the possibilities of their application in the educational process; monitoring the work of students according to agile methodology approaches when using the Moodle distance learning system. The analysis and observation of the students’ work allowed concluding on the possibility of introducing the methodology into the educational process carried out remotely using a distance learning system. The authors formulated recommendations on the application of distance learning tools for introducing the agile technologies in the learning process, in particular, the concept of distance course using the example of the Moodle online learning system, variants of the course objects settings, ways of evaluating the students’ work. The study shows that Moodle distance learning system acts as a virtual space where students interact as team members, implement project activities according to scrum and kanban approaches, using such course elements as a checklist, assignment, forum, and chat.
23
Carrera, Álvaro, Carlos A. Iglesias, and Mercedes Garijo. "Beast methodology: An agile testing methodology for multi-agent systems based on behaviour driven development." Information Systems Frontiers 16, no. 2 (July 18, 2013): 169–82. http://dx.doi.org/10.1007/s10796-013-9438-5.
Full text
24
Taylor, Katie Jane. "Adopting Agile software development: the project manager experience." Information Technology & People 29, no. 4 (November 7, 2016): 670–87. http://dx.doi.org/10.1108/itp-02-2014-0031.
Full textAbstract:
Purpose Early research into Agile approaches explored particular practices or quantified improvements in code production. Less well researched is how Agile teams are managed. The project manager (PM) role is traditionally one of “command and control” but Agile methods require a more facilitative approach. How this changing role plays out in practice is not yet clearly understood. The purpose of this paper is to provide insight into how adopting Agile techniques shape the working practices of PMs and critically reflect on some of the tensions that arise. Design/methodology/approach An ethnographic approach was used to surface a richer understanding of the issues and tensions faced by PMs as Agile methods are introduced. Ethnographic fiction conveys the story to a wider audience. Findings Agile approaches shift responsibility and spread expert knowledge seeming to undermine the traditional PM function. However, the findings here show various scenarios that allow PMs to wrest control and become more of a “gate-keeper”. Ethnographic fiction communicates a sense of the PMs frustration with the conflict between the need to control and the desire for teams to take more responsibility. Originality/value Stories provide insight and communicate the experiential feel behind issues faced by PMs adopting Agile to surface useful knowledge. The objective is not how to measure knowledge, but how to recognize it. These reflections are valuable to fellow researchers as well as practitioners and contribute to the growing literature on Agile project management.
25
Matsuo, Keita, and Leonard Barolli. "IoT sensors management system using Agile-Kanban and its application for weather measurement and electric wheelchair management." International Journal of Web Information Systems 16, no. 3 (July 22, 2020): 281–93. http://dx.doi.org/10.1108/ijwis-06-2020-0036.
Full textAbstract:
Purpose Recently, Internet of Things (IoT) devices and sensors are rapidly increasing in the word. They are connecting to the internet and are generating vast packets in the network. Thus, the networks could be congested, and the performance will degrade. For this reason, it is important to decrease the number of transmitted packets. Agile is a technique to develop the software and manage the work efficiently. Kanban is a method to support Agile development. The purpose of this paper is to propose an IoT sensors management system considering Agile–Kanban and show its application for weather measurement and electric wheelchair management. Design/methodology/approach The authors present the design and implementation of two systems and show the measurement device, data communication failure and experimental results. Findings The proposed Agile–Kanban system can manage a large amount of IoT sensors and can decrease the IoT sensor’s consumption power thus increasing the IoT sensor lifetime. Originality/value By experimental results, the authors have shown that the proposed systems have good performance and can control the IoT devices efficiently.
26
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.
27
Tøndel, Inger Anne, Martin Gilje Jaatun, Daniela Soares Cruzes, and Laurie Williams. "Collaborative security risk estimation in agile software development." Information & Computer Security 27, no. 4 (September 25, 2019): 508–35. http://dx.doi.org/10.1108/ics-12-2018-0138.
Full textAbstract:
PurposeToday, agile software development teams in general do not adopt security risk-assessment practices in an ongoing manner to prioritize security work. Protection Poker is a collaborative and lightweight software security risk-estimation technique that is particularly suited for agile teams. Motivated by a desire to understand why security risk assessments have not yet gained widespread adoption in agile development, this study aims to assess to what extent the Protection Poker game would be accepted by agile teams and how it can be successfully integrated into the agile practices.Design/methodology/approachProtection Poker was studied in capstone projects, in teams doing a graduate software security course and in sessions with industry representatives. Data were collected via questionnaires, observations and group interviews.FindingsResults show that Protection Poker has the potential to be adopted by agile teams. Key benefits include good discussions on security and the development project, along with increased knowledge and awareness. Challenges include ensuring efficient use of time and gaining impact on the end product.Research limitations/implicationsUsing students allowed easy access to subjects and an ability to collect rich data over time, but at the cost of generalizability to professional settings. Results from interactions with professionals supplement the data from students, showing similarities and differences in their opinions on Protection Poker.Originality/valueThe paper proposes ways to tackle the main obstacles to the adoption of the Protection Poker technique, as identified in this study.
28
Shim, Jung-Ah, Hyun-Jung Kwon, Hyun-ju Jung, and Moon-Sung Hwang. "Design of Acceptance Test Process with the Application of Agile Development Methodology." International Journal of Control and Automation 9, no. 2 (February 28, 2016): 343–52. http://dx.doi.org/10.14257/ijca.2016.9.2.32.
Full text
29
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.
30
Bogoyavlenska, Yuliya, Luca Persia, and Kateryna Bondarenko. "Smart-logistics for people management of innovative small and medium enterprises` development: Agile methodology." Economics. Ecology. Socium 4, no. 4 (December 31, 2020): 8–15. http://dx.doi.org/10.31520/2616-7107/2020.4.4-2.
Full textAbstract:
Introduction. Innovative entrepreneurship is one of the applied spheres, in which the implementation of core competencies: knowledge and skills from other areas is complicated nowadays due to challenges and rapid changes. Management systems for small and medium-sized enterprises are not so classical now, but horizontal and, what most importantly – flexible, agile is. Thus, it is proposed to turn to modern models of people management to increase the effectiveness of companies and institutions for future economy development.
Aim and tasks. The article appeals to management innovation and the use of the “mobility gap” as one of the most discussed economic problems that are necessary for the urban areas and require an appropriate solution development. The proposal is to use smart logistics for an effective people management system for innovative small and medium enterprises to zoom the weight of the cluster unit. The assertion that the increasing impact of horizontal management in outsourcing services is the way for further development and modernization of tax policy for the local economy.
Results. In the nearest future, the character of the local economy will change as communities develops cities, improving the quality of life, ensuring safety and neighbourhood policy and stimulating creative development. And it will create opportunities for cutting-edge initiatives, entrepreneurship and local municipalities, as well as developing relationships and competencies based on innovation and creative interaction between stakeholders in the new digital reality, while remaining people-centred. It is proposed to introduce management innovations into the management system according to the developed model according to the agile method of modernization: “to do” – list; "in progress" and motivation; “to verify” – monitoring; “done” – analysis; and business scaling. And to customize services, it is necessary the high quality achieving, speed that meets the needs of the market, and the quick creating of unique innovations.
Conclusions. This methodology has been tested by the project – Erasmus 2020, despite the “lockdown” conditions, by the open data project “City Code” with the aim of creating conditions for sustainable urban development by combining: talents, technologies, tolerance, and should be used to people management of small and medium-sized innovative enterprises.
31
Kramer, Jeremy, and Torrey Wagner. "Developmental Test and Requirements: Best Practices of Successful Information Systems Using Agile Methods." Delivering Performance at the Speed of Relevance: Agile Aquisition Approaches 26, no. 88 (April 1, 2019): 128–50. http://dx.doi.org/10.22594/dau.19-819.26.02.
Full textAbstract:
This article provides insights into the current state of developmental testing (DT) and requirements management in Department of Defense information systems employing Agile development. The authors describe the study methodology and provide an overview of Agile development and testing. Insights are described for requirements, detailed planning, test execution, and reporting. This work articulates best practices related to DT and requirements management strategies for programs employing modernized Software Development Life Cycle practices.
32
Azanha, Adrialdo, Ana Rita Tiradentes Terra Argoud, João Batista de Camargo Junior, and Pedro Domingos Antoniolli. "Agile project management with Scrum." International Journal of Managing Projects in Business 10, no. 1 (January 4, 2017): 121–42. http://dx.doi.org/10.1108/ijmpb-06-2016-0054.
Full textAbstract:
Purpose The purpose of this paper is to analyze the benefits of the agile project management (APM) framework compared to the traditional waterfall model, and understand how it can help companies add value and gain competitive advantage. Design/methodology/approach The methodology used was the exploratory qualitative research through a case study of a software project, developed with the support and application of the Scrum framework, in a pharmaceutical industry information technology project. Findings There were benefits found in the utilization of the agile framework, such as increased motivation and staff satisfaction, better control of requirements and especially higher quality of the delivered system, generating added value to the organization. Additionally, the project allowed the use of features from the first month of the application deployed, enabling a 75 percent reduction in development time, compared to traditional methods. The software development time was four months, 30 percent of what would be the total if the traditional methodology was adopted. Based on the results, the agile framework, especially the Scrum, proved to be a viable option as a project management approach. Research limitations/implications Since this research is an exploratory case study, its results cannot be generalized. Practical implications The paper provides relevant practical information and experiences to managers interested in implementing APM, as well as those interested in improving the management of projects. Originality/value This paper provides a case study with practical implications of using APM, and APM’s benefits and advantages are compared with the traditional waterfall approach. Companies can use this case study to better understand about the advantages and strengths of APM over the traditional approach.
33
Capili-Kummer, Marifel Grace, and Maria Leodevina C. Batugal. "Dynamic Alumni Monitoring with Decision Support System." International Journal of Recent Technology and Engineering 9, no. 5 (January 30, 2021): 279–84. http://dx.doi.org/10.35940/ijrte.f5308.019521.
Full textAbstract:
The present study focuses on gathering a real-time data on the employability of graduates. The web-based Dynamic Alumni Monitoring with Decision Support System is developed and linked to the institution’s website to gather alumni information. To realize the objective of this study, the agile method research design process is utilized. The agile methodology is a project management technique in software development process. The system has the capacity to monitor the graduates. It provides alumni verifications and confirmation after the pre-registration. The system has a platform in maintaining alumni data and notifications to periodically update the graduates’ profiles anytime and anywhere. The system has the capacity to make updates concerning alumni activities of the University. These are sent through their registered email addresses. Likewise, the system generates important reports needed by the school and its administrators.
34
Srivastava, Abhishek, P. K. Kapur, Deepti Mehrotra, and Rana Majumdar. "Modelling Fault Detection Using SRGM in Agile Environment and Ranking of Models." Journal of Cases on Information Technology 21, no. 2 (April 2019): 1–20. http://dx.doi.org/10.4018/jcit.2019040101.
Full textAbstract:
Today's software applications deployed in an enterprise to cater to the complex business processes, integrate various business units and address requirements of a global customer base. The traditional methodology of software engineering succumbs to the changing need of customer and technology advancement. On the behest of the customer, a software system should be designed in a way that it goes in concert with the present user needs. Agile methodology targets complex systems with its iterative, incremental, and evolutionary approach. There are numerous factors attributing towards the successful implementation of agile methodology. This led to adopting an approach of agile based on ‘lean' principles over the traditional software development life cycle (SDLC) approach. Collaborative work is done with the project team on a priority list. The implementation is done through “SCRUM” an empirical framework for learning. It has multiple sprints which are deliverable products. This idea has substantially reduced the ‘time to market' as the customer can decide which features of the software they would like to be delivered on a priority basis. To model trends of fault detection in each sprint, a growth model of software reliability is used. This research article presents a framework to analyze and measure the cumulative errors in an Agile Testing Process, the authors have applied modeling on various SRGMs to prove acceptability in an agile development process and finally compares these models using the Mahalanobis Distance Formula for Model ranking. The Mahalanobis distance criteria is easy to compute and that can be utilized to get the ranks and select the best model in view of an arrangement of contributing criteria.
35
Jiménez, Victor, Paulo Afonso, and Gabriela Fernandes. "Using Agile Project Management in the Design and Implementation of Activity-Based Costing Systems." Sustainability 12, no. 24 (December 11, 2020): 10352. http://dx.doi.org/10.3390/su122410352.
Full textAbstract:
The success of a costing system is dependent on its appropriation and assimilation by the organization. The involvement of all stakeholders from the early stages of design and implementation plays a critical role in this process. In this paper, the use of agile project management is investigated to support the design and implementation of more effective costing systems. A Design Science Research approach was followed to apply an agile project management approach—the Scrum methodology—to the design and implementation of an Activity-Based Costing (ABC) system in a hospital imaging service. The proposed methodology identifies the roles, the events, and the most important artifacts in the design and implementation of costing systems. Research results show that applying agile project management principles contributes to a higher degree of acceptance of the costing system by the operating personnel, as well as by top management. It was also found that a simpler model (result of sprint 5), instead of a more detailed one (proposed for sprint 4), may better fit the interests of the decision makers and the organization’s accounting and information systems. Thus, the best costing system is not necessarily the most complete or accurate, but the one that is most useful and adapted to the organization’s needs. The definition of the product backlog, the several sprints, and the iterative process were critical in this process. The adoption of the Scrum methodology allowed the design and implementation of an ABC system more adapted to the organization’s needs and allowed the early identification of problems that, traditionally, are only perceived at the end of the implementation process, therefore increasing the performance and economic sustainability of organizations.
36
Aarti, Mrs, and M. Karande. "SELECTION OF ENTERPRISE ARCHITECTURE BASED ON AGILE PARAMETERS FOR SCM-BASED CASE STUDY." Scholedge International Journal of Business Policy & Governance ISSN 2394-3351 4, no. 5 (September 21, 2017): 36. http://dx.doi.org/10.19085/journal.sijbpg040501.
Full textAbstract:
<strong>Aim/Purpose</strong>: This paper being a review paper shows mapping of enterprise architecture with respect to supply chain domain as per agile parameter so to find the best architecture for the development of the enterprise solution used in SCM company. <strong>Background /Methodology</strong>: Without EA, companies muddle through. In an agile environment selection of enterprise architecture is difficult even considering different parameters with SCM phases. This is a question and answer based research survey done for finding the mapping of SCM with different EAs were evaluated with 20yrs of experienced five experts. <strong>Originality/Value</strong>: This paper shows different EA mapped to SCM domain. Tabular format mapping of agile parameter with EA helps to find best EA for developing enterprise solutions even in agile environment. <strong>Findings</strong>: Comparison of 11 EA with a set of agile parameters shows that TOGAF is the most suitable EA for the development of the enterprise software solution. Systematic and structural working of TOGAF, handles the development in agile situation. <strong>Practical implications</strong>: Set of agile parameter from different phases of SCM may help practitioners to understand agile environment gives technical and logical gap which needs to consider in developing the software solution. <strong>Social implications</strong>: Mapping agile parameters at different strategies can help system to withstand in the changing environment with its impact on different operational levels of SCM. <strong>Research limitations/implications:</strong> Finding the type of agility and amount of agility in the SCM system can be an enhancement of this paper. Even more effective agile parameters affecting agility are the future of SCM.
37
Wang, Xiao Hua, and Xu Zeng. "A Preliminary Study on Software Architecture Evolution in Agile Development Process." Applied Mechanics and Materials 241-244 (December 2012): 2701–8. http://dx.doi.org/10.4028/www.scientific.net/amm.241-244.2701.
Full textAbstract:
Software architecture always exists in the target system although agile methodology (AM) weakens the design documents of the software architecture, and it will be improved continually as iteration process. The changes of business process and customer requirements should be dealt with in time. Therefore, it is essential that the stages of architecture evolution are explored in each release plan. The main hierarchy of architecture evolution is shown, the relationship between user stories and components is presented, and a method to support architecture evolution is given.
38
Zayat, Wael, and Ozlem Senvar. "Framework Study for Agile Software Development Via Scrum and Kanban." International Journal of Innovation and Technology Management 17, no. 04 (June 2020): 2030002. http://dx.doi.org/10.1142/s0219877020300025.
Full textAbstract:
This paper provides a systematic comparison between two well-known Agile methodologies: Scrum, which is a framework of doing projects by allocating tasks into small stages called sprints, and Kanban, which is a scheduling system to manage the flow of work by means of visual signals. In this regard, both methodologies were reviewed to explore similarities and differences between them. Then, a focus group survey was performed to specify the preferable methodology for product development according to various parameters in the project environment including project complexity, level of uncertainty, and work size with consideration of output factors like quality, productivity, and delivery. Results show the flexibility of both methodologies in approaching Agile objectives, where Scrum emphasizes on the corporation of the customer and development teams with a focus on particular skills such as planning, organization, presentation, and reviewing which makes it ideal for new and complex projects where a regular involvement of the customer is required, whereas Kanban is more operative in continuous-flow environments with a steady approach toward a system improvement.
39
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.
40
Нестеров, Алексей, and Alexey Nesterov. "Problems of Strategic Management of Socio-Economic Development at the Regional and Municipal Levels." Bulletin of Kemerovo State University. Series: Political, Sociological and Economic sciences 2018, no. 4 (January 14, 2019): 101–6. http://dx.doi.org/10.21603/2500-3372-2018-4-101-106.
Full textAbstract:
The paper features the problems of strategic management of social and economic development at the regional and municipal levels. Currently, the legal and the regulatory framework that ensures the management of socio-economic development at the regional and municipal levels is quite dynamic and corresponds with the current conditions and challenges. The legal and regulatory framework in the field of strategic management is formed not only as an institutional basis for socio-economic development: it also represents a thoroughly developed system of methods and tools for developing strategic documents and ensuring their implementation. However, normative legal documents reflect, as a rule, a traditional view of the implementation of the strategic planning process, formed within the scientific schools of design and planning, with the inclusion of individual elements of advanced technologies of strategic management. Federal authorities have consistently formed the basis for the actual strengthening of the role of the methodology of strategic management in regional and municipal management. The consistent implementation of the program-target approach, the methodology of strategic planning, the principles of project management in the practice of state and municipal management forms the basis for applying the principles of agile public administration as the basis for strategic management in real-time. Independence, initiative, innovation, openness, agile, competence, and high motivation will increasingly determine success in the practice of state and municipal government. Hence, successful work on overcoming the resistance of the administrative bureaucratic management system will be a pledge of effective implementation and application of mechanisms and technologies of project management and agile public administration.
41
Uvarina, N. V., and N. Yu Korneeva. "Aspects of Creative-Predictive Management in Modern Education." Prepodavatel XXI vek, no. 2, 2020 (2020): 11–19. http://dx.doi.org/10.31862/2073-9613-2020-2-11-19.
Full textAbstract:
The article deals with the aspects of creative and predictive management in education, formed on the basis of the trajectory of globalization, the strategy of development of predictive education at the present stage and the state of the legal and regulatory framework of modern vocational education. The researchers present the characteristics of the problem under consideration from the standpoint of its historical transformation and relevance in the regulatory and legal aspect. The essence of the notions “creative prediction” and “creative predictive management” is revealed; features of creative predictive management are presented; the process of creative predictive management as a social phenomenon and pedagogical phenomenon in modern education is revealed. As the results of the creative and predictive approach in management, the possibilities of creating educational agglomerations and creating an adapted AGILE-methodology in the education system are considered. The conclusion is made about the lack of methodological basis, regulatory and legal documentation, specific methods and forms of implementing the AGILE — methodology in management. Possibilities of AGILE-methodology application in managing the stakeholders of educational agglomeration are shown.
42
Ošlejšek, Radek, and Tomáš Pitner. "Optimization of Cyber Defense Exercises Using Balanced Software Development Methodology." International Journal of Information Technologies and Systems Approach 14, no. 1 (January 2021): 136–55. http://dx.doi.org/10.4018/ijitsa.2021010108.
Full textAbstract:
Cyber defense exercises (CDXs) represent an effective way to train cybersecurity experts. However, their development is lengthy and expensive. The reason lies in current practice where the CDX life cycle is not sufficiently mapped and formalized, and then exercises are developed ad-hoc. However, the CDX development shares many aspects with software development, especially with ERP systems. This paper presents a generic CDX development method that has been derived from existing CDX life cycles using the SPEM standard meta-model. The analysis of the method revealed bottlenecks in the CDX development process. Observations made from the analysis and discussed in the paper indicate that the organization of CDXs can be significantly optimized by applying a balanced mixed approach with agile preparation and plan-driven disciplined evaluation.
43
Denning, Stephen. "Agile: it’s time to put it to use to manage business complexity." Strategy & Leadership 43, no. 5 (September 21, 2015): 10–17. http://dx.doi.org/10.1108/sl-07-2015-0057.
Full textAbstract:
Purpose – Once executives understand how Agile and Scrum can manage the extraordinary complexities of software development, they will realize they can use the same management expertise to manage the mounting complexity of the rest of their business. Design/methodology/approach – The author explains that although the ideology of Agile puts emphasis on collaboration and teams, particularly self-organizing teams, managers should not confuse Agile teams with the generally unsuccessful efforts throughout the 20th Century to make teams a central and permanent aspect of management. Findings – In effect, Agile and Scrum represent a major management discovery, a scalable system to produce continuous customer-focused innovation in a dynamic business environment. Practical implications – Agile and Scrum can deal directly with current business issues by giving an authoritative voice to the customer and giving business and technical competence a preeminent role over authority. Originality/value – Agile/Scrum is enjoying added attention from managers in collaborative work arrangements such as networks and ecosystems. These arrangements can be scaled without sclerosis and seemingly without limit.
44
Hartono, Sugiarto. "Pengembangan Sistem Informasi Pemasaran pada Cv. Rumah Vera." ComTech: Computer, Mathematics and Engineering Applications 5, no. 1 (June 30, 2014): 410. http://dx.doi.org/10.21512/comtech.v5i1.2635.
Full textAbstract:
Evolving information technology can make business processes, which are carried out traditionally, transformed through the application of information technology that is useful for companies. Effective information systems design, should be used and provide a positive influence for the benefit of the organization. CV. Rumah Vera is a company that is engaged in the business of selling and marketing the property. The company began to realize that the implementation of information systems is very important in the development of its business. Rumah Vera requires a system that utilizes information technology, which can record all business transactions related to the marketing information system. Design methodology used is Agile methodology with object-oriented approach.
45
Thomas, Meetu, and Mali Senapathi. "Agile Requirements Engineering: An Empirical Analysis and Evidence from a Tertiary Education Context." Issues in Informing Science and Information Technology 16 (2019): 097–112. http://dx.doi.org/10.28945/4286.
Full textAbstract:
Aim/Purpose: The study describes empirical research into agile Requirements Engineering (RE) practices based on an analysis of data collected in a large higher education organization. Background: Requirements Engineering (RE) in agile development contexts is considerably different than in traditional software development. The field of agile RE is still nascent where there is a need to evaluate its impact in real-world settings. Methodology: Using a case study methodology, the study involved interviewing nine experienced software practitioners who reflected on the use and implementation of various agile RE practices in two software development projects of a student management system. Contribution: The primary contribution of the paper is the evaluation of agile RE practices in a large tertiary educational organization. Based on the analysis of the data, it provides valuable insights into the practice of agile RE in a specific context (i.e., education), but just as importantly, the ones that were omitted or replaced with others and why. Findings: While the evolutionary and iterative approach to defining requirements was followed in general, not all agile practices could be fully adhered to in the case organization. Although face-to-face communication with the customers has been recognized as one the most important agile RE practices, it was one of the most difficult practices to achieve with a large and diverse customer base. Addressing people issues (e.g., resistance to change, thinking, and mindset) was found to be a key driver to following the iterative RE process effectively. Contrary to the value-based approach advocated in the literature, the value-based approach was not strictly adhered to in requirements prioritization. Continuous integration was perceived to be a more beneficial practice than prototyping, as it allows frequent integration of code and facilitates delivering working software when necessary. Recommendations for Practitioners: Our study has important implications for practitioners. Based on our empirical analysis, we provide specific recommendations for effective implementation of agile RE practices. For example, our findings suggest that practitioners could address the challenges associated with limited face-to-face communication challenges by producing flexible, accessible, and electronic documentation to enable communication. Recommendations for Researchers: Researchers can use the identified agile RE practices and their variants to per-form in-depth investigations into agile requirements engineering in other educational contexts. Impact on Society: There are a number of new technologies that offer exciting new opportunities that can be explored to maximize the benefits of agile and other requirements techniques. Future Research: Future research could conduct case studies in different contexts and thus con-tribute to developing bundles or collections of practices to improve software development processes in specific contexts.
46
M Rejab, Mawarny, James Noble, and Stuart Marshall. "Agile Self-selecting Teams Foster Expertise Coordination." Interdisciplinary Journal of Information, Knowledge, and Management 14 (2019): 099–117. http://dx.doi.org/10.28945/4280.
Full textAbstract:
Aim/Purpose: This paper aims to discuss the activities involved in facilitating self-selecting teams for Agile software development projects. This paper also discussed how these activities can influence the successful expertise coordination in Agile teams. Background: Self-selecting teams enable Agile team members to choose teams based on whom they prefer to work with. Good team bonding allows Agile team members to rely on each other in coordinating their expertise resources effectively. This is the focal point where expertise coordination is needed in Agile teams. Methodology: This study employed Grounded Theory by interviewing 48 Agile practitioners from different software organizations mainly based in New Zealand. This study also carried out several sessions of observations and document analysis in conjunction with interviews. Contribution: This study contributes to the body of knowledge by identifying the way self-selecting teams support expertise coordination. Findings: Our findings indicated that the activities involved tend to influence the successful expertise coordination in Agile teams. Self-selecting teams are essential to supporting expertise coordination by increasing inter-dependencies between Agile team members, ensuring a diverse range of knowledge and skills in teams. Recommendations for Practitioners: The self-selecting team activities can be used as a guideline for Agile software organizations in forming self-selecting teams in the fastest and most efficient way. It is vital for management to facilitate the process of self-selecting teams in order to optimize successful expertise coordination. Recommendation for Researchers: There is potential for further Grounded Theory research to explore more activities and strategies involved in self-selecting teams. Impact on Society: Self-selecting teams in Agile software developments projects tend to boost the productivity of software development. Future Research: Several hypotheses can be tested through a deductive approach in future studies.
47
M. Randall, Robert. "Agile at IBM: software developers teach a new dance step to management." Strategy & Leadership 42, no. 2 (March 11, 2014): 26–29. http://dx.doi.org/10.1108/sl-01-2014-0003.
Full textAbstract:
Purpose – Explains how companies that are seeking to implement rapid innovation can adopt the Agile software development approach. In Agile, self-organizing teams work in short cycles called “sprints” and develop the features to enable the product to continuously evolve in the light of the experience they gain and through customer feedback. Design/methodology/approach – For insight into how Agile is being implemented at a leading software services firm with clients in hundreds of industries, Strategy & Leadership asked Rob Purdie, Agile Practice Lead for the IBM Design Lab, how Agile software development methods were contributing to the success of IBM's key digital marketing initiatives. Findings – The traditional approach to software development is to define, design, develop and test everything – before delivering anything. With Agile, managers can reduce waste by prioritizing features based on relative business value, evaluating and re-designing as the project proceeds. Practical implications – Agile requires leaders and teams to work and learn through problems, designs and options in an open and transparent environment. It places new demands on technical leaders in terms of negotiation and planning skills. Originality/value – Managers outside the software industry should note that Agile/Scrum is likely to be increasingly essential to the future of product development and manufacturing. Nowadays many products for consumers and businesses include embedded software systems, so developing products in the future will require deeper collaboration across multiple engineering disciplines and marketing teams and familiarity with the Agile approach.
48
Werder, Karl, and Alexander Maedche. "Explaining the emergence of team agility: a complex adaptive systems perspective." Information Technology & People 31, no. 3 (June 4, 2018): 819–44. http://dx.doi.org/10.1108/itp-04-2017-0125.
Full textAbstract:
Purpose Agile software development helps software producing organizations to respond to manifold challenges. While prior research focused on agility as a project or process phenomenon, the authors suggest that agility is an emergent phenomenon on the team level. The paper aims to discuss this issue. Design/methodology/approach Using the theory of complex adaptive systems (CASs), the study captures the multiple influencing levels of software development teams (SDTs) and their interplay with self-organization and emergence. The authors investigate three agile SDTs in different contextual environments that participate with four or more different roles each. Findings The results suggest self-organization as a central process when understanding team agility. While contextual factors often provide restriction on self-organization, they can help the team to enhance its autonomy. Research limitations/implications The theoretical contributions result from the development and test of theory grounded propositions and the investigation of mature agile development teams. Practical implications The findings help practitioners to improve the cost-effectiveness ratio of their team’s operations. Originality/value The study provides empirical evidence for the emergence of team agility in agile SDTs. Using the lens of CAS, the study suggests the importance of the team’s autonomy.
49
George, Joey F., Kevin Scheibe, Anthony M. Townsend, and Brian Mennecke. "The amorphous nature of agile: no one size fits all." Journal of Systems and Information Technology 20, no. 2 (May 14, 2018): 241–60. http://dx.doi.org/10.1108/jsit-11-2017-0118.
Full textAbstract:
Purpose This paper aims to investigate the extent to which newly agile organizations followed 2001’s Agile Manifesto, especially in terms of the 12 principles of the agile approach, as included in the Manifesto. Design/methodology/approach The authors conducted in-depth case studies of groups in three large business organizations that had recently adopted agile. Two researchers spent one day at each site, attending daily standups and conducting interviews with managers, developers and customers. Findings Across the three organizations, developers were faithful to two agile principles: the primacy of delivering valuable software continually and regular reflections on the process with an eye toward improvement. The developers were uniformly unfaithful to the principle that requires face-to-face communication. Each organization varied in their adherence to the remaining nine principles. Obstacles to faithful adoption included the experience of the organization with agile, the extent to which the industry was regulated and the extent to which developers and customers were physically dispersed. Originality/value While past research on agile development is extensive, this paper examines perspectives on the method and its adoption through the lens of the original Agile Manifesto and its 12 principles. The principles were grouped into three broader categories – software delivery, people and process – to provide additional insights and to sharpen the analysis.
50
Lemieux, Andree-Anne, Samir Lamouri, Robert Pellerin, and Simon Tamayo. "Development of a leagile transformation methodology for product development." Business Process Management Journal 21, no. 4 (July 6, 2015): 791–819. http://dx.doi.org/10.1108/bpmj-02-2014-0009.
Full textAbstract:
Purpose – The purpose of this paper is to propose a leagile transformation model for product development that guides manufacturers in the construction of a road map and the management of its deployment in line with both lean and agile improvement objectives. Design/methodology/approach – An intervention qualitative and transformative research approach was adopted in order to develop required knowledge to theorise professional practice made from rigorous observations of facts. The research project took place over a period of two and a half years, in partnership with an international firm that develops and produces a wide range of luxury products. Findings – The application of the methodology proved that a lean transformation does not have to be generated only by the field needs but it can follow a mixed approach where a top-down transformation management linked with strategic objectives is deployed without compromising implication and needs from people on the field. The right balance can be found between the strategic aspect of transformation and the incremental aspect on the field of lean paradigms. Research limitations/implications – For complete validation and widespread scientific application, the model should be tested in other sectors and industries. Practical implications – The application case of the leagile model in several divisions of a luxury organisation proved that the proposed approach can be used as a guide for manufacturer in the construction of an improvement road map and in the management of its deployment. The application cases enabled a number of positive results to be generated and measured on quantitative indicators such as service ratio for new products for which, one of the divisions saw an increase of 30 per cent. The approach created a positive revolution among development team members by its potential in terms of communication, steering, benchmarking and knowledge system. Originality/value – The model supports the identification and prioritisation of improvement initiatives by focusing on the levers for improvement that meet the needs and objectives of transformation, as well as the organisation’s maturity level.