Статті в журналах: "Agile Scrum"

1

Moses, Joseph. "Agile Writing." International Journal of Sociotechnology and Knowledge Development 7, no. 2 (April 2015): 1–13. http://dx.doi.org/10.4018/ijskd.2015040101.

Повний текст джерела

Анотація:

Scrum methodologies that support cross-functional writing teams to develop polished increments of writing instead of lengthy drafts of documents stand to improve productivity and learning within organizations. Scrum methodologies may be deployed in higher education as well as in nonacademic settings to achieve purposeful knowledge transfer across disciplines and across academic/industry borders. Key to scrum is an emphasis on productivity within fixed time frames, with productivity facilitated by learning that emerges in cross-functional teams. Higher education is similarly a domain in which productivity in fixed time frames takes the measure of student learning. Across the disciplines, scrum methodologies show promise for improving the quality of collaborative problem-solving in writing projects in college and at work.

Стилі APA, Harvard, Vancouver, ISO та ін.

2

Kühn, Philipp M., and Nikolaus Ehlenz. "Agile Werkverträge mit Scrum." Computer und Recht 34, no. 3 (March 1, 2018): 139–51. http://dx.doi.org/10.9785/cr-2018-340303.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

3

., K. Selvi. "SCRUM: AN AGILE PROCESS." International Journal of Research in Engineering and Technology 02, no. 03 (March 25, 2013): 337–40. http://dx.doi.org/10.15623/ijret.2013.0203019.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

4

Pfeffer, Joachim, and Jean Pierre Berchez. "Agile Arbeitsweisen mit Scrum." ATZelektronik 12, no. 5 (September 27, 2017): 58–61. http://dx.doi.org/10.1007/s35658-017-0073-7.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

5

Scheller, Vibeke Kristine, Sidsel Lond Grosen, and Helge Hvid. "Scrum-baseret projektstyring — en standard for bedre psykisk arbejdsmiljø?" Tidsskrift for Arbejdsliv 15, no. 4 (December 1, 2013): 76–94. http://dx.doi.org/10.7146/tfa.v15i4.108949.

Повний текст джерела

Анотація:

Artiklen undersøger, hvorledes agil projektstyring og -ledelse påvirker det psykiske arbejdsmiljø i IT-sektoren. Scrum, en type agil projektstyring, er en procedurel standard, hvor tilrettelæggelsen af arbejdet foregår løbende med en høj grad af medarbejderinvolvering. Det er derfor nærliggende at antage, at der her er tale om en standard, som skaber løsninger på nogle af de psykosociale belastninger, der findes i IT-sektoren. Dette studeres i to sammenlignelige casevirksomheder. I den ene virksomhed bidrager den agile standard positivt til det psykiske arbejdsmiljø, i den anden virksomhed bidrager den agile standard til en udvikling, der forringer det psykiske arbejdsmiljø. Det konkluderes, at agile standarder har potentiale til at forbedre det psykiske arbejdsmiljø. Hvorvidt disse potentialer realiseres afhænger af samspillet med andre standarder i organisationen og implementeringens

Стилі APA, Harvard, Vancouver, ISO та ін.

6

Khalid, Ayesha, Shariq Aziz Butt, Tauseef Jamal, and Saikat Gochhait. "Agile Scrum Issues at Large-Scale Distributed Projects." International Journal of Software Innovation 8, no. 2 (April 2020): 85–94. http://dx.doi.org/10.4018/ijsi.2020040106.

Повний текст джерела

Анотація:

The agile model is a very vast and popular model in use in the software industry currently. It changes the way software is developed. It was introduced in 2001 to overcome deficiencies of software development in a workshop arranged by researchers and practitioners who were involved with the agile concept. They introduced the complete agile manifesto. The agile model has main components that make it more viable for use in well-organized software development. One of these is scrum methodology. The reason for the agile-scrum popularity is its use for small-scale projects, making small teams and allows change requests at any stage of a project from the client. It works for client satisfaction. Instead of so much popularity and distinctive features, agile-scrum also has some limitations when used for large scale projects development that makes it less efficient for development. This article discusses the agile-scrum methodology and its limitations when using for large-scale project organization.

Стилі APA, Harvard, Vancouver, ISO та ін.

7

Ittensohn, Mark, and Micha Rieser. "Agile Produktentwicklung an Bibliotheken: Ein Erfahrungsbericht aus der Zentralbibliothek Zürich." Bibliothek Forschung und Praxis 45, no. 3 (November 27, 2021): 509–16. http://dx.doi.org/10.1515/bfp-2021-0046.

Повний текст джерела

Анотація:

Zusammenfassung Der Bericht zeigt anhand einer Fallstudie aus der Zentralbibliothek Zürich auf, welche Vorteile und Herausforderungen die agile Produktentwicklung an Bibliotheken haben kann. Im Zentrum steht dabei das Rahmenwerk Scrum, welches zur Entwicklung des Fallbeispiels – eines Escape Games – genutzt wurde. Wie der Bericht nahelegt, hängt der Erfolg der agilen Produktentwicklung wesentlich vom Komplexitätsgrad des Produktes sowie vom gemeinsamen Verständnis von Scrum und seiner Einbettung in andere Projektmanagement-Verfahren ab.

Стилі APA, Harvard, Vancouver, ISO та ін.

8

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.

Повний текст джерела

Анотація:

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.

Стилі APA, Harvard, Vancouver, ISO та ін.

9

Чуланова, Оксана, Oksana Chulanova, А. Меркулова, and A. Merkulova. "Methodical Instrumentation of Scrum Application as the Variety of the Methodology of Flexibility of Agile Manifesto Projects in the Management of Project Activity." Management of the Personnel and Intellectual Resources in Russia 7, no. 2 (June 13, 2018): 61–66. http://dx.doi.org/10.12737/article_5afedb6a7bdfa3.22810979.

Повний текст джерела

Анотація:

Project management includes many approaches and tools. The article presents the main principles of Agile as a methodology for flexible project management Agile manifesto. The main varieties of Agile manifesto are presented and the results of the author’s assessment of the possibilities and expediency of using each of the varieties are presented. More in detail in the article is considered Scrum. This methodology is popular in the development of complex projects. The essence of Scrum is to divide the entire process of the project into a lot of sprints, which require approximately the same amount of time to complete. Each sprint must combine an established number of specific tasks. The article notes that the ideological foundations of SCRUM are more clearly reflected in the Agile manifesto. This technology allows you to get the desired effect with minimal resources. Scrum allows you to correctly form resources and maximize the potential of the team. The article explores in detail the opportunities and risks that entail the use of one of the varieties of a flexible methodology for project management — Scrum. The author’s development of the methodological toolkit for implementing Scrum in project management of the organization is presented.

Стилі APA, Harvard, Vancouver, ISO та ін.

10

Amarta, Afrisco Ardytia Febrian, and Indra Gita Anugrah. "Implementasi Agile Scrum Dengan Menggunakan Trello Sebagai Manajemen Proyek Di PT Andromedia." Jurnal Nasional Komputasi dan Teknologi Informasi (JNKTI) 4, no. 6 (December 29, 2021): 528–34. http://dx.doi.org/10.32672/jnkti.v4i6.3702.

Повний текст джерела

Анотація:

Abstrak — Pengembangan software erat kaitannya dengan rangkaian proses SDLC (Software Development Lifecycle). Dalam penerapan SDLC ada beberapa metodologi yang bisa diterapkan seperti waterfall dan agile. Waterfall merupakan suatu metodologi yang tahapan-tahapannya dilakukan secara berurutan. Hal ini menjadi sebuah kendala di metode waterfall jika terdapat perubahan requirement atau kebutuhan di tengah proses pengembangan. Berbeda dengan agile dimana tahapan-tahapannya dilakukan secara iteratif atau berulang. Namun dalam penerapannya membutuhkan kerangka kerja yang mendukung konsep agile, salah satunya adalah scrum. Dalam penerapan agile scrum membutuhkan alat yang bisa berfungsi sebagai kolaborasi antar anggota tim serta pencatatan manajemen proyek. Salah satu alat yang bisa digunakan adalah trello. Abstract — Software development is closely related to the SDLC (Software Development Lifecycle) process chain. Several methodologies can be applied in implementing the SDLC, such as waterfall and agile. The waterfall is a methodology whose stages are carried out sequentially. This becomes an obstacle in the waterfall method if there is a change in needs or needs in the middle of the development process. In contrast to agile where the stages are carried out iteratively or repeatedly. However, its implementation requires a framework that supports agile concepts, one of which is scrum. In implementing agile scrum, you need a tool that can work as a collaboration between team members and project management records. One tool that can be used is Trello.

Стилі APA, Harvard, Vancouver, ISO та ін.

11

Prymak, V., and B. Korzh. "AGILE MANAGEMENT OF TEAMWORK OF ENGINEERING PROJECTS." Bulletin of Taras Shevchenko National University of Kyiv. Economics, no. 207 (2019): 21–27. http://dx.doi.org/10.17721/1728-2667.2019/207-6/3.

Повний текст джерела

Анотація:

The problems of introduction of agile methodologies in the process of functioning of domestic enterprises in the field of engineering services are investigated. The main reasons for the transition from the traditional cascade model of project team management to agile technologies, in particular, Scrum and Kanban, are identified. The main stages of implementation of engineering service based on Scrum and Kanban methodologies according to the level of organizational maturity of the enterprise are distinguished. A combined Scrum-Kanban adaptive model has been created to enable Agile principles to be implemented in a team management system at engineering services.

Стилі APA, Harvard, Vancouver, ISO та ін.

12

D. Fedenko. "AGILE AND SCRUM IN ACCOUNTING." Herald of the Economic Sciences of Ukraine, no. 2(37) (December 23, 2019): 212–13. http://dx.doi.org/10.37405/1729-7206.2019.2(37).212-213.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

13

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.

Повний текст джерела

Анотація:

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.

Стилі APA, Harvard, Vancouver, ISO та ін.

14

Pfeffer, Joachim, and Jean Pierre Berchez. "Agile working practices with scrum." ATZelektronik worldwide 12, no. 5 (October 2017): 52–55. http://dx.doi.org/10.1007/s38314-017-0073-7.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

15

Pawar, Rupali Pravinkumar, and Kirti Nilesh Mahajan. "Implementation of Change Management in Software Development by using Scrum Framework." International Journal of Advanced Research in Computer Science and Software Engineering 7, no. 7 (July 30, 2017): 400. http://dx.doi.org/10.23956/ijarcsse.v7i7.164.

Повний текст джерела

Анотація:

This paper will focus on implementation of change management in Scrum software development framework . Scrum is one of the mostly used software development framework from the Agile software development methodology. Scrum is based on iterative and incremental process. It is suitable for unstable requirements. The use of Scrum proved to be beneficial due to tight schedule and loosely defined user requirements that often changed during the development. The aim of the paper to study implementation process of change management in Scrum . First part of paper gives detailed information of Scrum framework. The middle of the paper presented the organizational process of agile software development using Scrum. Finally, the paper point out key points for managing changes in Scrum implementation. The primary data collection method was interviews of the industry expertise. The secondary source of data is reference books and Internet articles. This paper will help to understand basics of Scrum software development framework and process of change management in developing projects by using Scrum framework.

Стилі APA, Harvard, Vancouver, ISO та ін.

16

Kalyani, Darshita, and Devarshi Mehta. "Study of Agile Scrum and Alikeness of Scrum Tools." International Journal of Computer Applications 178, no. 43 (August 19, 2019): 21–28. http://dx.doi.org/10.5120/ijca2019919318.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

17

Neamah Ahmed, Mohammed, and Sawsan Rasheed Mohammed. "Agile Quality Management Framework in Construction Projects (AQMFCP)." International Journal of Engineering & Technology 7, no. 4.20 (November 28, 2018): 307. http://dx.doi.org/10.14419/ijet.v7i4.20.25944.

Повний текст джерела

Анотація:

In project management there has been a shift from traditional project management to the Agile Project Management (APM) style. The proposed Agile Quality Management Framework in Construction Projects will be built as a sequence of procedure that deals with a project from primary vision of project to the final delivery of project, will trace alignment and discover a contact between Agile and Traditional Project Management (TPM) concepts and find contact points among two of the more used Agile frameworks (scrum) and one of the more confirmed Project Management framework (PMBOK®) processes. This will result in a recognition of comparable areas between scrum and PMBOK® processes. Agile quality Management Framework is a new agile framework that covers the whole project lifecycle. The goal of the framework is to assist the project managers to adapt a more flexible approach to managing and implementing the construction project. The findings arrive that the agile project management using the Scrum methodology profits effectiveness procedures and a lower duration of process, ensuring value of quality planning and control inputs.

Стилі APA, Harvard, Vancouver, ISO та ін.

18

Ridha, Fakhrul, and Ega Hegarini. "Analysis of Maturity Level Project Management of Software Development In Scrum Framework: Case Research On Tribe Enterprise PT. XYZ." IT Journal Research and Development 5, no. 1 (July 24, 2020): 87–97. http://dx.doi.org/10.25299/itjrd.2020.vol5(1).4662.

Повний текст джерела

Анотація:

One of the most widely used product developments now is Agile Development Method. In Agile Development there are several frameworks, one of them is Scrum. This research examines the maturity level of software development project management that applies Scrum framework. The research was conducted using quantitative research methodologies using Scrum Maturity Model. Data was collected by distributing questionnaires to employees at a company that works as a Scrum Master. In addition to the data obtained from the questionnaire, interviews were also conducted to confirm answers from respondents. The interview aims to ensure the answers given by respondents are consistent with documentary evidence carried out through the research of project documents. Then the data analysis is done by assessing the level of maturity of each process in the Scrum framework using Agile Maturity Model (AMM) approach. The results from the analysis of Maturity Level Project Management of Software Development are used to provide recommendations for improvement to achieve a higher level of maturity.

Стилі APA, Harvard, Vancouver, ISO та ін.

19

Žužek, Tena, Janez Kušar, Lidija Rihar, and Tomaž Berlec. "Agile-Concurrent hybrid: A framework for concurrent product development using Scrum." Concurrent Engineering 28, no. 4 (September 24, 2020): 255–64. http://dx.doi.org/10.1177/1063293x20958541.

Повний текст джерела

Анотація:

Agile development became very popular at the beginning of the 21st century when the Manifesto for Agile Software Development was released. Since then, it has been predominant in the software industry and has been increasingly transferred to the development of physical products due to its great success. There are many studies on Agile-Stage-Gate hybrids that combine agile Scrum and the traditional Stage-Gate model, however no research has been found that addresses a direct integration of Scrum into a concurrent product development model in a similar way. In this paper, we therefore examine the possibility of introducing Scrum into the concurrent product development and propose a Scrum framework for an Agile-Concurrent hybrid. We propose that the framework for concurrent development remains unchanged: the stages overlap and the track-and-loop approach is preserved, while Scrum is proposed for the execution of day-to-day work. The main advantage of the proposed hybrid is that after each iteration the customer reviews the results of an entire loop, not just of one stage, which enables a broader understanding of the progress and facilitates a more extensive feedback. A quicker resolution of discrepancies, and a faster and more effective response to change is thus ensured. In the paper, the needed organizational changes and potential implementation issues are also discussed.

Стилі APA, Harvard, Vancouver, ISO та ін.

20

Beck, Chris. "Joining the Scrum." Manufacturing Management 2019, no. 9 (September 2019): 28–29. http://dx.doi.org/10.12968/s2514-9768(22)90038-9.

Повний текст джерела

Анотація:

Popular in software development, the ‘Scrum’ method of agile projectmanagement can translate to a manufacturing environment, as discovered to great effect by Oxfordshire manufacturer, Crowcon Detection Instruments

Стилі APA, Harvard, Vancouver, ISO та ін.

21

Mesaros, Diana, T. Rusu, and I. Mesaros. "Agile Scrum Applied in Agricultural Processes." Scientific Bulletin of Electrical Engineering Faculty 22, no. 1 (July 1, 2022): 1–5. http://dx.doi.org/10.2478/sbeef-2022-0010.

Повний текст джерела

Анотація:

Abstract This paper presents a case study of interdisciplinary subjects, more precisely the AGILE SCRUM specific to software development applied in agricultural processes to increase the productivity, maximize the profit and to emphasize the benefits of AGILE methodology which is suitable in every field of industry. Starting with theoretical aspects about Agile project management approach and philosophy, including values and principles, continuing with SCRUM framework, is emphasized the applicability of the method in various fields of industry, including agriculture.

Стилі APA, Harvard, Vancouver, ISO та ін.

22

Róbert Modranský, Silvia Jakabová, Michal Hanák, and Albert Oláh. "Lean and Agile Project Management and the Challenges for its Implementation in SMEs in Czech Republic." Technium Social Sciences Journal 9 (July 8, 2020): 413–40. http://dx.doi.org/10.47577/tssj.v9i1.1145.

Повний текст джерела

Анотація:

The purpose of this paper is to investigate the possibilities, challenges and benefits of implementing Lean & agile project management in manufacturing SMEs. Lean & agile project management methods were originally developed for the software development industry, where they have revolutionized the way projects are managed. In the last decade, practitioners outside software development industry have started to realize the potential and benefits of implementing the agile approach. However, there are still only a few researches devoted to agile hardware development, and even fewer on the possibilities of its implementation in SMEs. By conducting a case study in the only manufacturing SMEs that has successfully implemented Scrum, analysing internal company’s documents and interviewing several employees and top managers from different sectors, who participated in the projects where Scrum was implemented, the lessons this organization has learned and that could be beneficial for both researchers and practitioners, are reported. The findings from this research show that although some adaptions of the Scrum framework were required, the applicability of the Scrum in this manufacturing SME was possible and beneficial.

Стилі APA, Harvard, Vancouver, ISO та ін.

23

DRURY-GROGAN, MEGHANN L., and ORLA O'DWYER. "AN INVESTIGATION OF THE DECISION-MAKING PROCESS IN AGILE TEAMS." International Journal of Information Technology & Decision Making 12, no. 06 (November 2013): 1097–120. http://dx.doi.org/10.1142/s0219622013400105.

