<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <journal-title-group>
        <journal-title>I. Berezutskyi);</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>IT Project Characteristics Analysis Results Validation⋆</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Ihor Berezutskyi</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Tetyana Honcharenko</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Mykola Tsai</string-name>
          <email>nykolai.tsai@gmail.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Mykola Zdrilko</string-name>
          <email>zdrilko@gmail.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Illia</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Sachenko</string-name>
          <email>sachenko_ia@knuba.edu.ua</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Kyiv National University of Construction and Architecture</institution>
          ,
          <addr-line>31, Air Force Avenue, Kyiv, 03037</addr-line>
          ,
          <country country="UA">Ukraine</country>
        </aff>
      </contrib-group>
      <volume>000</volume>
      <fpage>0</fpage>
      <lpage>0003</lpage>
      <abstract>
        <p>Understanding the factors that contribute to project failure is crucial for enhancing project management strategies. This study investigates the relationship between project characteristics such as methodology selection, team composition, and risk management and project outcomes. A structured online questionnaire was created to collect data, offering broad accessibility and facilitating statistical analysis. The survey, currently in progress, has already yielded initial 50 responses, though the dataset continues to evolve. To ensure methodological rigor, the questionnaire adheres to best practices, including clear and concise questions, a mix of closed and open-ended responses, and a logical structure. The ongoing study aims to identify patterns and correlations that can improve project resilience and success rates. This study underscores the importance of a holistic approach to project management, where multiple factors methodology, team dynamics, stakeholder engagement, and proactive risk management must be carefully balanced to improve project outcomes. As data collection continues, further refinements will enhance these insights, providing more precise recommendations for optimizing project management strategies.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Project Management</kwd>
        <kwd>IT</kwd>
        <kwd>methodological approach</kwd>
        <kwd>complementary</kwd>
        <kwd>contradictory</kwd>
        <kwd>risk forecasting</kwd>
        <kwd>results validation</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>Project management has long been a field of extensive research due to its fundamental role in
ensuring successful project delivery across industries. Despite the evolution of methodologies and
best practices, a significant proportion of projects still fail either by exceeding budgets and
timelines or by not reaching completion. Understanding the underlying factors contributing to
project failure is crucial for refining management strategies, optimizing resource allocation, and
improving overall project success rates.</p>
      <p>One of the key elements influencing project outcomes is the choice of project management
gain valuable insights into improving project resilience. Statistical analysis of past project data
allows researchers and practitioners to identify trends, optimize decision-making, and develop
frameworks that enhance project delivery success. As industries continue to evolve, leveraging
data-driven approaches to understand failure patterns remains imperative for fostering more
robust and efficient project management practices.</p>
      <p>
        Most of the articles [
        <xref ref-type="bibr" rid="ref1 ref2">1-4</xref>
        ] focus on the decision-making aspects necessary for successfully
continuing project development. Some studies [5-8] provide specific implementations of different
methods to sustain projects. However, there is a lack of research analyzing actual project outcomes
through a survey-based approach that can identify patterns for different gaps. Typically, available
studies present lessons learned from individual projects rather than offering an overarching view of
multiple projects. Additionally, no prior research has been conducted to explore the correlation
between using an unsuitable methodology and project failure. Furthermore, there are no studies
that quantify risks by examining whether they were mitigated or escalated into issues existing
literature only provides general discussions on the importance of risk management. This study is
intended to analyze correlations between project failure and different characteristics such as
unsuitable methodology, risk assessment and other. Limitation of the article is self-selected bias
due to specific of a voluntary online survey for only project managers.
      </p>
    </sec>
    <sec id="sec-2">
      <title>2. Type of IT Project analysis method</title>
      <p>To systematically analyze the relationship between project failure and project characteristics, a
questionnaire-based approach has been employed. Questionnaires are a widely recognized research
tool in project management studies, allowing for structured data collection across diverse project
environments. There are several types of questionnaires, including structured, semi-structured, and
unstructured forms. Structured questionnaires use predefined questions with fixed response
options, facilitating quantitative analysis, while semi-structured and unstructured questionnaires
allow for open-ended responses that provide deeper insights.</p>
      <p>For this study, an online structured questionnaire was chosen as the primary data collection
