<?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">Development of an algorithm for selecting the optimal set of tools and techniques for Agile project management in industry and engineering</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">V</forename><forename type="middle">V</forename><surname>Andreev</surname></persName>
							<email>vyach.andreev@mail.ru</email>
							<affiliation key="aff0">
								<orgName type="institution">Nizhny Novgorod State Technical University n.a. R.E. Alekseev</orgName>
								<address>
									<settlement>Nizhny Novgorod</settlement>
									<country key="RU">Russia</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">S</forename><forename type="middle">N</forename><surname>Malozemov</surname></persName>
							<email>malozemovsage@mail.ru</email>
							<affiliation key="aff0">
								<orgName type="institution">Nizhny Novgorod State Technical University n.a. R.E. Alekseev</orgName>
								<address>
									<settlement>Nizhny Novgorod</settlement>
									<country key="RU">Russia</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Development of an algorithm for selecting the optimal set of tools and techniques for Agile project management in industry and engineering</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">3A2093FB5EDC8D76327EE2BA6677414D</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T01:46+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>decision-making algorithm</term>
					<term>system analysis</term>
					<term>project</term>
					<term>Agile management</term>
					<term>risk</term>
					<term>management tools</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Continuous development and the increase of the safety requirements in the field of engineering and industry, as well as the need to comply with the planned timing and costs of the projects require the use of modern approaches to the management of complex engineering systems and their interaction. To achieve the optimal balance between the deadlines and the resources expended, a project approach is used in world practice. One of the new methods of the project approach is Agile management. The use of Agile project management in industry and engineering requires a systematic adaptation of implementation approaches, taking into account internal requirements, risks and organizational characteristics, and is due to the high complexity of decision-making. The paper considers an approach to the formation of a generalized algorithm for the optimal set of tools selection for Agile project management in industry and engineering based on system analysis methods. This algorithm is designed to provide decision support for the selection of the most suitable tools and techniques for Agile project management with a view to their successful implementation.</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>Successful implementation of projects is largely due to competent, modern management. Today, there are many methods and approaches to project management. One of these approaches is Agile, which has proven itself in IT projects and in the banking sector. The first results of applying Agile approach in industry and engineering showed that using Agile similar to IT projects is impractical due to the different specifics of the activity and the impossibility of using a number of tools and techniques. When introducing this method in engineering and industry, it becomes difficult to select the optimal set of Agile tools and techniques. The problem is due to the large number of possible options and the lack of experience in the application of Agile project management in this area. To determine the tools and techniques of Agile, we need a mathematical method to optimize the decision-making process for selecting a set of tools and techniques.</p><p>The purpose is to determine the function and develop an algorithm for the optimal set of Agile management tools selections for a specific project.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">Correlation of sets of risks and tools</head><p>Based on the existing experience of using Agile in various projects, we define many basic Agile tools and techniques, forming them into a specific data table with a description (table <ref type="table" target="#tab_0">1</ref>).  Changing customer requirements in the later stages of the project 4 Conflicts within the team 5 Implicit dependencies with other projects 6 Excessive product complexity 7 The need for unique experts Thus, we get 2 sets of project tools and project risks. To determine the correlation of sets of risks and tools, we apply the Swiss Cheese model and the Bow-tie model. The Swiss Cheese model demonstrates the principle of multilevel protection against possible incidents, the Bow-tie model determines the need to influence both the causes and consequences of events. Agile tools designed to manage the project can serve as preventive measures, monitoring and control tools, remedies for recovery and mitigation. The principle of the correlation of risks and tools is presented in Fig. <ref type="figure" target="#fig_0">1</ref>. The formation of correlation between the elements of sets is carried out by the expert method, based on the experience of using Agile tools, personal professional experience in implementing projects in the selected field, taking into account the characteristics of the organization and the external environment.</p><p>In this correlation, we see that one risk can be blocked by different instruments; one tool can cover different risks. To select specific tools, we introduce expert assessmentsproject criteria: time (team's time spent on using the tool) (t), budget (including additional resources or competencies) (b), team satisfaction level (u). Each criterion is assigned a range of possible weight, taking into account pre-calculated costs <ref type="bibr" target="#b3">[4]</ref><ref type="bibr" target="#b4">[5]</ref><ref type="bibr" target="#b5">[6]</ref><ref type="bibr" target="#b6">[7]</ref>. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Application of system analysis methods</head><p>There are many decision-making methods. Due to the presence of several criteria in the tools and the presence of links between the sets of risks and tools, we will choose the main methods of system analysis, which we will use when selecting the optimal set of tools. For Agile approach, consider a group of descriptive models (that is, simulate human behavior in a decision-making situation).</p><p>Based on what we will build a phased decision-making algorithm. At each stage, depending on the task, we will use the most appropriate method.</p><p>The methods that we will use in the definition of a function are: the matrix method of multicriteria analysis, the logical-linguistic model, the cause-effect model, the method of pairwise comparisons, the axiomatic method. The matrix method of multicriteria analysis allows one to find a balanced estimate through the construction of matrices of values and the importance of alternatives.</p><p>A logical-linguistic model will make it possible to determine the most suitable set of all possible risks from the set of possible tools. In this model, when making a decision, there is no way to consider the importance of the element (risk), which affects the accuracy of the decision.</p><p>With a causal decision-making model, a function is determined with a possible consideration of the importance of the element. With this model, multicriteria analysis involves comparing a number of criteria with possible options, including alternative ones that arise in the process of solving the tasks.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">Decision making algorithm for tools selection</head><p>Define a general decision making algorithm for tools selection. At the first stage, the decision maker (DM) selects the possible risks that may arise during the implementation of the project, and also sets the limit values and factors of importance of the project parameters (time, budget, team satisfaction). We get the source data:</p><p>− preset project parameters (tpp; bpp; upp); − project risk list (set ri); − importance factor (w). Through the selected risks, the tools are determined based on predefined relationships. Get the matrix of M relations (risk -tool) -mri (matrix element showing the presence of communication, possibly in the binary system: 1-connection is, 0-communication is not).</p><p>Each tool consists of three previously defined criteria and (t; b; u). We divide the matrix of connections into three matrices for each of the criteria. We get three matrices with values that have previous relations (risk -tool).</p><p>We use the method of pairwise comparisons to find the smallest values in the first two matrices and the largest values in the third matrix that evaluates the qualitative characteristic -team satisfaction.</p><p>To find a set of tools on each of the matrices, a condition must meet, each risk must be assigned a minimum value (matrix element). We get the column of minimum values in two matrices and the maximum value in the third matrix.</p><p>We use the logical-linguistic decision-making model. We transform the given project parameters into a vector whose starting point is 0 and tends to a point -the given project parameters (xtbu), according to each of the criteria, these will be the points U(t), U(b), U(u). Then get many alternative solutions P (p1, p2, ..., pn), where, for example: p1 = u1 + u2 + u4, p2 = u6 + u9, p3 = u3 + u4 + u7.</p><p>Next, we check that all the parameters are fulfilled for each of the alternative solutions found and find the optimal solution. We will use the causal decision-making model. The criteria c (c1 = t, c2 = b, c3 = u) were determined in advance, we introduce the correction factor (cr1 = 1, cr2 = 1, cr3 = -1) for the convenience of comparison, Wimportance of the element (w1, w2, w3). Now, for each of the alternatives, we make a separate assessment for the entire range of criteria х (хt, xb, xu)table <ref type="table" target="#tab_2">3</ref>. Thus, the most appropriate solutions рj will be determined through the function:</p><p>𝑅𝑅 = 𝐹𝐹(𝑋𝑋, 𝑊𝑊), (1) where X is the vector of values хсj (хtj, xbj, xuj), crcorrection factor, W -element importance, F -value convolution function.</p><p>For the most balanced assessment, we can consider the sum of the products of the criterion and importance:</p><formula xml:id="formula_0">𝑅𝑅 = � 𝑝𝑝(𝑥𝑥 𝑐𝑐𝑐𝑐 • 𝑤𝑤 𝑐𝑐 ) 𝑛𝑛 𝑐𝑐=1 .</formula><p>(</p><formula xml:id="formula_1">)<label>2</label></formula><p>When finding the smallest number of alternative solutions (satisfying the given parameters), we check their fulfillment of the conditions without taking into account the correction factor:</p><formula xml:id="formula_2">𝑝𝑝 𝑐𝑐 (𝑡𝑡 𝑐𝑐 , 𝑏𝑏 𝑐𝑐 , 𝑢𝑢 𝑐𝑐 ) ≤ 𝑝𝑝 𝑐𝑐 (𝑡𝑡 𝑝𝑝𝑝𝑝 , 𝑏𝑏 𝑝𝑝𝑝𝑝 , 𝑢𝑢 𝑝𝑝𝑝𝑝 ).<label>(3)</label></formula><p>That is, some solution R must satisfy the conditions: the values of t and b -should be no more than the specified project parameters and the minimum possible, and the value u -no less than the specified project parameter and the maximum possible.</p><p>We use the axiomatic method to identify the correct solution.</p><p>𝑋𝑋�𝑡𝑡 𝑝𝑝𝑝𝑝 ; 𝑏𝑏 𝑝𝑝𝑝𝑝 ; 𝑢𝑢 𝑝𝑝𝑝𝑝 � ≥ 𝑝𝑝(𝑡𝑡; 𝑏𝑏; 𝑢𝑢), 𝑝𝑝(𝑡𝑡; 𝑏𝑏; 𝑢𝑢) = ∑ 𝑈𝑈 𝑐𝑐 (𝑡𝑡; 𝑏𝑏; 𝑢𝑢) 𝑛𝑛 𝑐𝑐=1</p><p>, Х(tpp;bpp;upp) -set parameters, i -tool serial number.</p><p>𝑝𝑝(𝑡𝑡; 𝑏𝑏; 𝑢𝑢)</p><formula xml:id="formula_3">= ⎩ ⎪ ⎪ ⎪ ⎨ ⎪ ⎪ ⎪ ⎧ � 𝑈𝑈(𝑡𝑡) ≤ 𝑥𝑥�𝑡𝑡 𝑝𝑝𝑝𝑝 � 𝑛𝑛 𝑐𝑐=1 ; � 𝑈𝑈(𝑏𝑏) ≤ 𝑥𝑥�𝑏𝑏 𝑝𝑝𝑝𝑝 � 𝑛𝑛 𝑐𝑐=1 ; � 𝑈𝑈(𝑢𝑢) ≤ 𝑥𝑥�𝑢𝑢 𝑝𝑝𝑝𝑝 � 𝑛𝑛 𝑐𝑐=1 . (<label>4</label></formula><formula xml:id="formula_4">)</formula><p>If there are several alternatives, it is possible to use the pairwise comparison method to find the most optimal solution.</p><p>Having found the optimal solution in a list form, it is necessary to ensure the conclusion of a set of tools for a specific project, with a description of each tool and the necessary time, budget and impact on team satisfaction.</p><p>As a result, the DM makes the final decision on the use of these tools and forms a project management plan (management action plan) based on the selected tools. Fig. <ref type="figure">2</ref> shows the general decision making algorithm for selecting tools.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Fig. 2. Decision making algorithm for tools selection</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">Recommendations for using the tool selection algorithm</head><p>As part of the application of this algorithm, the difficult questions will be:</p><p>− initial definition of the scope of application of Agile project management in engineering and industry;</p><p>− determination of the importance of the criterion and its value for qualitative indicators (for example, the impact on team satisfaction) in determining the overall indicator;</p><p>− combination of a formalized algorithm for selecting tools and difficult formalized practical experience of decision makers in the field of project management.</p><p>First, a preliminary analysis of the applicability of Agile to specific projects is needed. For many types of activities (for example, construction and installation works, commissioning) Agile is not applicable. For quick analysis, Agile applicability models (filters) can be used. However, there are currently no filters for projects in the field of industry and engineering. Analytical work is necessary to supplement the existing models of Agile applicability with criteria that are essential for the implementation of projects in the field of industry and engineering. Effective application of the obtained algorithm is possible only in the field of applicability of Agile.</p><p>Secondly, the project team, project stakeholders, and the expert community can be involved in working with criteria of tools. It is necessary to develop a common scale of assessments of tools, considering various points of view. The value of the criteria for each tool must be determined taking into account the specifics of the organization's activities and corporate culture (for example, in one project the "retrospective" tool will be a significant improvement and will positively affect team satisfaction, as in others it will be an obstacle). Multicriteria analysis should be complemented by significant methodological support. Statistics on other projects of companies in this field of activity can also be used.</p><p>Thirdly, it is necessary to provide for the possibility of choosing some Agile management tools, or to adjust the final set based on the decision of the project methodologist. If there is a lot of informal experience in using some Agile tools in a given company, an understanding of the internal corporate culture, a large number of quality criteria and implicit restrictions, various alternative solutions can be evaluated using the presented algorithm. In this case, it will also be useful to use readymade lists of data (risks / tools) of the algorithm. In the absence of significant experience in the company using Agile, the algorithm should be applied in its original form <ref type="bibr" target="#b11">[12]</ref><ref type="bibr" target="#b12">[13]</ref><ref type="bibr" target="#b13">[14]</ref>.</p><p>In addition, when making decisions on tools selection, various kinds of misconceptions are possible. One of the sources of error in decision-making is premature generalization. No matter how universal the tools are, it is impossible to rely on the consideration of criteria on the basis of a perfectly successful project from another field of activity. Also misconception can be attributed to reasoning by analogy. In some cases, not all instruments and risks can be evaluated by analogy in different projects. An example about the "retrospective" tool was described above.</p><p>Based on the decision-making methods used, it is recommended to approach each project individually for the optimal Agile tools selection in industry and engineering. Use the generated algorithm and systematic lists of risks, tools to improve the quality of managerial decision-making. Pay special attention to the methodological work on the formation of criteria and factors of importance for each of them. In some projects, it will be advisable to consider a wider range of alternatives, which will minimize the risks of the project and choose the optimal solution in terms of design parameters.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6.">Conclusions</head><p>The paper investigates the decision-making process when choosing tools for Agile project management. In the framework of this article, the following issues were considered:</p><p>− determining the principle of the Correlation of sets of risks and tools;</p><p>− definitions of the decision-making function for applying the Agile tools;</p><p>− development of an algorithm for the optimal set of Agile tools selection in industry and engineering.</p><p>To determine the function and develop the algorithm, methods of system analysis were used. At the same time, further application of system analysis methods for making multi-criteria decisions in terms of determining the scope of applicability of flexible project management and working with tool criteria also looks perspectively.</p><p>The paper gives recommendations on the application of the obtained algorithm and its further development. Two cases of application are considered:</p><p>− subject to your organization has Agile knowledge and experience in this field;</p><p>− subject to initial application of Agile project management approaches.</p><p>The results obtained can be applied to implement Agile approaches to project management in industry and engineering at the stages of initiation and planning. Using the right Agile tools and techniques can help you achieve your project goals on time and with significant resource savings.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Fig. 1 .</head><label>1</label><figDesc>Fig. 1. The principle of the correlation of risks and tools</figDesc><graphic coords="2,55.40,53.85,484.45,272.05" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0"><head></head><label></label><figDesc></figDesc><graphic coords="3,92.75,422.51,409.75,328.30" 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>Agile tools and techniques examples</figDesc><table><row><cell>№</cell><cell>Tool name</cell></row><row><cell>1 Retrospective</cell><cell></cell></row><row><cell>2 Poker planning</cell><cell></cell></row><row><cell cols="2">3 Work speed estimation</cell></row><row><cell>4 Work in one room</cell><cell></cell></row><row><cell>5 Product backlog</cell><cell></cell></row><row><cell>6 Task board</cell><cell></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>Examples of typical project risks</figDesc><table><row><cell>№</cell><cell>Risk name</cell></row><row><cell cols="2">1 Conflicts of goals and interests between stakeholders</cell></row><row><cell cols="2">2 Delays due to the change of performers</cell></row><row><cell>3</cell><cell></cell></row></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>Decision matrix for each criterion</figDesc><table><row><cell></cell><cell>p1</cell><cell>p2</cell><cell>…</cell><cell>pn</cell><cell>cr</cell><cell>W</cell></row><row><cell>t</cell><cell>xt1</cell><cell>xt2</cell><cell>…</cell><cell>xtn</cell><cell>1</cell><cell>w1</cell></row><row><cell>b</cell><cell>xb1</cell><cell>xb2</cell><cell>…</cell><cell>xbn</cell><cell>1</cell><cell>w2</cell></row><row><cell>u</cell><cell>xu1</cell><cell>xu2</cell><cell>…</cell><cell>xun</cell><cell>-1</cell><cell>w3</cell></row><row><cell></cell><cell>R1</cell><cell>R2</cell><cell>…</cell><cell>Rn</cell><cell></cell><cell></cell></row></table></figure>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Acknowledgments</head><p>The study was supported by the RFBR, grant № 19-07-</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<ptr target=":15." />
		<title level="m">©2020 Agile Alliance</title>
				<imprint>
			<date type="published" when="2020">03.2020</date>
		</imprint>
	</monogr>
	<note>Electronic resource</note>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Project Management Assessment and Development Center</title>
		<ptr target=":15." />
	</analytic>
	<monogr>
		<title level="m">Electronic resource</title>
				<imprint>
			<date type="published" when="2020">03.2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<monogr>
		<ptr target="http://agilerussia.ru/category/methodologies/(dateofaccess17." />
		<title level="m">Electronic resource</title>
				<imprint>
			<date type="published" when="2020">03.2020</date>
		</imprint>
	</monogr>
	<note>Agile Russia</note>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<idno>978-3-0369-5529-2</idno>
		<title level="m">Krogerus Michael Book of solutions. 50 models of strategic thinking / Michael Krogerus</title>
				<imprint>
			<publisher>Olymp-Business</publisher>
			<biblScope unit="page" from="2018" to="2208" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<monogr>
		<ptr target="https://rim-iii.postach.io/(dateofaccess18." />
		<title level="m">Three-level Russian instrumental project management model (RIM-M)</title>
				<imprint>
			<date type="published" when="2020">03.2020</date>
		</imprint>
	</monogr>
	<note>Electronic resource</note>