Повний текст джерела

Анотація:

This paper first explores the decision-making process in agile teams using scrum practices and second identifies factors that influence the decision-making process during the Sprint Planning and Daily Scrum Meetings. We conducted 34 semi-structured interviews and 18 observations across four agile teams. Our findings show that a rational decision-making process is sometimes followed in the Sprint Planning and Daily Scrum Meetings and that three factors can influence the rational decision-making process: sprint duration, experience and resource availability. Additionally, decisions are not always made in a collaborative manner by team members. This research contributes to the decision-making literature and project management literature by highlighting difficulties pertinent to decision making in agile teams.

Стилі APA, Harvard, Vancouver, ISO та ін.

24

Yahya, Norzariyah, and Siti Sarah Maidin. "Hybrid agile development phases: the practice in software projects as performed by software engineering team." Indonesian Journal of Electrical Engineering and Computer Science 29, no. 3 (March 1, 2023): 1738. http://dx.doi.org/10.11591/ijeecs.v29.i3.pp1738-1749.

Повний текст джерела

Анотація:

<span lang="EN-US">The combination of scrum and waterfall is one of the software engineering teams that preferred hybrid agile models. The purpose of combining the two models is to leverage the advantages of each also to tailor the hybrid agile model to the needs of the project. However, to what extent are the phases, stages, and features of scrum and waterfall implemented in a software project remains unclear. Additionally, which phase will employ scrum, and when will waterfall be deemed optimal is also the arising question. This research adopted a qualitative study, and interviews are used as a data collection instrument. The interview is conducted based on an interview protocol, and thematic analysis is utilized to extract the themes from the interviews. This study investigates how the scrum and waterfall models are utilized in a software project, and three themes were identified in answering the research question. The findings indicate five development phases in a hybrid agile project and that waterfall is the preferable model in planning, while development is on scrum, and project testing and deployment could be either waterfall or scrum.</span>

Стилі APA, Harvard, Vancouver, ISO та ін.

25

Tohirin, Tohirin, and Septian Rheno Widianto. "Peran Trello dalam Adopsi Agile Scrum Pada Pengembagan Sistem Informasi Kesehatan." MULTINETICS 6, no. 1 (June 7, 2020): 32–39. http://dx.doi.org/10.32722/multinetics.v6i1.2763.

Повний текст джерела

Анотація:

Agile scrum merupakan metodologi pengembangan sistem informasi yang sangat populer saat ini. Trello merupakan aplikasi sebagai tempat bekerja secara kolaboratif. Penelitian ini menunjukkan bahwa kombinasi pemanfaatan Agile Scrum dan Trello dapat terus dipelihara dan dipraktikkan oleh pengembang sistem informasi e-Puskesmas, sistem informasi OLTP. Kombinasi keduanya cukup dapat diandalkan, bahkan sampai penelitian ini ditulis sudah sampai Sprint ke-58.

Стилі APA, Harvard, Vancouver, ISO та ін.

26

., Tohirin. "PEMODELAN AGILE SCRUM DENGAN ALAT BANTU TRELLO DALAM PENGEMBANGAN SISTEM INFORMASI PUSAT KESEHATAN MASYARAKAT (E-PUSKESMAS)." Kurawal - Jurnal Teknologi, Informasi dan Industri 3, no. 1 (March 10, 2020): 93–103. http://dx.doi.org/10.33479/kurawal.v3i1.307.

Повний текст джерела

Анотація:

Agile scrum adalah metodologi pengembangan sistem informasi yang sangat populer saat ini. Trello adalah aplikasi sebagai tempat bekerja kolaboratif. Penelitian ini menunjukkan bahwa aplikasi kombinasi Agile Scrum dan Trello sebenarnya dipelihara dan dipraktikkan oleh pengembang sistem informasi e-Puskesmas, sebagai sistem informasi OLTP. Kombinasi ini cukup dapat diandalkan, bahkan saat tulisan ini ditulis hingga Sprint ke58.

Стилі APA, Harvard, Vancouver, ISO та ін.

27

Sharma, Nidhi, and Manoj Wadhwa. "eXSRUP: Hybrid Software Development Model Integrating Extreme Programing, Scrum & Rational Unified Process." TELKOMNIKA Indonesian Journal of Electrical Engineering 16, no. 2 (November 1, 2015): 377. http://dx.doi.org/10.11591/tijee.v16i2.1627.

Повний текст джерела

Анотація:

<p>Software industries are progressively adopting the agile development practices of customized models such as Extreme Programming (XP) or Scrum or Rational Unified Process (RUP). Scrum and Extreme Programming (XP) are frequently used agile models, whereas Rational Unified Process (RUP) is one popular classic plan driven software development methodology. Both agile and plan driven models have their own merits & demerits such as XP has good engineering practices, team collaboration and on the other hand weak documentation, poor performance in medium & large scale projects. Scrum is based on project management practices. RUP model has some limitations such as impractical for small and fast paced projects, tendency to be over budgeted, condemn rapid changes in requirements. This research paper based on proposes hybrid framework eXSRUP by combining strengths of Scrum, XP and RUP by suppressing their limitations to produce high quality software.</p>

Стилі APA, Harvard, Vancouver, ISO та ін.

28

Prima, Yа G. "Human capital of the project team in the context of Agile business transformation." Ekonomicheskie i sotsial’no-gumanitarnye issledovaniya, no. 2(30) (June 2021): 28–36. http://dx.doi.org/10.24151/2409-1073-2021-2-28-36.

Повний текст джерела

Анотація:

The article is devoted to research on agile management practices, including Scrum. Their distribution and the effects of their use by companies under conditions of Agile business transformation in Russia and abroad are considered in detail. The factors influencing the efficiency of using human capital of self-organizing teams were revealed. The main models of human capital assessment from the position of their applicability to Scrum teams were analyzed.

Стилі APA, Harvard, Vancouver, ISO та ін.

29