method. This approach offers several advantages, including broader reach due to time saving
answers, ease of participation, and real-time data collection. Online questionnaires reduce
geographical limitations, enabling respondents from various industries and regions to contribute,
which enhances the diversity and reliability of the dataset. Additionally, digital data collection
minimizes manual entry errors and facilitates statistical analysis. To ensure the reliability and
validity of the collected data, best practices in questionnaire design have been implemented. These
include:
•
•
•
•
•
•</p>
      <p>Clear and easy understandable questions: Questions are formulated to be direct and easy to
understand, reducing the risk of misinterpretation by respondents.</p>
      <p>Balanced use of question types: A mix of closed-ended and open-ended questions allows for
both statistical analysis and qualitative insights.</p>
      <p>Logical structure of the questions: The questionnaire follows a structured format, guiding
respondents from general questions to more specific aspects of project management,
ensuring logical progression..</p>
      <p>Limited response options per question: To avoid overwhelming respondents,
multiplechoice questions contain a reasonable number of options while ensuring comprehensive
coverage of possible answers.</p>
      <p>Pretesting and refinement: The questionnaire was pretested with a sample group before full
deployment to identify contradictory and improve clarity.</p>
      <p>Not time consuming: Amount of question limited that allow participant to complete them
in 5-10 minutes without obligation of providing long written explanation on any of the
questions.
•</p>
      <p>Confidentiality: Respondents' privacy is maintained to encourage honest and accurate
responses. Questionnaire does not store or ask for sex, position, country of origin and even
doesn’t store mail address.</p>
      <p>Main and core auditory for this survey are project managers. The survey is currently active, and
initial 50 responses have been gathered. However, data collection remains ongoing, and the dataset
is expected to evolve as more responses are recorded. Composed questions from survey [15] can be
seen in separated tables below.</p>
      <sec id="sec-2-1">
        <title>What caused retention Checkbox</title>
        <p>All team members
where expected
seniority</p>
      </sec>
      <sec id="sec-2-2">
        <title>Question</title>
      </sec>
      <sec id="sec-2-3">
        <title>Which PM methodology was used</title>
      </sec>
      <sec id="sec-2-4">
        <title>Why was this methodology chosen</title>
      </sec>
      <sec id="sec-2-5">
        <title>Methodology was changed during project</title>
      </sec>
      <sec id="sec-2-6">
        <title>Why methodology was changed</title>
      </sec>
      <sec id="sec-2-7">
        <title>Which PM methodology was used after the change</title>
      </sec>
      <sec id="sec-2-8">
        <title>Select</title>
      </sec>
      <sec id="sec-2-9">
        <title>Answer</title>
      </sec>
      <sec id="sec-2-10">
        <title>Checkbox</title>
      </sec>
      <sec id="sec-2-11">
        <title>Checkbox</title>
      </sec>
      <sec id="sec-2-12">
        <title>Select</title>
      </sec>
      <sec id="sec-2-13">
        <title>Checkbox</title>
      </sec>
      <sec id="sec-2-14">
        <title>Select</title>
        <p>(if previous answer
was "Yes") Client;
Performance;
Person related;
Budget related;</p>
        <p>Other</p>
      </sec>
      <sec id="sec-2-15">
        <title>Numeric Value</title>
        <p>What was the final
project outcome</p>
      </sec>
      <sec id="sec-2-16">
        <title>Challenges on the past project were because</title>
      </sec>
      <sec id="sec-2-17">
        <title>To what extent did the PM methodology contribute to the past project deliverables</title>
      </sec>
      <sec id="sec-2-18">
        <title>Question</title>
      </sec>
      <sec id="sec-2-19">
        <title>Did risks stated in the</title>
        <p>start or before start of
the past project
there were some risks
that were converted into
issues</p>
      </sec>
      <sec id="sec-2-20">
        <title>Most common risks that were converted into issues</title>
      </sec>
      <sec id="sec-2-21">
        <title>Most common risks that was mitigated</title>
      </sec>
      <sec id="sec-2-22">
        <title>Monthly; Biweekly; Weekly; Twice per week; Daily</title>
        <p>1; 0</p>
        <p>With information from this survey, after normalization, different parameters can be gathered.
Formulas and calculation for parameters such as overall success ratio, percentage of failed project
due to methodology, the most remediated and not remediated risk and many more different
characteristics are listed below.</p>
        <p>Project failure rate has the following formula:</p>
        <p>Pf =</p>
        <p>N</p>
        <p>f × 1 00</p>
        <p>N