</biblStruct>

<biblStruct xml:id="b5">
	<monogr>
		<ptr target="http://5informatika.net/(dateofaccess17." />
		<title level="m">Electronic resource</title>
				<imprint>
			<date type="published" when="2020">03.2020</date>
		</imprint>
		<respStmt>
			<orgName>Informatika</orgName>
		</respStmt>
	</monogr>
	<note>Bow-tie Model</note>
</biblStruct>

<biblStruct xml:id="b6">
	<monogr>
		<author>
			<persName><forename type="first">Gost R Iso /</forename><surname>Iec</surname></persName>
		</author>
		<idno>31010</idno>
		<ptr target="http://docs.cntd.ru/document/gost-r-iso-mek-31010-2011(dateofaccess17." />
		<title level="m">-2011 Risk management. Risk assessment methods</title>
				<imprint>
			<date type="published" when="2020-03">2020. 03.2020</date>
		</imprint>
		<respStmt>
			<orgName>Codex JSC</orgName>
		</respStmt>
	</monogr>
	<note>Electronic resource</note>
</biblStruct>

<biblStruct xml:id="b7">
	<monogr>
		<author>
			<persName><forename type="first">V</forename><forename type="middle">V</forename><surname>Podinovsky</surname></persName>
		</author>
		<title level="m">Ideas and methods of the theory of the importance of criteria in multicriteria decisionmaking problems / V.V. Podinovsky -M: Science</title>
				<imprint>
			<biblScope unit="page" from="2019" to="2103" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Analysis of multicriteria management decision-making methods (on the example of the task of selecting suppliers of material and technical resources</title>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">V</forename><surname>Kochkina</surname></persName>
		</author>
		<idno>338</idno>
	</analytic>
	<monogr>
		<title level="j">UDC</title>
		<editor>M.V. Kochkina, A.N. Karamyshev, I.I. Makhmutov, A.G. Isavnin, A.K. Rosenzweig -Naberezhnye Chelny</editor>
		<imprint>
			<biblScope unit="volume">2</biblScope>
			<biblScope unit="page">7</biblScope>
			<publisher>Publishing and Printing Center NCHI K (P) FU</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Adaptation of the ELECTRE family methods for inclusion in the expert decision support system</title>
		<author>
			<persName><forename type="first">T</forename><forename type="middle">K</forename><surname>Kravchenko</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">A</forename><surname>Druzhayev</surname></persName>
		</author>
		<ptr target="http://cyberleninka.ru/article/n/adaptatsiya-metodov-semeystva-electre-dlyavklyucheniya-v-ekspertnuyu-sistemu-podderzhki-prinyatiya-resheniy" />
	</analytic>
	<monogr>
		<title level="m">Electronic resource</title>
				<imprint>
			<publisher>A.A. Druzhayev</publisher>
			<date type="published" when="2015-03-18">2015. 18.03.2020</date>
			<biblScope unit="volume">2</biblScope>
		</imprint>
	</monogr>
	<note type="report_type">Business Informatics</note>
</biblStruct>

<biblStruct xml:id="b10">
	<monogr>
		<title level="m" type="main">System analysis, optimization and decision-making</title>
		<author>
			<persName><forename type="first">V</forename><forename type="middle">N</forename><surname>Kozlov</surname></persName>
		</author>
		<editor>Textbook / V.N. Kozlov. -M.</editor>
		<imprint>
			<date type="published" when="2016">2016</date>
			<biblScope unit="page">173</biblScope>
			<pubPlace>Prospect</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<monogr>
		<title level="m" type="main">System analysis in strategic management</title>
		<author>
			<persName><forename type="first">V</forename><forename type="middle">A</forename><surname>Agafonov</surname></persName>
		</author>
		<editor>Tutorial. / V.A. Agafonov -M: Rusyns</editor>
		<imprint>
			<biblScope unit="page" from="2020" to="2229" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">Mathematical models and decisionmaking in management: A guide for top managers / A</title>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">G</forename><surname>Madera</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">stereotype -M: Lenand</title>
		<title level="s">G. Madera -</title>
		<imprint>
			<date type="published" when="2019">2019</date>
			<biblScope unit="volume">3</biblScope>
			<biblScope unit="page">688</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<monogr>
		<title level="m" type="main">Decision making in fuzzy and blurry data: Fuzzy-technology / Yu</title>
		<author>
			<persName><forename type="first">Yu</forename><forename type="middle">A</forename><surname>Zak</surname></persName>
		</author>
		<editor>A. Zak</editor>
		<imprint>
			<publisher>Lenand</publisher>
			<biblScope unit="volume">2</biblScope>
			<biblScope unit="page" from="2016" to="2352" />
			<pubPlace>M</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">head of the department &quot;Nuclear Reactors and Power Plants</title>
		<author>
			<persName><surname>About</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Vyacheslav</surname></persName>
		</author>
		<author>
			<persName><surname>Andreev</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">graduate student of the department &quot;Nuclear Reactors and Power Plants</title>
		<title level="s">Doctor of Technical Sciences</title>
		<editor>
			<persName><forename type="middle">A R E</forename><surname>Nnstu N</surname></persName>
		</editor>
		<editor>
			<persName><surname>Alekseev</surname></persName>
		</editor>
		<imprint/>
	</monogr>
	<note>malozemovsage@mail</note>
</biblStruct>

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