Mahnič, Viljan, Strahil Georgiev, and Tomo Jarc. "Teaching Scrum in Cooperation with a Software Development Company." Organizacija 43, no. 1 (January 1, 2010): 40–48. http://dx.doi.org/10.2478/v10051-010-0005-2.

Повний текст джерела

Анотація:

Teaching Scrum in Cooperation with a Software Development CompanyThe increasing use of agile methods for software development creates the need for these methods to become part of the education of future computer and information science engineers. On the other hand, teaching these methods gives us an opportunity to verify individual agile concepts and their effectiveness. For that reason, project work is an appropriate and frequently used form of teaching that enables students to get acquainted with agile methods and, at the same time, provides case studies for evaluating individual agile concepts. We describe our approach to teaching the Scrum agile method, within the software technology course, in cooperation with a software development company. Students were taught through work on a real project for which a list of requirements was submitted by the company. A co-worker of this company participated throughout the teaching period playing the role of customer's representative. During their work, students consistently used the Scrum method and at the end of each iteration they evaluated their experience by means of a questionnaire. In the article, the Scrum method is presented first, then a description of work on the project is given and finally the results of the survey are described.

Стилі APA, Harvard, Vancouver, ISO та ін.

30

Wohllebe, Atilla, and Michael Götz. "Communities of Practice for Functional Learning in Agile Contexts: Definition Approach and Call for Research." International Journal of Advanced Corporate Learning (iJAC) 14, no. 1 (June 29, 2021): 62. http://dx.doi.org/10.3991/ijac.v14i1.21939.

Повний текст джерела

Анотація:

With the increasing relevance of information technology and software development in particular, the popularity of agile working methods like Scrum and Kanban has grown significantly in recent years. Characteristic for many agile frameworks like Scrum is the work in cross-functional teams. While this has many advantages in development, cross-functional teams make functional learning very challenging. Therefore, so-called Communities of Practice (CoPs) have been established in practice. This paper defines CoPs in the agile context and reviews existing literature on CoPs in agile context. There is very little literature how CoPs in the agile context are employed to enhance functional learning. The author calls for more scientific research for example on CoP’s success factors and contribution to functional learning outcomes in agile environments.

Стилі APA, Harvard, Vancouver, ISO та ін.

31

Vega, Florencia, Guillermo Rodríguez, Fabio Rocha, and Rodrigo Pereira dos Santos. "Scrum Watch: a tool for monitoring the performance of Scrum-based work teams." JUCS - Journal of Universal Computer Science 28, no. 1 (January 28, 2022): 98–117. http://dx.doi.org/10.3897/jucs.67593.

Повний текст джерела

Анотація:

Agile Methods propose an approach for developing software based on an iterative and incremental life cycle model, in which needs and solutions evolve through collaboration between multi-functional and self-organized teams. As such, agile practices in work teams are gaining much momentum. To meet the demanding level of projects, agile software development also has to keep up with several challenges. In this context, software industry has chosen to use several tools to ease development and communication between different teams’ members. However, these tools generate overwhelming volumes of data that hamper decision-making by project managers. To address this issue, we present Scrum Watch, a tool-based approach that focuses on generating, through cloud-based technologies, graphic elements and reports that assist project managers with information to support decision making. Results obtained from an undergraduate Systems Engineering course through a capstone project confirm the feasibility of the proposed approach, which exploits the benefits of the availability and visualization of process and product metrics.

Стилі APA, Harvard, Vancouver, ISO та ін.

32

Esteki, Mohammad, Taghi Javdani Gandomani, and Hadi Khosravi Farsani. "A risk management framework for distributed scrum using PRINCE2 methodology." Bulletin of Electrical Engineering and Informatics 9, no. 3 (June 1, 2020): 1299–310. http://dx.doi.org/10.11591/eei.v9i3.1905.

Повний текст джерела

Анотація:

The distributed Agile development approach has been accepted by software companies due to its promised benefits. However, due to the controversial nature of distributed and Agile development, significant challenges arise from spatial, temporal, social, and cultural differences between distributed teams. Scrum, as the most popular Agile methodology, assumes that team members work together in the same room. But this principle does not apply in a realistic scenario where Scrum teams are distributed in different locations. Hence, proposing a risk management framework is necessary in order to succeed such teams. The purpose of this research was to propose a risk management framework in Scrum using the PRINCE2 methodology, which includes the perceived risks in distributed Scrum projects and their causes and roots for managing these risks. By embedding distributed Scrum in delivery layer of PRINCE2 and considering perceived risk factors, along with a hybrid model, a risk management framework was suggested. This framework has been used in a case study, and the results showed its proper functionality in detecting and eliminating potential risks in the case under study. Also, using this framework led to higher team efficiency in terms of increasing the number of completed user stories in each sprint.

Стилі APA, Harvard, Vancouver, ISO та ін.

33

Ilyés, Enikő. "Teaching agile operation and leadership through linked university courses." Teaching Mathematics and Computer Science 20, no. 1 (September 13, 2022): 1–32. http://dx.doi.org/10.5485/tmcs.2022.0534.

Повний текст джерела

Анотація:

Agile software development methods, especially Scrum, are commonly used in software development companies. For this reason, our goal was that our undergraduate students gain experience as Scrum development team members and our master's students as agile leaders. To this end, we had redesigned and linked an undergraduate and a master's course, and launched the new course in the spring of 2021. The success of our approach was confirmed by a questionnaire survey of 86 undergraduate and 27 master's students. A/B testing was also performed. Our approach is a novelty compared to solutions where the Scrum Master is a course member, an instructor, or a university employee. In addition to being resource-efficient, it also offers master's students an unparalleled opportunity to develop agile leadership skills. Subject Classification: 97U50

Стилі APA, Harvard, Vancouver, ISO та ін.

34

Pardo Calvache, César Jesús, Piedad Rocío Chilito Gomez, Daniel Esteban Viveros Meneses, and Francisco José Pino Correa. "Scrum+: A scaled Scrum for the agile global software development project management with multiple models." Revista Facultad de Ingeniería Universidad de Antioquia, no. 93 (August 23, 2019): 105–16. http://dx.doi.org/10.17533//udea.redin.20190519.

Повний текст джерела

Анотація:

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

