<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.3 20210610//EN" "JATS-journalpublishing1-3.dtd">
<article article-type="research-article" dtd-version="1.3" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xml:lang="ru"><front><journal-meta><journal-id journal-id-type="publisher-id">koz</journal-id><journal-title-group><journal-title xml:lang="ru">"Вестник Северо-Казахстанского университета имени Манаша Козыбаева"</journal-title><trans-title-group xml:lang="en"><trans-title>Bulletin of Manash Kozybayev North Kazakhstan University</trans-title></trans-title-group></journal-title-group><issn pub-type="ppub">2958-003X</issn><issn pub-type="epub">2958-0048</issn><publisher><publisher-name>М. Қозыбаев атындағы СҚУ</publisher-name></publisher></journal-meta><article-meta><article-id pub-id-type="doi">10.54596/2958-0048-2025-2-184-193</article-id><article-id custom-type="elpub" pub-id-type="custom">koz-2193</article-id><article-categories><subj-group subj-group-type="heading"><subject>Research Article</subject></subj-group><subj-group subj-group-type="section-heading" xml:lang="ru"><subject>ИНФОРМАЦИОННО-КОММУНИКАЦИОННЫЕ ТЕХНОЛОГИИ</subject></subj-group><subj-group subj-group-type="section-heading" xml:lang="en"><subject>INFORMATION AND COMMUNICATION TECHNOLOGIES</subject></subj-group></article-categories><title-group><article-title>Методология Agile в банковском программном обеспечении: анализ внедрения на примере компании Smart Solution</article-title><trans-title-group xml:lang="en"><trans-title>Agile methodologies in banking software: a case-based analysis of implementation at Smart Solution</trans-title></trans-title-group></title-group><contrib-group><contrib contrib-type="author" corresp="yes"><name-alternatives><name name-style="eastern" xml:lang="ru"><surname>Куликова</surname><given-names>Е. В.</given-names></name><name name-style="western" xml:lang="en"><surname>Kulikova</surname><given-names>E. V.</given-names></name></name-alternatives><bio xml:lang="ru"><p>Аврора</p></bio><bio xml:lang="en"><p>Kulikova Evgenia V., corresponding author, MS Computer Science, Solutions Architect and Business Analysis Manager </p><p>Ontario </p></bio><email xlink:type="simple">ekulikova@smartsolution.com</email><xref ref-type="aff" rid="aff-1"/></contrib></contrib-group><aff-alternatives id="aff-1"><aff xml:lang="ru">Smart Solution<country>Канада</country></aff><aff xml:lang="en">Smart Solution, located Aurora<country>Canada</country></aff></aff-alternatives><pub-date pub-type="collection"><year>2025</year></pub-date><pub-date pub-type="epub"><day>04</day><month>07</month><year>2025</year></pub-date><volume>0</volume><issue>2 (66)</issue><fpage>184</fpage><lpage>193</lpage><permissions><copyright-statement>Copyright &amp;#x00A9; Куликова Е.В., 2025</copyright-statement><copyright-year>2025</copyright-year><copyright-holder xml:lang="ru">Куликова Е.В.</copyright-holder><copyright-holder xml:lang="en">Kulikova E.V.</copyright-holder><license xml:lang="ru" license-type="creative-commons-attribution" xlink:href="https://creativecommons.org/licenses/by/4.0/" xlink:type="simple"><license-p>Данная работа распространяется под лицензией Creative Commons Attribution 4.0.</license-p></license><license xml:lang="en" license-type="creative-commons-attribution" xlink:href="https://creativecommons.org/licenses/by/4.0/" xlink:type="simple"><license-p>This work is licensed under a Creative Commons Attribution 4.0 License.</license-p></license></permissions><self-uri xlink:href="https://vestnik.ku.edu.kz/jour/article/view/2193">https://vestnik.ku.edu.kz/jour/article/view/2193</self-uri><abstract><p>В последние годы внедрение фреймворков Agile в разработку банковского программного обеспечения значительно активизировалось, что обусловлено необходимостью повышения гибкости, ускорения поставки решений и повышения адаптивности к изменениям. В настоящей статье представлен кейс Smart Solution (далее – Smart), канадского поставщика банковских ИТ-решений, с акцентом на практическое применение методологий Scrum, Kanban и Scrumban в условиях нормативно регулируемой финансовой среды. На основе анализа внутренних процессов, структуры команды, используемых инструментов и типов проектов рассмотрено, каким образом принципы Agile были адаптированы для соблюдения требований соответствия, обеспечения предсказуемости релизов и эффективного управления параллельными потоками задач. Среди выявленных проблем – несоответствие инструментов, отсутствие устойчивого фокуса в спринтах и ограничения Scrum при выполнении задач технической поддержки. Полученные результаты свидетельствуют о том, что Scrumban представляет собой жизнеспособную гибридную модель, сочетающую структурированное планирование с гибкостью непрерывного потока. В завершение представлены рекомендации по применению Agile в банковской сфере и сформулированы гипотезы для дальнейших исследований.</p></abstract><trans-abstract xml:lang="en"><p>The implementation of Agile frameworks in banking software development has gained momentum in recent years, driven by the need for flexibility, faster delivery, and greater responsiveness to change. This paper presents a case study of Smart Solution (hereafter referred to as Smart), a Canadian banking software provider, and explores the practical application of Scrum, Kanban, and Scrumban methodologies within a regulated financial environment. Through an analysis of internal practices, team structure, tooling, and project types, the study examines how Agile principles have been adapted to meet compliance standards, maintain predictable release cycles, and balance multiple parallel workstreams. Challenges encountered include tool misalignment, inconsistent sprint focus, and the limitations of Scrum for maintenance work. Findings suggest that Scrumban offers a viable hybrid solution, combining structured planning with continuous flow. The paper concludes with recommendations for implementing Agile in the banking domain and proposes several hypotheses for future research.</p></trans-abstract><kwd-group xml:lang="ru"><kwd>Agile</kwd><kwd>Scrum</kwd><kwd>Kanban</kwd><kwd>Scrumban</kwd><kwd>банковское программное обеспечение</kwd><kwd>финтех</kwd><kwd>соответствие требованиям</kwd><kwd>разработка ПО</kwd><kwd>кейс-стади</kwd></kwd-group><kwd-group xml:lang="en"><kwd>Agile</kwd><kwd>Scrum</kwd><kwd>Kanban</kwd><kwd>Scrumban</kwd><kwd>Banking Software</kwd><kwd>Fintech</kwd><kwd>Compliance</kwd><kwd>Software Development</kwd><kwd>Case Study</kwd></kwd-group></article-meta></front><back><ref-list><title>References</title><ref id="cit1"><label>1</label><citation-alternatives><mixed-citation xml:lang="ru">Anderson, D.J. (2010). Kanban: Successful evolutionary change for your technology business. Blue Hole Press.</mixed-citation><mixed-citation xml:lang="en">Anderson, D.J. (2010). Kanban: Successful evolutionary change for your technology business. Blue Hole Press.</mixed-citation></citation-alternatives></ref><ref id="cit2"><label>2</label><citation-alternatives><mixed-citation xml:lang="ru">Google. (2022). AI principles. https://ai.google/principles/</mixed-citation><mixed-citation xml:lang="en">Google. (2022). AI principles. https://ai.google/principles/</mixed-citation></citation-alternatives></ref><ref id="cit3"><label>3</label><citation-alternatives><mixed-citation xml:lang="ru">Highsmith, J. (2009). Agile project management: Creating innovative products. Addison-Wesley.</mixed-citation><mixed-citation xml:lang="en">Highsmith, J. (2009). Agile project management: Creating innovative products. Addison-Wesley.</mixed-citation></citation-alternatives></ref><ref id="cit4"><label>4</label><citation-alternatives><mixed-citation xml:lang="ru">International Organization for Standardization. (2022). ISO/IEC 22989:2022 - Artificial intelligence - Concepts and terminology. ISO.</mixed-citation><mixed-citation xml:lang="en">International Organization for Standardization. (2022). ISO/IEC 22989:2022 - Artificial intelligence - Concepts and terminology. ISO.</mixed-citation></citation-alternatives></ref><ref id="cit5"><label>5</label><citation-alternatives><mixed-citation xml:lang="ru">Ladas, C. (2009). Scrumban: Essays on Kanban systems for lean software development. Modus Cooperandi Press.</mixed-citation><mixed-citation xml:lang="en">Ladas, C. (2009). Scrumban: Essays on Kanban systems for lean software development. Modus Cooperandi Press.</mixed-citation></citation-alternatives></ref><ref id="cit6"><label>6</label><citation-alternatives><mixed-citation xml:lang="ru">Rigby, D.K., Sutherland, J., &amp; Takeuchi, H. (2016). Embracing agile. Harvard Business Review, 94(5), 40-50.</mixed-citation><mixed-citation xml:lang="en">Rigby, D.K., Sutherland, J., &amp; Takeuchi, H. (2016). Embracing agile. Harvard Business Review, 94(5), 40-50.</mixed-citation></citation-alternatives></ref><ref id="cit7"><label>7</label><citation-alternatives><mixed-citation xml:lang="ru">Schwaber, K., &amp; Beedle, M. (2002). Agile software development with Scrum. Prentice Hall.</mixed-citation><mixed-citation xml:lang="en">Schwaber, K., &amp; Beedle, M. (2002). Agile software development with Scrum. Prentice Hall.</mixed-citation></citation-alternatives></ref><ref id="cit8"><label>8</label><citation-alternatives><mixed-citation xml:lang="ru">Stanford Institute for Human-Centered Artificial Intelligence. (2024). AI Index Report 2024. https://aiindex.stanford.edu/report/</mixed-citation><mixed-citation xml:lang="en">Stanford Institute for Human-Centered Artificial Intelligence. (2024). AI Index Report 2024. https://aiindex.stanford.edu/report/</mixed-citation></citation-alternatives></ref><ref id="cit9"><label>9</label><citation-alternatives><mixed-citation xml:lang="ru">Smart. (2017-2024). Internal documentation and retrospective reports (Unpublished internal documents).</mixed-citation><mixed-citation xml:lang="en">Smart. (2017-2024). Internal documentation and retrospective reports (Unpublished internal documents).</mixed-citation></citation-alternatives></ref></ref-list><fn-group><fn fn-type="conflict"><p>The authors declare that there are no conflicts of interest present.</p></fn></fn-group></back></article>
