<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Methodology of Building Agile-Education Processes in Higher Education Institutions</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Viktoriia</forename><surname>Mironova</surname></persName>
							<email>vicky.mironova@gmail.com</email>
							<affiliation key="aff0">
								<orgName type="institution">Taras Shevchenko National University of Kyiv</orgName>
								<address>
									<addrLine>Bohdana Havrylyshyna St, 24</addrLine>
									<postCode>04116</postCode>
									<settlement>Kyiv</settlement>
									<country key="UA">Ukraine</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Mykola</forename><surname>Pyroh</surname></persName>
							<email>mykola.pyroh@yahoo.com</email>
							<affiliation key="aff0">
								<orgName type="institution">Taras Shevchenko National University of Kyiv</orgName>
								<address>
									<addrLine>Bohdana Havrylyshyna St, 24</addrLine>
									<postCode>04116</postCode>
									<settlement>Kyiv</settlement>
									<country key="UA">Ukraine</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Iryna</forename><surname>Harko</surname></persName>
							<email>garko.iryna@gmail.com</email>
							<affiliation key="aff0">
								<orgName type="institution">Taras Shevchenko National University of Kyiv</orgName>
								<address>
									<addrLine>Bohdana Havrylyshyna St, 24</addrLine>
									<postCode>04116</postCode>
									<settlement>Kyiv</settlement>
									<country key="UA">Ukraine</country>
								</address>
							</affiliation>
							<affiliation key="aff1">
								<orgName type="institution">National Technical University of Ukraine &quot;Igor Sikorsky Kyiv Polytechnic Institute&quot;</orgName>
								<address>
									<addrLine>Politekhnichna St, 41, Academic building № 18</addrLine>
									<postCode>03056</postCode>
									<settlement>Kyiv</settlement>
									<country key="UA">Ukraine</country>
								</address>
							</affiliation>
						</author>
						<author>
							<affiliation key="aff2">
								<orgName type="department">Information Technology and Interactions</orgName>
								<address>
									<addrLine>2-3 December</addrLine>
									<postCode>2020</postCode>
									<settlement>Kyiv</settlement>
									<country key="UA">Ukraine</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Methodology of Building Agile-Education Processes in Higher Education Institutions</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">E965F962724F68D9E3E4D5D8A2956C02</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T09:05+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>agile-methodology</term>
					<term>scrum</term>
					<term>education</term>
					<term>Information Technology</term>
					<term>training of specialists</term>
					<term>professional training</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>In this paper the technology of using the popular flexible software development methodology agileis considered for the development and construction of courses and semantic links of higher education disciplines for training specialists in the field of information technology.</p><p>The authors analyze the basic principles of the Agile-Manifest and their application for the formation of the curriculum program and the students' training disciplines. The presented article considers the result the flexible agile software development methodology implementation into the process of higher education students teaching. We present approaches to the educational process modernization, educational and methodological support development and approaches to teaching in high school on the example of the discipline "Web technologies and site programming" for students in specialty 122 Computer Science in educational program "Applied Programming". The article describes the results of several years gradual adaptation of Agile technology to the learning process, its introduction into the learning process and the results of the developed methodology approbation. The theoretical bases and advantages of Agile-methodology over the classical scheme of training, which we define as "direct" or "cascade", are considered. In order to effectively study the impact of flexible methodologies on the educational process, approaches to the formation of experimental and control academic students groups are presented. The dynamics of laboratory work timeliness and comparison of the academic groups final results are given. The influence of Agile-methodology on the academic groups success is considered and a statistical comparison with the classical approach to teaching is made. Also, we determined the directions of further research on the topic of Agile-methodology implementation in the educational process taking into account the urgency of the education transformation issue in Ukraine and professional training of specialists in the field of information technology.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">Introduction</head><p>Training of specialists in the field of information technologies requires the formation of educational programs and courses using modern technologies, programming languages, libraries and frameworks. However, the rapid growth and changing trends in the IT sector makes it impossible to create such a program even for four years of bachelor's degree <ref type="bibr" target="#b0">[1]</ref>. That is, even if at the beginning of the educational cycle, the program was designed taking into account the most relevant approaches and topics, at the time of graduation, it becomes obsolete. To understand the need to adapt to such changes, it is worth estimating the frequency of programming languages standards updates and releases, which are 1-3 years for Java, 3 years for C ++ and from six months to 3 years in C#. And even more, programming libraries and frameworks are released almost each month.</p><p>To help higher education institutions to adopt their materials and educational programs, we propose the introduction of an adaptive methodology based on Agile methodology <ref type="bibr" target="#b1">[2]</ref>. Such approach should promote the development of future IT professionals' skills, help student to quickly master new material and be flexible at the IT industry fast-paced market <ref type="bibr" target="#b2">[3]</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">Principles of Agile-education processes</head><p>Agile managementan iterative method of planning and managing projects and processes <ref type="bibr" target="#b1">[2]</ref>. Agile management allocates short product development cycles, providing additional updates depending on changing customer needs. In 2001, Kent Beck, Martin Fowler, Dave Thomas, and 14 other leading software practitioners published the Agile Manifesto, which was a brief description of some of the easy software development technique principles. Agile-Manifesto describes the principles of "flexible" methodology of software development and implementation: priority of customer interests, openness to change, system operation at all times, mobile joint teams "customer-developeruser" with a high level of communication. Flexibility and adaptability are that the Agile client outlines the task, sets the direction, and the team thinks how to solve this problem. The team can change the path to the goal and implement the client's plans in any way convenient for them. According to Agile's principles, the client's business goals, his wishes are more important than the initial conditions and documentation. Another difference between Agile and traditional control schemes is the process algorithm. The traditional management model involves a gradual movement from the stage of analysis to the stage of production. Agile consists of cyclically repeating sprints (Sprint), in other words a number of stages of continuous product implementation and adjustment (fig 1 <ref type="figure">.</ref>).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Figure 1: Agile-methodology Scheme</head><p>If we consider the process of training a specialist in higher education in terms of project management, and the specialistas a unique product, the training can be approached from the standpoint of project management and apply to this process all modern and successful project management methodologies. Due to the success of the Agile approach in industry, software design, marketing and business, foreign experts in the field of education have tried to apply similar principles to the field of education, thus forming the Agile Schools Manifesto:</p><p> people and interaction are more important than processes and tools;  significant knowledge is more important than learning;  cooperation with stakeholders is more important than complex negotiations;  readiness for change is more important than following the original plan. 12 agile principles adapted to the school were also formed. The same principles are easy to implement in the field of higher education and training:</p><p>1. Education results through continuous learning of the discipline 2. Divide large chunks of study and materials into smaller and achievable tasks for quicker completion and easier mastering the proper skills 3. Adhere to the decided timeframe for the delivery of a completed tasks and homeworks 4. Students and teacher must frequently collaborate to ensure that the education is going in the correct direction 5. Create a supportive environment to motivate students and encouraging them to get the job done 6. Prefer face-to-face communication over other methods 7. Knowledge of theoretical and practical materials is the primary measure of progress 8. Try to maintain a constant pace of learning 9. Maintain the quality of study by paying attention to technical details 10. Maintain simplicity 11. Promote self-organization in the team 12. Regularly reflect on your performance for continuous improvement EduScrum's <ref type="bibr" target="#b3">[4]</ref> theory and methodology are based on the empirical theory of process management or empiricism. Empiricism states that knowledge comes from experience and decision-making based on knowledge and information. eduScrum uses an iterative, consistent approach to optimizing the achievement of learning objectives and risk control. Three bases support each implementation of empirical process control: transparency, verification and adaptation (fig <ref type="figure">2</ref>).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Figure 2: The Education Empirical Methodology Basis</head><p>Transparency ensures the visibility of essential aspects of the process for those responsible for the outcome. Transparency requires defining these aspects by a common standard, so observers have a common understanding of what is seen. All participants in the process must communicate in one language and understand all definitions.</p><p>Those who do the work and those who accept the work product must have a common definition of "Ready"(DOR -Definition of Ready) and "Done" (DoD -Definition of Done). EduScrum users should frequently check eduScrum artifacts and progress toward learning objectives for unwanted deviations. These inspections are most effective in the case of diligent and systematic performance by both teachers and students in the classroom. If the student (or teacher) determines that one or more aspects of the process threaten to deviate from the defined boundaries and/or the results will be unacceptable, the planning or approach should be adjusted as soon as possible to minimize further deviations. The tools of such adaptation are planning, review of sprints and demonstration of results, personal reflection.</p><p>Considering the rapid changes in the IT market and trends in demand for programming languages we propose new Agile methodology of building educational programs in higher education institutions. This methodology is built in concept of branched scheme based on the principles of flexible methodology (fig. The difference of this approach comparing to classical cascade educational scheme is the abandonment of the usual transition from the previous to the next work by dividing each topic into differential tasks. This allow students to perform tasks clearly aware of the "degree of immersion" in the topic. Thus, the part "must be done" is a direct task according to the material covered on a particular topic, part "should be done"a complex level of the task that provides additional conditions to the functionality of the program within the passed topic of direct work and previous work, the last part "can be done"a task aimed at the active use of hours set aside for independent work, this includes encouraging students to explore ways to improve the program code, its refactoring and work towards clean code.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Figure 3: MoSCoW prioritization technique</head><p>According to the "Regulations on the organization of the educational process" <ref type="bibr" target="#b4">[6]</ref> for independent work is allocated from 50 to 67 percent of the time allotted for the study of the discipline.</p><p>To effectively use this time, in order to provide quality training for future professionals, we have developed comprehensive tasks aimed not only to deepen students' knowledge, but also to give an understanding of the self-organization of groups during the performance of complex work.</p><p>According to Agile Education, groups of 3 to 5 people are formed to perform a complex task, which distribute roles in the group and build relationships according to the eduScrum methodology. In this context, the teacher has the role of consultant-coordinator, who determines the requirements for the functionality of integrated work, guides student groups in their search for information and helps to develop skills of interaction, mutual assistance and mutual learning of group members.</p><p>Table <ref type="table" target="#tab_0">1</ref> presents a fragment of the work program of the discipline "Web technologies and site programming". According to its structure, according to the developed methodology, the plan of work on a complex task is divided into stages (according to eduScrumsprints), before the first stage students receive tasks and are divided into groups that will work on their complex works. According to the methodology, special meetings are provided to coordinate their actions in the group, where students discuss their work in the group or identify problematic stages.</p><p>According to the Agile methodology, this thematic plan can be presented in the form of product requirements and sprint goals (Table <ref type="table" target="#tab_1">2</ref>). After developing the plan, students begin work on the goals and requirements of the product, which is to break the complex work into small tasks, which are distributed among group members. Students determine the degree of "readiness" of each task, ie what its state is considered to meet the goals of the group and can be defined as satisfactory for integration into the product, and determine the priority of tasks according to the above scheme. The results of such work are usually demonstrated in the form of an Agile board (fig. <ref type="figure" target="#fig_1">4</ref>). During the sprint, each of the tasks performed is moved on the board in the column "In progress", when the task corresponds to DoD, it is moved to the column "Done". According to our plan, the teacher coordinates the activities of student groups during retrospectives, which summarize the work of the group during the stage. In retrospect, students report on the work done, closed tasks, uncompleted tasks, carry over to the next stage tasks from the category "must be done", if they were not completed during the current stage, and answer the theoretical questions. Thus, the presentation of the material encourages students to make efforts to self-development in the influence of external, subjective and objective factors such as:</p><p> changes in the academic schedule.  changes in teaching methods and tools.</p><p> the need to turn to another technology.  the need to review the functionality of the product.  unpredictable changes in the development team. Objectives of the first sprint of the discipline "Web technologies and site programming" according to the Agile methodology Learning objective Key results Master the basic principles of website creation and html structure  We know the basic principles and features of HTML.  We can create a simple web-page using HTML/CSS.  Understand the differences of block and inline tags;  We can create semantic web page and validate it according to W3C standard; Master the methods of creating adaptive web-pages  We know the structure and methods of using the media queries for web-page creation  We understand the purpose of using viewport and its' characteristics  We know the difference between relative and absolute values and positioning  We can create a web-site that will be working on any devices and screens  We understand the differences between adaptive and responsive web-design technologies</p><p>Retrospective is an opportunity for the teacher to understand the needs of each student and student teams, to adapt learning materials to individual perception, to adapt the goals and objectives of subsequent sprints given the speed and quality of knowledge of the material by teams and individual students. In addition, the goals of the sprint and its objectives may change under the influence of external factors: time changes and changes in the schedule; changes in discipline requirements due to changes in the labor market or the irrelevance of technology; changes in teaching methods and tools, etc. The above processes give us a picture of the understanding of learning, which corresponds to the classic scheme of eduScrum <ref type="bibr" target="#b6">[8]</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Agile-education methodology implementation</head><p>Proposed agile-education methodology was used to develop a more adaptive work curriculum of the discipline "Web technologies and site programming" for students majoring in 122 Computer Science educational program "Applied Programming" <ref type="bibr" target="#b5">[7,</ref><ref type="bibr" target="#b6">8]</ref>. Implementing the principles of Agile Education and own developments in the educational process, a method of teaching this discipline was developed, which without violating the structure and educational norms at the Taras Shevchenko National University of Kyiv <ref type="bibr" target="#b4">[6]</ref>. Proposed approach can make the learning process to be more adaptive to changing requirements and each individual group speed of learning and mastering practical skills. This approach to complex tasks was tested by the authors in the 2018/2019 and 2019/2020 academic years. This approach contributes to the interpretation of the usual learning process as a long-term project using Agile-methodology <ref type="bibr" target="#b7">[9]</ref>. However, after two years of testing the methodology, the authors decided to adapt this approach to laboratory work <ref type="bibr" target="#b5">[7,</ref><ref type="bibr" target="#b6">8]</ref>. At the beginning of the article we outlined a certain adaptation of a set of laboratory works to the Agile methodology. Therefore, in the 2019/2020 academic year, it was decided to adapt the methodology of group work for laboratory tasks. In order to assess the effectiveness of the methodology in the full cycle of studying the discipline "Web technologies and site programming" in the presence of two groups (50 students), divided into four subgroups (10-15 students), in the current academic year it was decided to teach two subgroups Agile methodology (experimental groups: EG1, EG2), and twoaccording to established methodologies (control groups: CG1, CG2) (Table <ref type="table" target="#tab_2">3</ref>).</p><p>The discipline "Web technologies and site programming" is studied in the third year in the second semester. The experiment was conducted in the second semester of the 2019/2020 academic year while studying the basics of programming web-sites. That is why, in order to ensure the normal distribution of students into groups according to the level of initial training, the points of their average marks gained during education on the faculty, were used as data. In Agile subgroups (EG1 and EG2) students were divided into groups of 3-4 people working on tasks together. These students received complex tasks, taking into account the teamwork and defended them together, including a package of theoretical questions. In subgroups KG1 and KG2 laboratory work was performed according to the classical "cascade" scheme. According to the results of the exam, the average score of students in all subgroups was calculated (Table <ref type="table" target="#tab_3">4</ref>).</p><p>As you can see, students in the control groups who studied in the traditional format, on average, received 14.18 points less than students in the experimental subgroups. It is also worth noting that the average score of students in the second group is 0.93 higher than that of students in the first group. Similar dynamics is observed in the corresponding control and experimental subgroups: the average score in the experimental subgroup of the first group (EG1) exceeds the average score in the control subgroup of the same group (CG1) by 13.58 points, while for subgroups EG2 and CG2 this difference is 14.78 points. It is also worth noting that students in the second group generally study better and have higher scores. Figures <ref type="figure" target="#fig_3">5,6</ref> show the distribution of final points in the discipline for students of all subgroups. Studying the graphs presented in Figures <ref type="figure" target="#fig_1">2 and 4</ref>, we can see that for the experimental groups the distribution of final scores in the discipline is significantly shifted to the right, in the subgroup EG2 the maximum occurs in the range of 90-100 points. In the control subgroups CG1 and CG2 the percentage of students who received a final grade of "excellent" (90 points and above) -10% and 13.33% respectively, in the experimental subgroups EG1 and EG2 this figure is higher -36.36% and 35.71%, respectively. At the same time, in the experimental subgroups there is no student with a score below 60, and in the control subgroups the percentage of such students is: CG1 -20% and CG2 -13.33%. For a more detailed analysis of the effectiveness of the implementation of Agile-methodology and to identify the features of students' learning in different learning technologies, an equally important indicator was consideredthe timeliness of students' laboratory work. A positive feature of the use of Agile-methodology in experimental subgroups is that students within microgroups (3-4 people) had a motivational influence on each other, which prompted them to perform all tasks with deadlines, which was reflected in the dynamics of timeliness of their laboratory works (Fig. <ref type="figure" target="#fig_4">7</ref>).</p><p>Thus, we see that the percentage of students who performed laboratory work on time in the experimental subgroups ranges from 79-90%, while this figure for the control subgroups remained at 54-62%. In addition, in the control subgroups there was a violation of the deadlines for laboratory work for 3 or more weeks in 19-20% of students, in contrast to 2-5% in the experimental subgroups (Table <ref type="table" target="#tab_4">5</ref>). According to the results of the study, we can state that Agile-groups submitted materials with better compliance with deadlines, and group work encouraged students to help each other in the studied theories, which was a condition for successful delivery of laboratory work.  </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">Conclusions</head><p>The introduction of flexible methodologies in the educational process optimizes approaches in the training of future IT professionals. The implementations of the flexible methodology of software development -Agilein the process of development of educational and methodical support and the proposed approaches in teaching in higher education contribute not only to better understanding and mastering by students of theoretical and practical educational material.</p><p>This approach also helps students understand the production processes in IT projects that are set up according to the Agile methodology, set themselves to work within Scrum, gives an initial idea of the complexity of the task, mandatory and additional product requirementstheir knowledge of the discipline. Agile and Scrum methodologies allow to develop and implement a modern, adapted to the requirements of the labor market training program for IT professionals and helps to develop skills to find the necessary information and interact with peers, which will also help further training and improve their "soft skills". The introduction of Agile-methodology in the educational process radically changes the attitude of students to learning and stimulates their systematic educational work, which in turn affects the quality of work and compliance with deadlines. This allows for a more objective and differentiated assessment of student performance and develops opportunities for a personal-activity approach to learning. We are convinced that the introduction of flexible methodologies in the educational process of training students in technical specialties should become an integral part of the transformation of higher education.</p><p>In addition to the above, the proposed approach is more successfully combined with distance learning, which is dictated to us by the realities of today. With the beginning of the quarantine period of COVID-19 in higher educational institutions of Ukraine, the authors adapted the developed approach to the online mode of conducting lectures and practical classes. Maps have been developed to study the entire discipline and connections of each module, so that students in isolation, even without constant Internet access, can go independently on the map of the module and occasionally adjust their work according to the requirements of the team and the teacher. Agile-methodology of studying disciplines in distance format will be developed in further research and presented together with the results of the proposed adaptation to distance learning in the following articles. </p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head></head><label></label><figDesc>3.) of software development "must do, should do, could do" [5].</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Figure 4 :</head><label>4</label><figDesc>Figure 4: A fragment of the Agile-Sprint discipline board</figDesc><graphic coords="6,91.10,179.19,412.72,196.20" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Figure 5 :</head><label>5</label><figDesc>Figure 5: Distribution of final points in the discipline for students of the first group by subgroups</figDesc><graphic coords="7,72.00,360.95,449.95,211.10" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_3"><head>Figure 6 :</head><label>6</label><figDesc>Figure 6: Distribution of final points in the discipline for students of the second group by subgroups</figDesc><graphic coords="8,72.20,72.00,450.60,219.60" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_4"><head>Figure 7 :</head><label>7</label><figDesc>Figure 7: Dynamics of timeliness of laboratory work for students of all subgroups</figDesc><graphic coords="9,72.00,135.24,450.10,275.38" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0"><head></head><label></label><figDesc></figDesc><graphic coords="2,72.00,382.71,450.75,173.40" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0"><head></head><label></label><figDesc></figDesc><graphic coords="4,72.00,185.84,451.10,200.39" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head>Table 1 .</head><label>1</label><figDesc>Fragment of the table of the discipline "Web technologies and site programming" thematic plan</figDesc><table><row><cell>Topic Number and Title</cell><cell></cell><cell>Hours</cell><cell></cell></row><row><cell></cell><cell>Lectures</cell><cell>Practical</cell><cell>Home</cell></row><row><cell></cell><cell></cell><cell>works</cell><cell>works</cell></row><row><cell>Basics of HTML/CSS. Information content and</cell><cell>4</cell><cell>6</cell><cell>10</cell></row><row><cell>structure of the Web-site</cell><cell></cell><cell></cell><cell></cell></row><row><cell>Adaptive and Responsive Web Design. Media Queries</cell><cell>2</cell><cell>2</cell><cell>10</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_1"><head>Table 2 .</head><label>2</label><figDesc></figDesc><table /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_2"><head>Table 3 .</head><label>3</label><figDesc>Distribution</figDesc><table><row><cell>of students by groups</cell><cell></cell><cell></cell><cell></cell></row><row><cell cols="2">Control group (CG)</cell><cell>Experimental group (EG)</cell><cell>Total</cell></row><row><cell>First Group</cell><cell>10</cell><cell>11</cell><cell>21</cell></row><row><cell>Second Group</cell><cell>15</cell><cell>14</cell><cell>29</cell></row><row><cell>Total</cell><cell>25</cell><cell>25</cell><cell>50</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_3"><head>Table 4 .</head><label>4</label><figDesc>Average</figDesc><table><row><cell cols="2">score of students by groups</cell><cell></cell><cell></cell></row><row><cell></cell><cell>Control group (CG)</cell><cell>Experimental group (EG1)</cell><cell>Total</cell></row><row><cell>First Group</cell><cell>69.6</cell><cell>83.18</cell><cell>76.39</cell></row><row><cell>Second Group</cell><cell>69.93</cell><cell>84.71</cell><cell>77.32</cell></row><row><cell>Total</cell><cell>69.77</cell><cell>83.95</cell><cell>76.86</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_4"><head>Table 5 .</head><label>5</label><figDesc>Dynamics</figDesc><table><row><cell>of laboratory work timeliness by groups</cell><cell></cell><cell></cell><cell></cell><cell></cell></row><row><cell></cell><cell>CG1</cell><cell>EG1</cell><cell>CG2</cell><cell>EG2</cell></row><row><cell>Timely execution</cell><cell>54%</cell><cell>79%</cell><cell>62%</cell><cell>90%</cell></row><row><cell>Deadline violation -1 week</cell><cell>14%</cell><cell>12%</cell><cell>11%</cell><cell>6%</cell></row><row><cell>Deadline violation -2 weeks</cell><cell>11%</cell><cell>5%</cell><cell>9%</cell><cell>3%</cell></row><row><cell>Deadline violation -3 weeks</cell><cell>12%</cell><cell>1%</cell><cell>9%</cell><cell>1%</cell></row><row><cell>Deadline violation -more than 3 weeks</cell><cell>8%</cell><cell>4%</cell><cell>10%</cell><cell>1%</cell></row></table></figure>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Ukrainian higher education is dead. Stay away from it</title>
		<author>
			<persName><forename type="first">D</forename><surname>Semyonov</surname></persName>
		</author>
		<ptr target="https://cutt.ly/Mymj2R5" />
	</analytic>
	<monogr>
		<title level="j">Medium</title>
		<imprint>
			<date type="published" when="2016">2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<monogr>
		<ptr target="https://cutt.ly/SyEftwh" />
		<title level="m">Agile-software development manifesto</title>
				<imprint>
			<date type="published" when="2001">2001</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Modern educational policy will cause a lack of IT specialists</title>
		<author>
			<persName><forename type="first">V</forename><surname>Seminozhenko</surname></persName>
		</author>
		<ptr target="https://cutt.ly/Jymzx4M" />
	</analytic>
	<monogr>
		<title level="j">Euro Education</title>
		<imprint>
			<date type="published" when="2014">2014</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<title level="m" type="main">Agile Methodologies in Education: A Review. In Agile and Lean Concepts for Teaching and Learning</title>
		<author>
			<persName><forename type="first">P</forename><surname>Salza</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Musmarra</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Ferrucci</surname></persName>
		</author>
		<ptr target="https://cutt.ly/Niu2nzk" />
		<imprint>
			<date type="published" when="2019">2019</date>
			<publisher>Springer</publisher>
			<biblScope unit="page" from="25" to="45" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<monogr>
		<ptr target="https://cutt.ly/5yEhQf6" />
		<title level="m">Regulations on the organization of the educational process at the Taras Shevchenko National University of Kyiv</title>
				<imprint>
			<date type="published" when="2018">2018</date>
		</imprint>
		<respStmt>
			<orgName>Taras Shevchenko National University of Kyiv</orgName>
		</respStmt>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">AGILE methodology in education as the main tool for building modern educational disciplines of higher education</title>
		<author>
			<persName><forename type="first">V</forename><surname>Mironova</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Pyroh</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Economics and Management</title>
		<imprint>
			<biblScope unit="issue">76</biblScope>
			<biblScope unit="page" from="124" to="130" />
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Agile-methodology and informatization of the educational process on the example of project work in the discipline &quot;Algorithmization and basics of programming</title>
		<author>
			<persName><forename type="first">V</forename><surname>Mironova</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Pyroh</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Harko</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">VII International. scientific and technical conf. Problems of informatization</title>
				<meeting><address><addrLine>Cherkasy</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2019">2019</date>
			<biblScope unit="page">30</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Evaluating Agile Principles in Active and Cooperative Learning</title>
		<author>
			<persName><forename type="first">J</forename><surname>Stewart</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Decusatis</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Kidder</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Massi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Anne</surname></persName>
		</author>
		<ptr target="https://cutt.ly/piuBBUI" />
	</analytic>
	<monogr>
		<title level="m">Student-Faculty Research Day</title>
				<meeting><address><addrLine>P. B3</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2009">2009</date>
		</imprint>
		<respStmt>
			<orgName>CSIS, Pace University</orgName>
		</respStmt>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