Стилі APA, Harvard, Vancouver, ISO та ін.

35

Thiele, H., S. Weber, J. Reichwein, J. A. Bartolo, Y. Tchana, L. Jimenez, and J. C. Borg. "A SCRUM AGILE INTEGRATED DEVELOPMENT FRAMEWORK." Proceedings of the Design Society: DESIGN Conference 1 (May 2020): 747–56. http://dx.doi.org/10.1017/dsd.2020.9.

Повний текст джерела

Анотація:

AbstractWith design methodologies, as Integrated Product Development, industry is continuously looking to improve their product development processes. Staying ahead concurrence forces them to deliver new and more complex products in shorter time. When it comes to fast delivery and requirement changes, product development can be inspired by agile methods. Although the application is difficult, the idea to implement these methods for development of products other than software comes out. To ease its implementation, this paper proposes to use IPD as a framework for agile product development.

Стилі APA, Harvard, Vancouver, ISO та ін.

36

Povna, Svitlana. "СВІТОВИЙ ДОСВІД ЗАПРОВАДЖЕННЯ ГНУЧКИХ МЕТОДОЛОГІЙ УПРАВЛІННЯ КОНКУРЕНТОСПРОМОЖНІСТЮ ПІДПРИЄМСТВ ТА ОРГАНІЗАЦІЙ". PROBLEMS AND PROSPECTS OF ECONOMIC AND MANAGEMENT, № 1(21) (2020): 63–71. http://dx.doi.org/10.25140/2411-5215-2020-1(21)-63-71.

Повний текст джерела

Анотація:

The article explores the features of flexible management methodologies, among which Kaizen and Agile are highlighted. These methodologies are designed to work in changing market conditions and customer requirements. It is noted that all these methodologies are focused on the evolutionary development of organizations, thus gradual improvements that ultimately maintain the competitiveness of organizations at a high level. The components of Kaizen and Agile are highlighted and their basic principles are compared. It is noted that Kaizen has become the source for some Agile techniques. An analysis of the implementation of the Agile methodology in the world was carried out, which showed the spread of its influence in the global world. The advantages of adopting Agile that companies implemented flexible technology receive are primarily the ability to manage changing priorities, the visibility of the project, aligning business with IT, and team morale. However, there are many problems with the implementation of this methodology; one of the main is the organizational culture that does not contribute to change and communication. However, some Agile methods, such as Scrum, have fairly clear implementation rules that must be introduced in their entirety, and they must be fully followed. The problems of Scrum introduction are mainly connected with insufficient adherence to the Scrum process, which eliminates its advantages. The Agile methodology helps organizations grow larger than the critical size for such organizations.

Стилі APA, Harvard, Vancouver, ISO та ін.

37

Mayor, Jesus, and Daniel López-Fernández. "Scrum VR: Virtual Reality Serious Video Game to Learn Scrum." Applied Sciences 11, no. 19 (September 28, 2021): 9015. http://dx.doi.org/10.3390/app11199015.

Повний текст джерела

Анотація:

Education is crucial for the growth of society, and the usage of effective learning methods is key to transmit knowledge to young students. Some initiatives present Virtual Reality technologies as a promising medium to provide active, effective, and innovative teaching. In turn, the use of this technology seems to be very attractive to students, making it possible to acquire knowledge through it. On the other hand, agile methodologies have taken an essential role within information technologies and they are key in Software Engineering education. This paper combines both areas and presents prior research about Virtual Reality experiences with educational purposes and introduces a serious VR video game that aims to promote the learning of agile methodologies in Software Engineering education, specifically the Scrum methodology. This application tries to bring students closer to their first days of work within a software development team that uses the Scrum methodology. Two evaluation processes performed with university teachers and students indicate that the developed video game meets the proposed objectives and looks promising.

Стилі APA, Harvard, Vancouver, ISO та ін.

38

Peterson, Matthew, and Joshua Summers. "WHEN WORLDS COLLIDE – A COMPARATIVE ANALYSIS OF ISSUES IMPEDING ADOPTION OF AGILE FOR HARDWARE." Proceedings of the Design Society 1 (July 27, 2021): 3451–60. http://dx.doi.org/10.1017/pds.2021.606.

Повний текст джерела

Анотація:

AbstractThe objective of this paper is to explore challenges identified for implementation of scrum for hardware development intersect with agile principles found in the literature. A series of comparative analyses are done at the textual level, through logical intersections, and through thematic analysis. It is shown that there are five underlying themes found across two sets of scrum challenges (constraints of physicality and the 13 principles). These five themes include: flexiblity, chunkability, scalability, endurability, and teamability. These five themes further are found related to the defining principles of the agile manifesto. Using this understanding, future efforts will include empirical case study work to determine the impact that these have on application of scrum methods and tools. Additionally, guidelines should be developed to help hardware product engineers in applying scrum.

Стилі APA, Harvard, Vancouver, ISO та ін.

39

Newmark, Richard I., Gabe Dickey, and William E. Wilcox. "Agility in Audit: Could Scrum Improve the Audit Process?" Current Issues in Auditing 12, no. 1 (March 1, 2018): A18—A28. http://dx.doi.org/10.2308/ciia-52148.

Повний текст джерела

Анотація:

SUMMARY Changes in environmental forces provide an opportunity for audit firms to move away from an up front and reactive audit planning approach to one that is more agile. Agility involves quicker adaption to the external and internal environments and can result in improved operating performance, quality, and client satisfaction. One way to introduce agility in a project-based organization is to adopt Scrum, an agile project management approach that has been applied in other industries to allow organizational teams to review, reflect, learn, and adapt. This “inspect-and-adapt” philosophy inherent in Scrum enables teams to effectively work in ever-changing conditions, resulting in a high level of sustainable productivity. We provide an overview of key Scrum principles and concepts and address future areas for Scrum research.

Стилі APA, Harvard, Vancouver, ISO та ін.

40

Rachmadini, Fernanda, and Sugeng Santoso. "Peran Project Owner dalam Menjalankan Agile Project Management (Studi Kasus: PT. XYZ)." Jurnal Manajemen dan Organisasi 12, no. 3 (November 12, 2021): 166–76. http://dx.doi.org/10.29244/jmo.v12i3.33326.