Ps=
( N − N )</p>
        <p>f × 1 00</p>
        <p>N
Si=</p>
        <p>N</p>
        <p>t × 1 00</p>
        <p>N
Ra= N p ositive × 1 00</p>
        <p>N T eams
where Pf is Project failure rate, N f is number of failed and N ❑is number of Projects. By “failed”
meant projects that have answer “Delivered but exceeded budget or timeline” and “Not delivered or
failed” for question “What was the final project outcome”.</p>
        <p>With given set of data we have failure rate 66%
Project success rate has similar formula:</p>
        <p>Expected that success rate will be around 60-70% of overall quantity of the projects. But with
given set of the data our success rate is only 34%</p>
        <p>
          In [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ] where used different set of characteristics, like stakeholder involvement and team
availability, and to identify it’s values correct formulas to calculate those characteristics are
introduced. According to article results should be in scale high-medium-low. Formula for
stakeholder involvement will look this way:
        </p>
        <p>Where Si is stakeholder involvement and N i is number of interaction quantities and they
should be combined in this way: for high interactions answer “Daily” should be used, for low is
“Monthly” and for medium is sum of the rest answers for the “Stakeholder involvement” question.</p>
        <p>As result High interaction is 28%, Medium interaction 50% and Low interaction is 22%. Those
results falls into common sense that mean that medium iteration should be biggest one.</p>
        <p>For resource availability formula will be more complex because it gathers information out of
three questions from questionnaire:</p>
        <p>Where Ra is resource availability, N positive is number of positive (“Yes”) responses for questions
“Team was fully staffed on time and budget”, “There were cases of team member retention” and
(1)
(2)
(3)
(4)
“All team members where expected seniority” in Teams type. N Teams is quantity of answers for
those three questions, typically should be three times more than N .</p>
        <p>Result or resource availability with given data is 51,3% and it’s mean that in half case all
parameters of Team composition were correct and there were no issues with it.</p>
        <p>Next formula is for identifying methodology that was initially used in given (3):</p>
        <p>M i=</p>
        <p>N i × 1 00</p>
        <p>N</p>
        <p>Where M i is each methodology type from the question “Which PM methodology was used” and
N i is number of answers for each methodology type.</p>
        <p>Quite interesting will look metrics about correlation between methodology that was initially
used and used after the change, but this not direct scope of this article. Results shown in Table 6.
(5)
(6)
(7)
Methodology</p>
        <p>Scrum
Kanban
Waterfall</p>
        <p>Hybrid
No methodology</p>
        <p>Other</p>
        <p>Percentage
20
18
24
18
6
14
where N C h ange is number of answers “Methodology not suitable” and “Client insist” in question
“Why was the methodology changed” and N Met h odology is overall quantity of answers on this
question.</p>
        <p>Next and the most important characteristic that needs to be digested is correlation between
project failure and wrong methodology. To calculate it Pearson correlation coefficient will be used:
where r is Pearson correlation coefficient, P−f¿¿ and M −f¿¿ are means of corresponding items and
M f is wrong methodology indicator that calculates with next formula:
r =∑ ( Pf −</p>
        <p>P−¿)( Mf−M−f¿)</p>
        <p>f