Повний текст джерела

Анотація:

Agile project management methodologies provide the means to respond to highly dynamic customer needs. One of the agile project management frameworks is scrum. Scrum is shaped in 3 important roles by project owner, scrum master, and development team. The research objective was to determine the roles and responsibilities of the project owner when run several projects at PT. XYZ using the agile project management methodology scrum framework. The research method used is descriptive qualitative, with the investigative method adopted is a single case study, namely the company PT. XYZ which is engaged in IT with several application development projects. The results obtained from the interview are that the role of the project owner must understand the needs desired by customers by being sensitive to customer needs that highlight quality and uncertain changes, besides understanding the scrum team in delivering product services desired by customers in order to provide maximum quality and acceptance by the customer. In addition, the project owner must carry out the responsibilities such as explaining the SoW and the objectives to be achieved in the project, preparing a budget for the project, allocating of development teams who will work on the product, determining the priority of the product backlog and the sprint that will be executed, monitoring each stage sprints that are being worked on by the developer team, holding daily meetings for a maximum of 15 minutes with the scrum team, arranging and holding meetings with customers and the scrum team for each sprint that has been completed, and collaborating with the scrum team to discuss any changes desired by customers.

Стилі APA, Harvard, Vancouver, ISO та ін.

41

Shafiq, Shagufta, Yaser Hafeez, Sadia Ali, Naila Iqbal, and Muhammad Jamal. "Towards Scrum Based Agile Framework for Global Software Development Teams." Mehran University Research Journal of Engineering and Technology 38, no. 4 (October 1, 2019): 979–98. http://dx.doi.org/10.22581/muet1982.1904.11.

Повний текст джерела

Анотація:

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

Стилі APA, Harvard, Vancouver, ISO та ін.

42

Rodrigues, Eliane Lima, and Isabel Cristina Scafuto. "Learning in the transformation of organizations with the implementation of agile methods." Revista de Gestão e Secretariado 13, no. 4 (December 30, 2022): 2514–32. http://dx.doi.org/10.7769/gesec.v13i4.1486.

Повний текст джерела

Анотація:

Objective: This article aims to understand the influence of organizational learning on adaptation during the implementation of agile methods in the project management environment in companies. The study focuses on changing project management processes from the traditional “waterfall” to agile management models to meet the needs of organizations. It aims to identify how the organization based on traditional project management migrates to a new process, adapting the new agile methodology to its day-to-day activities. Design/methodology/approach: We carried out a systematic literature review, answering the question: How does organizational learning influence the adaptation of agile methods? Results: We grouped the articles into five fields of research: Agile Learning; Organizational Learning in the implementation of Lean and Scrum methodologies: Implementation of Lean and Scrum methodologies; Learning of the individual in the organization and Organizational Learning. Originality/Value: This article seeks interests in the potential of applying agile projects and the organizational learning acquired from this new model.

Стилі APA, Harvard, Vancouver, ISO та ін.

43

Almeida, Fernando, Diogo Adão, and Catarina Martins. "Decision Support System for Assigning Members to Agile Teams." International Journal of Information Technologies and Systems Approach 12, no. 2 (July 2019): 43–60. http://dx.doi.org/10.4018/ijitsa.2019070103.

Повний текст джерела

Анотація:

The use of agile methodologies like SCRUM is seen by companies in the software engineering field as a strategic necessity for their competitiveness, which makes them more reactive and dynamic in an increasingly demanding and competitive international market. One of the critical factors in the implementation of a SCRUM environment is the set-up of teams that are simultaneously homogeneous and composed of the best collaborators for each SCRUM role. In this sense, this study describes the modeling process and presents the implementation of a decision support system that can contribute to improving the process of assigning an agile team simultaneously considering the technical and social skills of employees. The results of the study allowed testing the application considering different competencies associated to each Agile position, the impact that the attribution process suffers from oscillations in the process of evaluation and self-evaluation, and the impact in terms of the performance of the inclusion of new collaborators and criteria comparison.

Стилі APA, Harvard, Vancouver, ISO та ін.

44

Sophatsathit, Nalinee. "A Social Network Scrum Framework for Software Development under COVID-19 Pandemic." International Journal of Innovative Technology and Exploring Engineering 10, no. 4 (February 28, 2021): 172–77. http://dx.doi.org/10.35940/ijitee.d8544.0210421.

Повний текст джерела

Анотація:

This research proposes a framework for social network scrum meeting that serves as an alternate means for work continuation under the COVID-19 pandemic. Conventional agile and scrum methods that require in-person meeting on daily basis, as well as scrum process become impractical under stringent ‘social lockdown’ mandates. To prevent any disruptive discontinuity, the proposed framework sets up an online meeting to replace the in-person stand-up meeting and scrum. Some supporting practices are also established to adjust both agile and scrum event flows that suit this online encounter. They are production development setup and social network meeting. The former offers industrial practices that are well entrenched and proven, while the latter has been used extensively in this digital age. The proposed method is tested with computer science student’s projects. Students are able to continue their meeting, discussion, and some outputs rather than being isolated with no fruitful outcome. The proposed method does establish some ground work to be explored for future software development environments that will suit to the imminent digital technological advancement.

Стилі APA, Harvard, Vancouver, ISO та ін.

45

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.

Повний текст джерела

Анотація:

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.

Стилі APA, Harvard, Vancouver, ISO та ін.

46

Shah, Ashni, Alfonso Huidobro Pereda, and Milene Gonçalves. "Sprinting Out of Stuckness: Overcoming Moments of Stuckness to Support the Creativity Flow in Agile Team Settings." Proceedings of the Design Society: International Conference on Engineering Design 1, no. 1 (July 2019): 2347–56. http://dx.doi.org/10.1017/dsi.2019.241.

Повний текст джерела

Анотація:

AbstractMultidisciplinary agile teams working in fast paced, delivery-oriented sprint cycles of two weeks can experience moments of stuckness. Typically, these moments can be characterised by the inability to continue, which can be quite detrimental in agile settings, where time is pressured. This paper aims to explore these moments of stuckness, to understand when and why they occur and to understand the different strategies Scrum teams use to overcome them, both on a personal as well as team level. A combination of interviews and observations were conducted with six Scrum team members and two experts to understand their process and experiences while working in an agile set up. We have identified five strategies, which strongly rely on agile values of collaboration, communication, and creativity. These are: looking for expert guidance, open communication, creating spike stories, visual communication and incubation. The findings from this study provide both practice and academia with a deeper understanding into how can creativity be supported in agile settings.

Стилі APA, Harvard, Vancouver, ISO та ін.

47

Marinho, Leonardo Lima, Suelen Regina C. dos Santos, Leonardo Andrade, Bruna Costa Cons, Marcelo Schots, and Vera Maria Werneck. "Scrumie: Scrum Teaching Agent Oriented Game." Revista de Informática Teórica e Aplicada 27, no. 2 (April 27, 2020): 140–52. http://dx.doi.org/10.22456/2175-2745.98203.

Повний текст джерела

Анотація:

The use of agile methods has become essential in software development at the present time. Among the existing methods, Scrum is one of the major ones, and is used to manage projects in companies, even outside of the scope of software systems development. Considering the relevance of this subject and the success usually obtained in learning through educational games, Scrumie was proposed to teach the management of Scrum projects. Scrumie applies intelligence in multiagent architecture being developed with Agile Passi an agent oriented methodology. This paper contains a proposal, modeling, implementation and evaluation of the Scrumie game.

Стилі APA, Harvard, Vancouver, ISO та ін.

48

Aragonés-Jericó, Cristina, and Pedro Canales-Ronda. "AGILE LEARNING IN MARKETING: SCRUM IN HIGHER EDUCATION." Journal of Management and Business Education 5, no. 4 (November 27, 2022): 345–60. http://dx.doi.org/10.35564/jmbe.2022.0020.

Повний текст джерела

Анотація:

The main objective of this article is to show the results of a teaching innovation project that proposes the use of agile methodologies, typical of the business world, to adapt them to teaching. To this end, the agile technique Scrum is applied, a practical and experiential method in which learning by doing is used. Scrum facilitates the development of important skills for the students' future employment (working under pressure, adapting to new situations, teamwork, communication and conflict management). The specific objectives of the project are: 1. To design practical classes based on Scrum. 2. To use digital technologies and resources efficiently. 3. To bring the university and business worlds closer together. 4. To measure the perception of university students after the application of the teaching innovation project. To analyze descriptive results, a survey was carried out among the students who participated in the project, reaching a sample of 425 students (Faculty of Economics, University of Valencia). Most of them have had previous experience with learning-by-doing methodologies and consider them much more useful than the traditional methodology. The aspects they value most highly in the agile methodology are team performance, interactivity and commitment. In addition, the students involved mainly value them as interesting, entertaining, useful and dynamic.

Стилі APA, Harvard, Vancouver, ISO та ін.

49

Kovalchuk, Nataliia, and Kateryna Komarova. "Scrum teams as a tool to use flexible approaches in managing organizations." INNOVATIVE ECONOMY, no. 1-2 (2020): 85–92. http://dx.doi.org/10.37332/2309-1533.2020.1-2.13.

Повний текст джерела

Анотація:

Purpose. The aim of the article is substantiation of expediency of using Scrum methodology in organization of team work of enterprise. Methodology of research. The main principles of enterprise management theories, scientific works of national and foreign scientists on team management became the methodological principles of the research. The following research methods are used to substantiate the importance of incorporating flexible approaches into the enterprise management strategy, namely: abstract and logical (to reveal the theoretical foundations of team formation and development); logical (to identify the advantages and disadvantages of using Scrum commands); economics and mathematics (to build charts using Scrum methodology in industries). Findings. The importance of using teamwork and flexible technologies is substantiated. Characteristics of effective teams, the content of stages of development of teams are determined; the essence of managing the processes of relationships in teams is formulated. The main stages of team development and formation are highlighted. The main advantages and disadvantages of using Agile philosophy in management are considered. Recommendations are developed for Ukrainian companies to increase competitiveness, which consists in forming a corporate culture based on the values of people in the company, cooperation with the customer, readiness for change taking into account the peculiarities of the industry in the decision-making process regarding the implementation of Scrum teams and their adaptation to the needs of business. Originality. The theory of team management has been further developed, including conceptual foundations for the expediency of using flexible forms of organization in enterprise management. Practical value. The obtained results may form the basis of further theoretical and applied research related to the use of Agile philosophy in Ukrainian enterprises and the formation of Scrum teams in various business areas. Key words: Agile philosophy; Scrum master; Scrum team; sprint; team; stages of team development.

Стилі APA, Harvard, Vancouver, ISO та ін.

50

Artyukhov, Artem E., Iurii Iu Volk, and Tetiana A. Vasylieva. "Agile methodology in higher education quality assurance system for SDGs 4, 8 and 9 achievement: national experience." CTE Workshop Proceedings 9 (March 21, 2022): 81–94. http://dx.doi.org/10.55056/cte.105.

Повний текст джерела

Анотація:

This paper is focused on considering agile methodology as an instrument to use in education quality assurance. We propose the Scrum method applicable for education quality assurance based on adapted Manifesto for Agile Education Quality Assurance and twelve principles behind it. The Scrum procedure is described and roles are distributed for two real-life cases of external and internal educational program quality evaluation. We illustrate that proposed Scrum procedure perfectly fits existing practices and can be used to enhance both external and internal quality assurance processes in higher education. We consider achievement of SDG 4 targets through proposed methodology as the necessary step to take in achieving SDGs 8 and 9. It is concluded that stakeholders feedback about their satisfaction by economic and innovative factors should be included in each sprint review procedure in proposed Scrum methodology. We discuss SDG 4 achieving within multilayered DIKW+DM hierarchy as a framework for education quality assurance that allow to join information processing, knowledge acquisition and corresponding decision-making algorithm.

Стилі APA, Harvard, Vancouver, ISO та ін.

Статті в журналах з теми "Agile Scrum"

Оформте джерело за APA, MLA, Chicago, Harvard та іншими стилями