√∑ ( Pf − P¿f × √∑ ( M f − M ¿f ¿ ¿</p>
        <p>¿ ¿
M f =</p>
        <sec id="sec-2-22-1">
          <title>N C h ange</title>
        </sec>
        <sec id="sec-2-22-2">
          <title>N M et h odology</title>
          <p>Result based on the data available is 48% and it means that in most of half of the cases
methodology was changed during the project.</p>
          <p>In result this Pearson correlation coefficient should show us actual correlation between
methodology and project failure and with value more that zero direction will be positive that will
mean that have correlation between those characteristics exists.</p>
          <p>For methodology correlation coefficient is weak but positive 0,092 and it means that there exists
correlation between methodology and project success.</p>
          <p>As for the risks there two simple formulas for most remediated and not remediated risk:
Where Ri is each remediated risk from question “Most common risks that were mitigated”, Rri
is number of answers for each remediated risk and N Rt is number of overall answers in the
question. Similar for not remediated:</p>
          <p>Ri= NR Rrri × 1 cs 00
Rni=</p>
          <p>Rn ri
N R r</p>
          <p>Interesting enough that Team retention risk sits on first place in both remediated and not
remediated risks</p>
          <p>Another crucial formula is formula for correlation between risk monitoring frequency and
project failure. This formula can show if risk monitoring is important for project failure or not. To
calculate this value another variant of Pearson correlation coefficient will be used:
r =
n ∑ ( Rm f − Po )−∑ Rmf ∑ Po
√[ n ∑ Rm f 2−(∑ Rmf ) ] ¿ ¿ ¿
2
where Rmf is risk monitoring frequency, Po is project outcome and n is number of responses.</p>
          <p>Where Rni is each not remediated risk from question “Most common risks that were converted
into issues”, Rnri is number of answers for each not remediated risk. Result is shown in Table 7.
(9)
(10)
Risk name</p>
          <p>Scope creep
Budget overrun</p>
          <p>Team retention
Unclear requirements</p>
          <p>Other
16
18
24
18
24
12
24
26
18
20</p>
          <p>Since desired outcome need to have more value and for that reason Fail value have higher
numeric value than Success. Results on given data show 0,1475 and it means that there no visible
correlation between project success and risk monitoring frequency.</p>
          <p>Next value that needs to be assessed is correlation between team composition and project
failure. To calculate this value firstly needs to be assessed team composition values and calculate
them with given formula:</p>
          <p>T s=S + R +∑ C + E
where T s is team composition score, S is staffing status from the question in Table 1, R is
retention status, ∑ C is sum of retention cases and E is expected seniority value. In that case max
value of T s should not exceed 5 for each case.</p>
          <p>Since team composition value logic calculated overall Pearson coefficient for correlation
between team composition and project failure can be calculated with next formula:
where T s team composition score, Po project outcome and n number of responses.</p>
          <p>Results here are more expected, correlation is 0,2421 and it means that there correlation
between Team composition and project success.</p>
          <p>Next parameter is correlation between project complexity and project failure.:
r =
n ∑ ( T s− Po )−∑ T s ∑ Po
√[ n ∑ T s2−(∑ T s) ] ¿ ¿ ¿</p>
          <p>2
r =
n ∑ ( Pc− Po )−∑ Pc ∑ Po
√[ n ∑ Pc2−(∑ Pc ) ] ¿ ¿ ¿
2
(11)
(12)
(13)
(14)
where Pc project complexity, Po project outcome and n number of responses.</p>
          <p>Result is same as in risk monitoring parameter, correlation coefficient is negative, -0,006 and it
meant that there not visible correlation between project complexity and project success rate.</p>
          <p>This formula is correlation between project success and project industry:</p>
          <p>I si= I i</p>
          <p>P f i
where I si is success rate in specific industry and I i quantity of specific industry in questionnaire
answers. Results are shown in Table 8.</p>
          <p>Transportation
Food and beverages</p>
          <p>Logistics
E-Commerce</p>
          <p>Edtech
Government</p>
          <p>Oil&amp;Gas
Manufacturing</p>
          <p>Other
40
0
14
60
20
50
66
0</p>
          <p>As the foundational dataset for this research is still undergoing refinement, it must be
acknowledged that the current responses collected from various industries may not fully reflect the
final or most accurate data. This limitation arises from the preliminary nature of the dataset and
the fact that certain industry sectors lack sufficient. In particular, some industry types reported
zero or near-zero success percentages, which may not indicate an actual absence of successful or
failed projects but instead highlight limitations in sample size at this stage of the study.</p>
          <p>This observation presents a methodological challenge from a statistical standpoint. The
presence of sectors with missing or non-numeric success data can distort the overall interpretation
of industry-level performance trends. As a result, caution must be exercised when drawing
generalized conclusions across industry categories, as some of the observed inconsistencies may be
attributable to incomplete data rather than to underlying differences in project execution or
methodology selection.</p>
          <p>Despite these constraints, the article presents a comprehensive analysis of project
characteristics and their potential correlations with outcomes. These analyses were performed
using structured data collected through questionnaires. The summarized findings of this analysis,
including identified correlations and their respective significance levels, are presented in Table 9
below. This table encapsulates the core empirical insights gained through the current phase of
research and serves as a foundation for further refinement and validation as the dataset evolves.</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. Conclusion</title>
      <p>The analysis of project failure rates and their correlation with various project characteristics has
yielded several key insights. The study found a project failure rate of 66%, with only 34% of projects
classified as successful. Among the factors investigated, methodology selection, team composition,
and risk monitoring practices emerged as critical influences on project outcomes.</p>
      <p>The data revealed a weak but still existing correlation (0.092) between project failure and
incorrect methodology selection, with 48% of respondents indicating that the chosen methodology
was later deemed unsuitable. This suggests that while methodology plays a role in project success,
other factors may have a stronger impact. Similarly, team composition showed a weak correlation
(0.2421) with project failure, reinforcing the idea that staffing issues contribute to project
challenges but may not be the sole determining factor.</p>
      <p>On the other hand, risk monitoring frequency showed no significant correlation (-0.1475) with
project failure, implying that merely tracking risks does not necessarily prevent failure unless
appropriate mitigation actions are taken. Additionally, project complexity also showed no
correlation (-0.006) with failure, suggesting that project outcomes are not solely dictated by
complexity but rather by how well they are managed.</p>
      <p>Stakeholder involvement also played a notable role, with high interaction levels (28%)
correlating with better project success rates, while low interaction (22%) tended to be associated
with poorer outcomes. The study also identified key risks that were either mitigated or not, with
budget overruns (24%) and team retention issues (26%) being the most common risks that led to
project difficulties.</p>
      <p>Overall, these findings highlight the need for a holistic approach to project management, where
methodology selection, risk mitigation, stakeholder engagement, and team composition are all
carefully considered to improve success rates. As data collection continues, further analysis may
refine these insights and provide more definitive conclusions on how best to enhance project
management practices for better outcomes.</p>
      <p>The results of this study have the potential to be integrated into a specialized mobile application
tailored for use within specific industries. This application could serve as a valuable tool not only
for internal departments, such as a Project Management Office (PMO), but also for external
stakeholders including consulting firms, partner organizations, and companies that are involved in
auditing processes. By embedding the study's findings into the app, it becomes a centralized
platform for informed decision-making and project planning.</p>
      <p>In addition to suggesting appropriate methodologies, the application would function as a
proactive advisory system for project managers. It would offer practical guidance and predictive
alerts about potential challenges or obstacles that may arise during different project phases. This
feature aims to empower project leaders with foresight and preparedness, ultimately contributing
to higher project success rates and more efficient resource allocation.</p>
    </sec>
    <sec id="sec-4">
      <title>Acknowledgements</title>
      <p>Ihor Berezutskyi would like to express his deepest gratitude to his wife, Hanna Zaviriukha, whose
support, advices around questionnaire composition helped to craft this work. Also worth mention
that Hanna was one of the first participants in survey and helped to identify several different
mistakes in wording and in logic.</p>
      <p>Also Ihor Berezutskyi would like to thank her daughter Liza for bringing joy and necessary
distraction that allow to systematically structure article and adjust formatting.</p>
      <p>In addition, Ihor Berezutsky would like to thank his supervisor, professor Tetyana
Honcharenko, for her technical expertise and guidance around work structure.</p>
      <p>Lastly, Ihor Berezutskyi wishes to express his sincere gratitude to his project manager colleagues,
whose participation in the survey and willingness to share their experiences provided invaluable
data for this research. Their support and engagement have been essential in making this study
possible.</p>
    </sec>
    <sec id="sec-5">
      <title>Declaration on Generative AI</title>
      <p>During the preparation of this work, the authors used ChatGPT in order to: Paraphrase and
reword. After using this tool/service, the authors reviewed and edited the content as needed and
takes full responsibility for the publication’s content.
IEEE 4th International Conference on Smart Information Systems and Technologies (SIST),
May 2024, URL: DOI: 10.1109/SIST61555.2024.10629587
[3] I. Berezutskyi, T. Honcharenko, Potential implications of artificial intelligence for project
management information systems, 2024. URL: https://ceur-ws.org/Vol-3709/paper3.pdf
[4] D. Chernyshev, G. Ryzhakova, H. Petrenko, I. Chupryna, N. Reznik, Digital Administration of
the Project Based on the Concept of Smart Construction, Lecture Notes in Networks and
Systems, vol.495 LNNS, pp. 1316–1331, 2023, International Conference on Business and
Technology, ICBT 2021, DOI: 10.1007/978-3-031-08954-1_114
[5] Mihaylenko, V., Borodavka, Y., Dolya, E., Savenko, V. Information tools for project
management of the building territory at the stage of urban planning, CEUR Workshop
Proceedings, 2021, 2851, рр. 22–33, http://ceur-ws.org/Vol-2851/paper3.pdf
[6] S. Bushuyev, K. Pilyugina,I. Achkasov, A. Zaprivoda, Clip Thinking in the Digital Age:
Complimentary or Contradictory, 2023 IEEE 18th International Conference on Computer
Science and Information Technologies (CSIT), 2023. DOI: 10.1016/j.procs.2023.12.210
[7] Khan, A., Hasana, M.K., Ghazal, T.M., Islam, S., Alzoubi, H.M., Mokhtar, U.A., Alam, R.,
Ahmad, M., 2022. Collaborative Learning Assessment via Information and Communication
Technology, in: Proceedings, RIVF 2022., pp. 311-316
[8] S. Bushuyev, N. Bushuyeva, D. Bushuiev, V. Bushuieva, Integrated Intelligence Model for
Assessment Digital Transformation Project, 2023 IEEE International Conference on Smart
Information Systems and Technologies (SIST), 2023. DOI:10.1109/SIST58284.2023.10223578
[9] M. El Khatib, A. Al Falasi, Effects of Artificial Intelligence on Decision Making in Project</p>
      <p>Management, American Journal of Industrial and Business Management 11, 2021, pp. 251-260.
[10] Harvard Business Review Analytic Services, The Evolution of Decision Making: How Leading
Organizations Are Adopting a Data-Driven Culture. URL:
https://hbr.org/resources/pdfs/tools/17568_HBR_SAS%20Report_webview.pdf
[11] R. Nicoara, Project Management Methods, 2023, DOI: 10.1007/978-1-4842-9663-9_12
[12] R. L. Moura, T. C. J. Carneiro, T. L. Dias, VUCA environment on project success: The effect of
project management methods, Brazilian Business Review 20(3), 2023, DOI:
10.15728/bbr.2023.20.3.1.en
[13] M. Nekrasova, Using methods of probability theory and mathematical statistics in project
management, Bulletin of the National Technical University «KhPI» Series Dynamics and
Strength of Machines, 2023, DOI: 10.20998/2078-9130.2023.2.293040
[14] S. Turney Pearson Correlation Coefficient (r). Guide &amp; Examples, 2024
https://www.scribbr.com/statistics/pearson-correlation-coefficient/
[15] I. Berezutskyi, Method for analyzing project characteristics, Management of Development of</p>
      <p>Complex Systems, Kyiv, 2025. DOI: 10.32347/2412-9933.2025.61.145-150
[16] Aliyev, Ali. The AI and Quantum Era: Transforming Project Management Practices. Journal of</p>
      <p>Future Artificial Intelligence and Technologies 1.4 (2025): 348-370
[17] G. Ryzhakova, T. Honcharenko, K. Predun, N. Petrukha, O. Malykhina, and O. Khomenko.</p>
      <p>Using of Fuzzy Logic for Risk Assessment of Construction Enterprise Management System.
2023 IEEE International Conference on Smart Information Systems and Technologies (SIST),
Astana, Kazakhstan, 2023, pp. 208-213, doi:10.1109/SIST58284.2023.10223560
[18] O. Ilin, S. Bushuyev, V. Gots, T. Liashchenko, Management of IT projects of business analytics
in the BANI environment, Management of Development of Complex Systems, 2024, DOI:
10.32347/2412-9933.2024.59.45-52.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>R.</given-names>
            <surname>Young</surname>
          </string-name>
          , Why Projects Fails | Incorrect Methodology https://ligsuniversity.com/why-projectsfail
          <string-name>
            <surname>-</surname>
          </string-name>
          incorrect-methodology/, LIGS University,
          <year>2024</year>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>I.</given-names>
            <surname>Berezutskyi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Honcharenko</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Ryzhakova</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Tykhonova</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Pokolenko</surname>
          </string-name>
          ,
          <string-name>
            <surname>I. Sachenko</surname>
          </string-name>
          ,
          <article-title>Methodological Approach for Choosing Type of IT Projects Management</article-title>
          , Conference: 2024
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>