{"id":11167,"date":"2025-05-19T15:37:16","date_gmt":"2025-05-19T15:37:16","guid":{"rendered":"https:\/\/thecodest.co\/blog\/\/"},"modified":"2026-05-19T13:37:24","modified_gmt":"2026-05-19T13:37:24","slug":"scrum-programines-irangos-inzinerijoje","status":"publish","type":"post","link":"https:\/\/thecodest.co\/lt\/blog\/scrum-in-software-engineering\/","title":{"rendered":"\"Scrum\" Software Engineering"},"content":{"rendered":"<p><\/p>\n\n\n\n<p>Jei j\u016bs\u0173 programin\u0117 \u012franga <a href=\"https:\/\/thecodest.co\/lt\/blog\/best-practices-for-building-a-strong-and-cohesive-team\/\">komanda<\/a> kovojate su kintan\u010diais reikalavimais, praleistais terminais ar nesusikalban\u010diomis suinteresuotosiomis \u0161alimis, nesate vieni. <a href=\"https:\/\/www.atlassian.com\/agile\/scrum\" rel=\"nofollow noopener noreferrer\">scrum<\/a> svetain\u0117je <a href=\"https:\/\/thecodest.co\/lt\/blog\/the-top-benefits-of-outsourcing-software-engineering-services\/\">programin\u0117s \u012frangos in\u017einerija<\/a> yra <a href=\"https:\/\/thecodest.co\/lt\/blog\/how-to-implement-agile-methodology\/\">Agile<\/a> sistema ypa\u010d veiksminga kuriant sud\u0117tingus produktus, nes joje taikomi kartotiniai procesai, skaidrumas ir pritaikomumas. \u0160iame vadove tiksliai paai\u0161kinama, kaip veikia \"Scrum\", kas k\u0105 daro ir kaip j\u0105 veiksmingai \u012fgyvendinti 2026 m.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-key-takeaways\">Pagrindin\u0117s i\u0161vados<\/h2>\n\n\n\n<p>\"Scrum\" - tai programin\u0117s \u012frangos in\u017einerijos srityje naudojama agile sistema, skirta valdyti sud\u0117tingus <a href=\"https:\/\/thecodest.co\/lt\/blog\/3-common-challenges-of-software-product-development-for-startups\/\">produkt\u0173 k\u016brimas<\/a> atliekant iteracin\u012f ir inkrementin\u012f darb\u0105, paprastai organizuojam\u0105 fiksuoto ilgio iteracijomis, vadinamomis sprintais (paprastai 1-4 savait\u0117s). Supratimas, kod\u0117l tai svarbu, prasideda nuo pagrindini\u0173 komponent\u0173 ir j\u0173 tarpusavio veikimo.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Trys esminiai vaidmenys lemia \"Scrum\" s\u0117km\u0119<\/strong>: A <strong>skuduras team<\/strong> sudaro trys pagrindiniai vaidmenys: <a href=\"https:\/\/thecodest.co\/lt\/dictionary\/how-to-make-product\/\">Produktas<\/a> Savininkas, savinink\u0117. <strong>Scrum Master<\/strong>, ir <a href=\"https:\/\/thecodest.co\/lt\/blog\/how-to-hire-the-best-outsourced-development-team-for-a-scaleup\/\">K\u016brimo komanda<\/a>. \u0160ie vaidmenys apibr\u0117\u017eiami remiantis <strong>Scrum teorija<\/strong>, kuriame pateikiami pagrindiniai principai, kuriais grind\u017eiama \"Scrum\" strukt\u016bra ir praktika. Kiekvienas j\u0173 turi konkre\u010dias pareigas, kurios padeda u\u017etikrinti, kad k\u016brimas jud\u0117t\u0173 \u012f priek\u012f ir nesusidaryt\u0173 kli\u016b\u010di\u0173.<\/li>\n\n\n\n<li><strong>Penki \"scrum\" \u012fvykiai sukuria ritm\u0105 ir atskaitomyb\u0119<\/strong>: <a href=\"https:\/\/thecodest.co\/lt\/dictionary\/what-is-sprint-backlog\/\">Sprint<\/a>, Sprinto planavimas, kasdienis \"Scrum\", sprinto per\u017ei\u016bra ir sprinto retrospektyva strukt\u016bruoja team darb\u0105 ir u\u017etikrina reguliar\u0173 produkto ir proceso tikrinim\u0105 bei pritaikym\u0105.<\/li>\n\n\n\n<li><strong>Trys <strong>Scrum artefaktai<\/strong> i\u0161laikyti skaidrum\u0105<\/strong>: Svetain\u0117 <a href=\"https:\/\/thecodest.co\/lt\/blog\/know-the-difference-product-vs-sprint-backlog\/\">Produkt\u0173 s\u0105ra\u0161as<\/a>, sprinto darb\u0173 s\u0105ra\u0161as ir padid\u0117jimas leid\u017eia visiems matyti darbus, tod\u0117l galima priimti geresnius sprendimus ir grei\u010diau koreguoti eig\u0105.<\/li>\n\n\n\n<li><strong>Privalumai apima ne tik greitesn\u012f pristatym\u0105<\/strong>: In\u017einerijos team, naudojantys \"Scrum\", patiria greit\u0105 gr\u012f\u017etam\u0105j\u012f ry\u0161\u012f, didesn\u012f klient\u0173 pasitenkinim\u0105 ir geresn\u012f bendradarbiavim\u0105 tarp \"Scrum\" team nari\u0173 dirbant su sud\u0117tingais projektais.<\/li>\n\n\n\n<li><strong>Da\u017eniausiai pasitaikan\u010di\u0173 sp\u0105st\u0173 galima i\u0161vengti<\/strong>: Neai\u0161ki organizacin\u0117 strukt\u016bra, silpni sprinto tikslai ar netinkamai naudojami parengiamieji pos\u0117d\u017eiai ma\u017eina \"Scrum\" veiksmingum\u0105, ta\u010diau kiekviena problema turi konkre\u010di\u0173 sprendim\u0173, kurie aptariami \u0161iame straipsnyje.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-what-is-scrum-in-software-engineering\">Kas yra \"Scrum\" Software Engineering?<\/h2>\n\n\n\n<p><strong>Scrum<\/strong> yra ver\u017eli <a href=\"https:\/\/thecodest.co\/lt\/blog\/8-key-questions-to-ask-your-software-development-outsourcing-partner\/\">programin\u0117s \u012frangos k\u016brimas<\/a> sistema, pagal kuri\u0105 darbas organizuojamas \u012f terminuotus sprintus (paprastai nuo 1 iki 4 savai\u010di\u0173), per kuriuos team pristato darbin\u0117s programin\u0117s \u012frangos dalis, kurias galima i\u0161si\u0173sti. Sprintas yra fiksuotas laiko tarpas, per kur\u012f <strong>Skirta team<\/strong> dirbama siekiant bendro sprinto tikslo, o dvi savait\u0117s yra \u012fprasta trukm\u0117, kuri suderina gr\u012f\u017etamojo ry\u0161io greit\u012f ir planavimo s\u0105naudas.<\/p>\n\n\n\n<p><strong>Scrum<\/strong> grind\u017eiamas empiriniu proces\u0173 valdymu, kuris teigia, kad \u017einios gaunamos i\u0161 patirties, o sprendimai priimami remiantis stebimais rezultatais. Empirin\u0117 proces\u0173 kontrol\u0117 apima skaidrum\u0105, tikrinim\u0105 ir pritaikym\u0105, kurie u\u017etikrina, kad visi darbai b\u016bt\u0173 matomi, da\u017enai tikrinami ir prireikus pritaikomi siekiant pagerinti kokyb\u0119 ir pa\u017eang\u0105. <strong>Scrum<\/strong> remiasi ai\u0161kiai apibr\u0117\u017etu <a href=\"https:\/\/thecodest.co\/lt\/blog\/what-to-look-for-in-a-custom-software-development-company\/\">k\u016brimo procesas<\/a> u\u017etikrinti skaidrum\u0105, nuolatin\u012f tobul\u0117jim\u0105 ir auk\u0161tos kokyb\u0117s rezultatus visoje <a href=\"https:\/\/thecodest.co\/lt\/dictionary\/why-do-projects-fail\/\">projektas<\/a> gyvavimo cikl\u0105.<\/p>\n\n\n\n<p>\u0160is empiri\u0161kumas padeda in\u017einieriams team efektyviau nei tradiciniai krioklio modeliai tvarkyti kintan\u010dius reikalavimus, sud\u0117tingas architekt\u016bras ir paveld\u0117t\u0173 sistem\u0173 integracij\u0105. Tyrimai rodo, kad krioklio projektuose po i\u0161leidimo atsiranda iki 40% daugiau defekt\u0173, palyginti su judriais metodais, daugiausia d\u0117l to, kad reikalavimai per anksti u\u017efiksuojami.<\/p>\n\n\n\n<p>Apsvarstykite tipin\u012f scenarij\u0173: team kuria <a href=\"https:\/\/thecodest.co\/lt\/blog\/find-your-ideal-stack-for-web-development\/\">\u017einiatinklio svetain\u0117<\/a> 2 savai\u010di\u0173 trukm\u0117s sprintuose su nuolatiniu diegimu ir automatizuotais testais. Per kiekvien\u0105 sprint\u0105 sukuriama veikianti programin\u0117 \u012franga, kuria suinteresuotosios \u0161alys gali i\u0161 tikr\u0173j\u0173 naudotis ir teikti atsiliepimus, o ne m\u0117nesius laukti didel\u0117s apimties i\u0161leidimo.<\/p>\n\n\n\n<p>Svarbu, <strong>Scrum<\/strong> yra sistema, o ne grie\u017eta metodika. Tokia technin\u0117 praktika, kaip TDD, porinis programavimas, k\u016brimas pagal kamien\u0105 ir CI\/CD pipelines, paliekama team autoriaus nuo\u017ei\u016brai. \u0160is lankstumas leido <strong>Scrum<\/strong> prisitaikyti prie \u0161iuolaikini\u0173 stek\u0173, \u012fskaitant debes\u0173 program\u0117les, <a href=\"https:\/\/thecodest.co\/lt\/dictionary\/microservices\/\">mikroservisai<\/a>, ir dirbtinio intelekto \/ ML funkcijas.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-agile-vs-scrum-in-software-development\">\"Agile\" ir \"Scrum\" programin\u0117s \u012frangos k\u016brimo srityje<\/h2>\n\n\n\n<p>Agile yra plati filosofija, kylanti i\u0161 2001 m. \"Agile\" manifesto, kurioje pirmenyb\u0117 teikiama asmenims, o ne procesams, veikian\u010diai programinei \u012frangai, o ne dokumentams, bendradarbiavimui su klientais, o ne sutartims, ir reagavimui \u012f poky\u010dius, o ne plan\u0173 laikymuisi. <strong>Scrum<\/strong> yra viena i\u0161 konkre\u010di\u0173 \"Agile\" strukt\u016br\u0173, kurioje \u0161ie \"Agile\" principai \u012fgyvendinami per konkre\u010dias strukt\u016bras.<\/p>\n\n\n\n<p>\u0160tai kuo prakti\u0161kai skiriasi \"agile\" metodika nuo \"scrum\" metodikos:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><th>Aspektas<\/th><th>Agile (filosofija)<\/th><th>\"Scrum\" (sistema)<\/th><\/tr><tr><td>Strukt\u016bra<\/td><td>Lankstus, pagr\u012fstas principais<\/td><td>Nustatyti vaidmenys, \u012fvykiai, artefaktai<\/td><\/tr><tr><td>Iteracijos<\/td><td>Ne\u012fpareigota<\/td><td>Sprintai pagal laik\u0105 (1-4 savait\u0117s)<\/td><\/tr><tr><td>Vaidmenys<\/td><td>Nenurodyta<\/td><td>Produkto savininkas, Scrum Master, programuotojai<\/td><\/tr><tr><td>Susitikimai<\/td><td>Pagal poreik\u012f<\/td><td>Penkios apibr\u0117\u017etos \"scrum\" ceremonijos<\/td><\/tr><tr><td>Artefaktai<\/td><td>Skiriasi priklausomai nuo \u012fgyvendinimo<\/td><td>Produkto darb\u0173 \u017eurnalas, sprinto darb\u0173 \u017eurnalas, prieaugis<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>Apsvarstykite, kaip gal\u0117t\u0173 veikti neformali judri team: k\u016br\u0117jai imasi u\u017eduo\u010di\u0173, kai yra pasiruo\u0161\u0119, susitikimai vyksta ad hoc, o leidiniai i\u0161leid\u017eiami, kai team jau\u010diasi pasiruo\u0161usi. A <strong>Scrum k\u016brimas team<\/strong>, prie\u0161ingai, darbas suskirstytas \u012f sprintus su oficialiomis sprinto per\u017ei\u016bromis ir sprinto retrospektyvomis, kurios sukuria nusp\u0117jam\u0105 ritm\u0105.<\/p>\n\n\n\n<p>Kitos judrios metodikos <a href=\"https:\/\/thecodest.co\/lt\/blog\/team-augmentation-how-to-scale-your-tech-team-efficiently-in-2026\/\">Kanban<\/a> (nenutr\u016bkstamas srautas su WIP apribojimais) ir XP (d\u0117mesys techninei praktikai). <strong>Scrum<\/strong> geriausiai tinka produkt\u0173 k\u016brimui, kai kei\u010diasi funkcij\u0173 rinkiniai, daug suinteresuot\u0173j\u0173 \u0161ali\u0173, kurioms reikia reguliaraus gr\u012f\u017etamojo ry\u0161io, ir team, kuriems naudingas strukt\u016brinis iteracijos procesas. <strong>Scrum agile<\/strong> i\u0161 ties\u0173 yra judrus programin\u0117s \u012frangos k\u016brimas, ta\u010diau ne visi judr\u016bs metodai naudoja \"scrum\" renginius ar reikalauja \"scrum\" meistro vaidmens.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-origins-and-evolution-of-scrum-in-software-engineering\">\"Scrum\" i\u0161takos ir raida Software Engineering<\/h2>\n\n\n\n<p>Kenas Schwaberis ir Jeffas Sutherlandas suk\u016br\u0117 \u201cScrum\" XX a. de\u0161imtojo de\u0161imtme\u010dio prad\u017eioje, \u012fkv\u0117pti 1986 m. \"Harvard Business Review\" straipsnio \"The New New <strong>Produkto k\u016brimo \u017eaidimas<\/strong>\u201d pagal Takeuchi ir Nonaka. Tame straipsnyje buvo apra\u0161ytas regbio team stiliaus po\u017ei\u016bris \u012f inovacijas, taigi ir \u201cScrum\u201d, kuris labai skiriasi nuo grie\u017et\u0173 nuosekli\u0173j\u0173 modeli\u0173.<\/p>\n\n\n\n<p>Pirmieji \"Scrum\" diegimo etapai tokiose \u012fmon\u0117se kaip \"Easel Corporation\" ir \"IDX Health\" buvo orientuoti \u012f nedideles, kartu veikian\u010dias programin\u0117s \u012frangos team grupes, kurios kas 30 dien\u0173 pristatydavo naujienas. <a href=\"https:\/\/thecodest.co\/lt\/blog\/revolutionize-telecom-with-top-software-solutions\/\">Telecom<\/a> ir <a href=\"https:\/\/thecodest.co\/lt\/blog\/fintech-the-future-of-finance\/\">finansai<\/a> sektoriuose buvo prad\u0117ta taikyti anksti, o atvej\u0173 tyrimai parod\u0117, kad 50% sutrumpino ciklo laik\u0105 30 dien\u0173 intervalais.<\/p>\n\n\n\n<p>Svarbiausi \"Scrum\" evoliucijos etapai:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>1995<\/strong>: Schwaberis ir Sutherlandas oficialiai pristat\u0117 \"Scrum\" parodoje OOPSLA<\/li>\n\n\n\n<li><strong>2010<\/strong>: Pirmasis oficialus <strong>Scrum vadovas<\/strong> paskelbta internete<\/li>\n\n\n\n<li><strong>2017<\/strong>: Atnaujinti sujungt\u0105 \u201cK\u016brimo grup\u0117s\u201d terminologij\u0105 \u012f \u201cK\u016br\u0117j\u0173\u201d<\/li>\n\n\n\n<li><strong>2020<\/strong>: \u012ediegta produkto tikslo koncepcija, supaprastinta iki 13 puslapi\u0173, pabr\u0117\u017etas vienas produkto savininkas.<\/li>\n<\/ul>\n\n\n\n<p>\u0160iuolaikin\u0117 in\u017einerin\u0117 praktika 2015-2026 m. pakeit\u0117 tai, kaip team kuria savo \"Atlikto\" apibr\u0117\u017et\u012f. <a href=\"https:\/\/thecodest.co\/lt\/blog\/maximize-your-software-delivery-the-4-essential-devops-practices-you-need-to-know\/\">DevOps<\/a> integracija rei\u0161kia, kad dabar DoD da\u017enai apima CI\/CD pipeline etapus, steb\u0117senos kabliukus ir na\u0161umo kriterijus. Komandos \u012ftraukia funkcij\u0173 \u017eymes, skirtas A\/B bandymams, ir automatinio at\u0161aukimo mechanizmus tiesiai \u012f savo sprinto darbo eig\u0105.<\/p>\n\n\n\n<p>\u0160iandien \"Scrum\" galima pritaikyti daugeliui team ir sud\u0117tingiems produktams, taikant tokius modelius kaip bendri darb\u0173 planai ir tarpusavio team koordinavimas. Scrum aljansas ir kitos organizacijos toliau sertifikuoja Scrum praktikus visame pasaulyje. Ta\u010diau pagrindiniai \"Scrum\" principai teb\u0117ra orientuoti \u012f team darb\u0105, prisitaikym\u0105 ir skaidrum\u0105.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-scrum-framework-roles-team-members-and-organizational-structure\">\"Scrum\" sistema: Vaidmenys, komandos nariai ir organizacin\u0117 strukt\u016bra<\/h2>\n\n\n\n<p>\"Scrum\" team programin\u0117s \u012frangos in\u017einerijos srityje - tai nedidelis, daugiafunkcinis, savaranki\u0161kai valdomas padalinys, paprastai nuo 5 iki 10 \u017emoni\u0173, turintis visus \u012fg\u016bd\u017eius, reikalingus veikian\u010diai programinei \u012frangai pristatyti kiekvien\u0105 sprint\u0105. \"Scrum\" apima konkre\u010dius vaidmenis, tokius kaip produkto savininkas, Scrum Master ir programuotojai, kuri\u0173 kiekvienas turi apibr\u0117\u017etas pareigas, kad b\u016bt\u0173 i\u0161vengta kli\u016b\u010di\u0173 ir paskirstyta atsakomyb\u0117. Scrum Master yra atsakingas u\u017e \"Scrum\" team efektyvumo didinim\u0105, instruktuodamas team narius, \u0161alindamas kli\u016btis ir palengvindamas \"Scrum\" procesus, kad pager\u0117t\u0173 team na\u0161umas ir pristatymas.<\/p>\n\n\n\n<p><strong>Drobiniai teams<\/strong> yra saviorganizuojantys ir tarpfunkciniai, t. y. team nariai glaud\u017eiai bendradarbiauja ir prisiima kolektyvin\u0119 atsakomyb\u0119 u\u017e atlikt\u0105 darb\u0105, o tai didina team sanglaud\u0105 ir veiksmingum\u0105. \u0160i strukt\u016bra tinka \u012fvairiems organizaciniams modeliams, organizuotiems pagal produkt\u0173 linijas, team platformas ar vert\u0117s srautus.<\/p>\n\n\n\n<p>Sistemoje s\u0105moningai vengiama dalini\u0173 team (speciali\u0173 backend grupi\u0173, tik QA team), kurios pa\u017eeid\u017eia vis\u0105 team koncepcij\u0105. Tarpfunkci\u0161kumas suma\u017eina perdavim\u0173 skai\u010di\u0173 ir leid\u017eia visiems sutelkti d\u0117mes\u012f \u012f sprinto tiksl\u0105, o ne \u012f atskirus rezultatus.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-product-owner-in-software-engineering\">Produkto savininkas Software Engineering<\/h3>\n\n\n\n<p>Produkto savininkas yra atsakingas u\u017e produkto vert\u0117s didinim\u0105 ir produkto \"Backlog\" valdym\u0105, u\u017etikrinant, kad jo prioritetai b\u016bt\u0173 nustatomi atsi\u017evelgiant \u012f verslo ir klient\u0173 poreikius. \"Scrum\" taiko verte pagr\u012fst\u0105 prioritet\u0173 nustatym\u0105, kad kuo anks\u010diau ir da\u017eniau b\u016bt\u0173 u\u017etikrinta did\u017eiausia verslo vert\u0117.<\/p>\n\n\n\n<p>Programin\u0117je \u012frangoje team produkto savininkas glaud\u017eiai bendradarbiauja su naudotojais, <a href=\"https:\/\/thecodest.co\/lt\/blog\/enhance-your-application-with-professional-ux-auditing\/\">UX<\/a> dizaineriai, pardav\u0117jai ir palaikymo specialistai, kad suformuot\u0173 naudotojo istorijas pagal INVEST kriterijus (nepriklausomas, sutartinis, vertingas, \u012fkainojamas, nedidelis, i\u0161bandomas). Jie apibr\u0117\u017eia pri\u0117mimo kriterijus ir supranta, kaip funkcijos veikia auk\u0161to lygio architekt\u016br\u0105.<\/p>\n\n\n\n<p>Konkretaus produkto savininko pareigos:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Prioritetini\u0173 produkt\u0173 s\u0105ra\u0161o su funkcijomis, klaidomis ir technin\u0117mis skolomis palaikymas<\/li>\n\n\n\n<li>B\u016bsim\u0173 sprint\u0173 element\u0173 tobulinimas kartu su k\u016brimo grupe team<\/li>\n\n\n\n<li>Reikalavim\u0173 i\u0161ai\u0161kinimas sprinto planavimo metu<\/li>\n\n\n\n<li>Sprendim\u0105 d\u0117l parengties i\u0161leisti versl\u0105 priimti atsi\u017evelgiant \u012f verslo vert\u0119 ir technin\u0119 rizik\u0105.<\/li>\n<\/ul>\n\n\n\n<p>Vienas produkto savininkas kiekvienam produktui padeda i\u0161vengti prie\u0161taring\u0173 \"scrum\" k\u016brimo kryp\u010di\u0173 team. Net kai padeda verslo analitikai, galutinius sprendimus d\u0117l atsilikimo priima produkto savininkas. Kai <strong>projekt\u0173 valdymas<\/strong> kelioms team, dirban\u010dioms su bendru produktu, produkto savininkas i\u0161lieka prieinamas team nariams sprinto metu, koordinuodamas vis\u0173 komponent\u0173 veikl\u0105.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-scrum-master-servant-leader-for-the-team\">Scrum Master: Tarnaujantis komandos lyderis<\/h3>\n\n\n\n<p>Scrum Master veikia kaip team treneris, padedantis jiems laikytis \"scrum\" proceso, \u0161alinantis kli\u016btis ir palengvinantis team nari\u0173 bendradarbiavim\u0105. \u0160is tarnaujan\u010dio lyderio vaidmuo sutelkia d\u0117mes\u012f \u012f tai, kad team suteikia galimyb\u0119, o ne vadovauja j\u0173 darbui. Scrum Master taip pat palengvina \"Scrum\" darb\u0105, \u012fskaitant planavim\u0105, kasdienius pasitarimus ir produkto prieaugio pristatym\u0105, u\u017etikrindamas, kad \u0161i bendradarbiavimo veikla b\u016bt\u0173 gerai organizuota ir sinchronizuota pagal \"Scrum\" sistem\u0105.<\/p>\n\n\n\n<p>Da\u017eniausiai pasitaikan\u010dios programin\u0117s \u012frangos in\u017einerijos kli\u016btys, kurias padeda i\u0161spr\u0119sti Scrum Master:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Sukurti pipeline nes\u0117kmes, blokuojan\u010dias integracij\u0105<\/li>\n\n\n\n<li>Tr\u016bkstamos bandym\u0173 aplinkos <a href=\"https:\/\/thecodest.co\/lt\/blog\/discover-the-top-reasons-why-qa-is-vital\/\">QA<\/a><\/li>\n\n\n\n<li>Neai\u0161ku, <a href=\"https:\/\/thecodest.co\/lt\/blog\/compare-staff-augmentation-firms-that-excel-in-api-team-staffing-for-financial-technology-projects\/\">API<\/a> nuosavyb\u0117 tarp paslaug\u0173<\/li>\n\n\n\n<li>Priklausomyb\u0117 nuo kit\u0173 team, kuri n\u0117ra \u012fvykdyta<\/li>\n\n\n\n<li>Funkcij\u0173 k\u016brim\u0105 l\u0117tina technin\u0117 skola<\/li>\n<\/ul>\n\n\n\n<p>Scrum Master bendradarbiauja su vadovybe, siekdamas pagerinti organizacin\u0119 strukt\u016br\u0105 ir kult\u016br\u0105, kad team gal\u0117t\u0173 veiksmingai organizuoti savo veikl\u0105. Jie apsaugo team nuo apimties \u0161liau\u017eimo sprinto metu ir u\u017etikrina, kad tokie renginiai kaip kasdieniai \"scrum\" susirinkimai, sprinto per\u017ei\u016bra ir sprinto retrospektyva i\u0161likt\u0173 tikslingi, o ne tu\u0161ti ritualai.<\/p>\n\n\n\n<p>Prie\u0161ingi modeliai, kuri\u0173 reikia vengti: Scrum Master veikia kaip <a href=\"https:\/\/thecodest.co\/lt\/blog\/tech-lead-roles-and-responsibilities\/\">projekt\u0173 vadovas<\/a> skiria u\u017eduotis, atlieka tik susitikim\u0173 planuotojo funkcij\u0105 arba tampa tarpininku, kuris apsaugo team nuo bendravimo su suinteresuotosiomis \u0161alimis. Scrum Master tur\u0117t\u0173 mokyti team tiesiogiai bendrauti su \u0161iais asmenimis, kartu pa\u0161alindamas sisteminius blokatorius.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-scrum-developers-scrum-development-team\">\"Scrum\" k\u016br\u0117jai (\"Scrum\" k\u016brimo komanda)<\/h3>\n\n\n\n<p>K\u016brimo grup\u0117 - tai savaranki\u0161kai organizuojama grup\u0117, atsakinga u\u017e potencialiai i\u0161leid\u017eiamos produkto dalies pristatym\u0105 kiekvieno sprinto pabaigoje, kuri\u0105 paprastai sudaro nuo 5 iki 9 nari\u0173. J\u0105 sudaro <strong><a href=\"https:\/\/thecodest.co\/lt\/blog\/hire-software-developers\/\">programin\u0117s \u012frangos k\u016br\u0117jai<\/a><\/strong>, testeriai, DevOps <a href=\"https:\/\/thecodest.co\/lt\/blog\/team-extension-guide-software-development\/\">in\u017einieriai<\/a>, UX dizaineriai, <a href=\"https:\/\/thecodest.co\/lt\/blog\/app-data-collection-security-risks-value-and-types-explored\/\">duomenys<\/a> in\u017einieriai - visi, kurie prisideda prie sprinto darb\u0173 s\u0105ra\u0161o element\u0173 k\u016brimo.<\/p>\n\n\n\n<p>K\u016br\u0117jai kolektyviai planuoja, vertina ir vykdo. Jie sprend\u017eia, kaip paversti produkto darb\u0173 s\u0105ra\u0161o elementus veikian\u010dia dalimi, atitinkan\u010dia sprinto tiksl\u0105. \"Scrum\" d\u0117mesys savaranki\u0161kai valdomoms ir organizuojamoms team strukt\u016broms skatina k\u016brybi\u0161kum\u0105 ir inovacijas, tod\u0117l team yra laimingesni ir produktyvesni.<\/p>\n\n\n\n<p>Tarpfunkciniai \u012fg\u016bd\u017eiai, padedantys suma\u017einti kli\u016btis:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Visapusi\u0161kas <a href=\"https:\/\/thecodest.co\/lt\/blog\/how-the-codests-team-extension-model-can-transform-your-in-house-development-team\/\">k\u016brimo paj\u0117gumai<\/a><\/li>\n\n\n\n<li>Testavimo automatizavimo patirtis<\/li>\n\n\n\n<li>\u017dinios apie infrastrukt\u016br\u0105 kaip kod\u0105<\/li>\n\n\n\n<li>Duomen\u0173 baz\u0117s ir duomen\u0173 pipeline \u012fg\u016bd\u017eiai<\/li>\n<\/ul>\n\n\n\n<p>praktika, pavyzd\u017eiui, programavimas poromis, <a href=\"https:\/\/thecodest.co\/lt\/dictionary\/what-is-code-refactoring\/\">kodas<\/a> per\u017ei\u016bros ir k\u016brimas pagal kamien\u0105 padeda kurti team kokyb\u0119 kiekviename sprinte. Programuotojams tenka atsakomyb\u0117 u\u017e atlikt\u0173 darb\u0173 apibr\u0117\u017eimo laikym\u0105si ir sprinto darb\u0173 s\u0105ra\u0161o atnaujinim\u0105, kad b\u016bt\u0173 atspind\u0117ta reali pa\u017eanga. Kai k\u016brimo team kiekvien\u0105 sprint\u0105 pateikia nauding\u0105 produkto prieaug\u012f, visa team \u012fgyja pasitik\u0117jim\u0105 j\u0173 nusp\u0117jamumu.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-scrum-artifacts-in-software-engineering\">\"Scrum\" artefaktai Software Engineering<\/h2>\n\n\n\n<p>\"Scrum\" turi tris pagrindinius artefaktus: produkto darb\u0173 \u017eurnal\u0105, sprinto darb\u0173 \u017eurnal\u0105 ir prieaug\u012f, kurie padeda apibr\u0117\u017eti produkt\u0105 ir jam sukurti reikalingus darbus. Produkto darb\u0173 s\u0105ra\u0161as ir sprinto darb\u0173 s\u0105ra\u0161as i\u0161 esm\u0117s yra team darb\u0173 s\u0105ra\u0161as, kuriame i\u0161samiai apra\u0161omos ir pagal prioritetus i\u0161d\u0117stomos u\u017eduotys, kurias team turi atlikti kuriant produkt\u0105 arba per kiekvien\u0105 sprint\u0105. \u0160ie <strong>Scrum artefaktai<\/strong> u\u017etikrinti, kad \"Scrum\" team ir projekto suinteresuotosioms \u0161alims b\u016bt\u0173 skaidrus darbas ir pa\u017eanga.<\/p>\n\n\n\n<p>Kiekvienas artefaktas turi ai\u0161k\u0173 tiksl\u0105 ir per sprint\u0105 nuolat tobulinamas. Kalbant apie programin\u0119 \u012frang\u0105, artefaktai apima naudotojo istorijas, techninius reikalavimus, nefunkcinius reikalavimus, klaid\u0173 taisymus ir architekt\u016brinius patobulinimus.<\/p>\n\n\n\n<p>Gerai apibr\u0117\u017eta \"Atlikto\" apibr\u0117\u017etis u\u017etikrina, kad pakopos b\u016bt\u0173 tikrai i\u0161leid\u017eiamos - kodas sujungiamas, i\u0161bandomas, dokumentuojamas ir \u012fdiegiamas bent jau \u012f stadijos aplink\u0105. \u0160iuolaikin\u0117s priemon\u0117s, tokios kaip \"Jira\", <a href=\"https:\/\/thecodest.co\/lt\/dictionary\/azure-developer\/\">Azure<\/a> DevOps, ir Linear palaiko \u0161iuos artefaktus lentomis, darbo eigomis ir ataskaitomis, nepaver\u010diant \"Scrum\" grie\u017etu procesu.<\/p>\n\n\n\n<p>Artefakt\u0173 skaidrumo u\u017etikrinimas skatina tiksli\u0105 patikr\u0105 \"Scrum\" rengini\u0173 metu. Kai visi mato t\u0105 pa\u010di\u0105 informacij\u0105, kasdieniai \"scrum\" ir sprinto per\u017ei\u016bros pokalbiai yra pagr\u012fsti realybe, o ne prielaidomis.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-product-backlog\">Produkt\u0173 s\u0105ra\u0161as<\/h3>\n\n\n\n<p>Produkt\u0173 s\u0105ra\u0161as - tai dinami\u0161kas funkcij\u0173, reikalavim\u0173, patobulinim\u0173 ir pataisym\u0173 s\u0105ra\u0161as, kur\u012f produkto savininkas tvarko ir nustato prioritetus, siekdamas maksimaliai padidinti vert\u0119 klientui. Tai yra viso produkto team darb\u0173 s\u0105ra\u0161as, sudaromas pagal verslo vert\u0119, investicij\u0173 gr\u0105\u017e\u0105, rizik\u0105 ir priklausomybes.<\/p>\n\n\n\n<p>Programin\u0117je \u012frangoje tipiniai atsilikimo element\u0173 formatai yra \u0161ie:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Vartotojo istorijos su INVEST savyb\u0117mis<\/li>\n\n\n\n<li>Pri\u0117mimo kriterijai, apibr\u0117\u017eiantys \u201catlikta\u201d<\/li>\n\n\n\n<li>Apskai\u010diavimai istorijos ta\u0161kais<\/li>\n\n\n\n<li>Techniniai smaigaliai tyrimams ir prototip\u0173 k\u016brimui<\/li>\n\n\n\n<li>Prane\u0161imai apie klaidas su atk\u016brimo veiksmais<\/li>\n\n\n\n<li>Technin\u0117s skolos elementai su poveikio vertinimais<\/li>\n<\/ul>\n\n\n\n<p>Reguliariose tobulinimo sesijose (apie 10% team paj\u0117gum\u0173) team nariai ir produkto savininkas kartu aptaria b\u016bsimus elementus, padalina dideles epines dalis ir papildo technines detales. Sveikame produkto darb\u0173 s\u0105ra\u0161e yra gerai patikslint\u0173 element\u0173 bent 1-2 artimiausiems sprintams, tod\u0117l galima skland\u017eiai planuoti b\u016bsimus sprintus.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-sprint-backlog\">Sprinto darb\u0173 s\u0105ra\u0161as<\/h3>\n\n\n\n<p>Sprinto darb\u0173 s\u0105ra\u0161as - tai k\u016brimo grup\u0117s team atrinkt\u0173 element\u0173, kuriuos reikia \u012fgyvendinti per einam\u0105j\u012f sprint\u0105, s\u0105ra\u0161as, kuris sprinto metu gali keistis, ta\u010diau turi b\u016bti i\u0161laikytas pagrindinis sprinto tikslas. J\u012f sudaro atrinkti produkt\u0173 s\u0105ra\u0161o elementai ir j\u0173 \u012fgyvendinimo planas.<\/p>\n\n\n\n<p>Sprinto planavimo metu k\u016br\u0117jai suskirsto pasirinktus elementus \u012f u\u017eduotis:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\u012egyvendinti OAuth2 API galin\u012f ta\u0161k\u0105<\/li>\n\n\n\n<li>Para\u0161ykite prisijungimo srauto integracijos testus<\/li>\n\n\n\n<li>Atnaujinti API dokumentacij\u0105<\/li>\n\n\n\n<li>Konfig\u016bruoti funkcijos v\u0117liav\u0117l\u0119 laipsni\u0161kam diegimui<\/li>\n\n\n\n<li>Nustatykite steb\u0117jimo persp\u0117jimus<\/li>\n<\/ul>\n\n\n\n<p>Sprinto darb\u0173 s\u0105ra\u0161\u0105 turi ir atnaujina k\u016br\u0117jai. Jame atsispindi realiuoju laiku pasiekta pa\u017eanga, kli\u016btys ir bet kokie su produkto savininku suderinti pakeitimai. Apimties poky\u010diai per <strong>dabartinis sprinto ciklas<\/strong> leid\u017eiama tik tuo atveju, jei jie nekelia pavojaus sprinto tikslui arba nevir\u0161ija team paj\u0117gum\u0173.<\/p>\n\n\n\n<p>Sprinto tikslo pavyzdys: \u201c\u012egalinti naudotoj\u0173 registracij\u0105 per OAuth2 naujiems mobiliesiems klientams.\u201d Visi sprinto darb\u0173 s\u0105ra\u0161o punktai tur\u0117t\u0173 b\u016bti suderinti su \u0161iuo tikslu, kad visi vienodai suprast\u0173 prioritetus.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-increment-and-definition-of-done\">Padid\u0117jimas ir apibr\u0117\u017eimas \"Atlikta<\/h3>\n\n\n\n<p>Inkrementas, taip pat \u017einomas kaip sprinto tikslas, yra sprinto galutinis produktas, kuris turi atitikti team apibr\u0117\u017et\u012f, kad b\u016bt\u0173 laikomas u\u017ebaigtu. Tai vis\u0173 u\u017ebaigt\u0173 darb\u0173 s\u0105ra\u0161o element\u0173 suma, sudaranti potencialiai i\u0161leid\u017eiam\u0105 versij\u0105 sprinto pabaigoje.<\/p>\n\n\n\n<p>Programin\u0117s \u012frangos team apibr\u0117\u017eimas \"Atlikta\" gali b\u016bti toks:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><th>Kategorija<\/th><th>Kriterijai<\/th><\/tr><tr><td>Kodo kokyb\u0117<\/td><td>80%+ vieneto test\u0173 apr\u0117ptis, praeinantys linter patikrinimus<\/td><\/tr><tr><td>Per\u017ei\u016br\u0117kite<\/td><td>Patvirtinta tarpusavio kodo per\u017ei\u016bra, saugumo patikra atlikta<\/td><\/tr><tr><td>Testavimas<\/td><td>Integracijos testai \u012fveikiami, na\u0161umo kriterijai \u012fvykdyti<\/td><\/tr><tr><td>Dokumentacija<\/td><td>Atnaujinti API dokumentai, README aktuali<\/td><\/tr><tr><td>\u012ediegimas<\/td><td>\u012ediegta \u012f etapin\u012f diegim\u0105, sukonfig\u016bruoti steb\u0117jimo kabliukai<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>Inkrementas demonstruojamas per sprinto per\u017ei\u016br\u0105, kurios metu suinteresuotosios \u0161alys testuoja funkcionalum\u0105 ir nuolat teikia gr\u012f\u017etam\u0105j\u012f ry\u0161\u012f, kuris gali pakeisti produkt\u0173 s\u0105ra\u0161\u0105. \"Scrum\" suma\u017eina projekto nes\u0117km\u0117s rizik\u0105, nes reguliariai pateikiami ma\u017ei veikiantys programin\u0117s \u012frangos vienetai. Inkrementas gali b\u016bti i\u0161leistas bet kurio sprinto metu arba po jo, kai produkto savininkas nustato pakankam\u0105 verslo vert\u0119 ir priimtin\u0105 technin\u0119 rizik\u0105.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-core-scrum-events-scrum-ceremonies-for-software-teams\">Pagrindiniai \"Scrum\" renginiai (Scrum ceremonijos) programin\u0117s \u012frangos komandoms<\/h2>\n\n\n\n<p>Penki pagrindiniai \"Scrum\" renginiai - \"Sprintas\", \"Sprinto planavimas\", \"Kasdienis \"Scrum\", \"Sprinto per\u017ei\u016bra\" ir \"Sprinto retrospektyva\" - strukt\u016bruoja team laik\u0105 ir u\u017etikrina reguliar\u0173 tikrinim\u0105 bei pritaikym\u0105. Laiko ribojimas \"Scrum\" \u012fvykiuose padeda sutelkti d\u0117mes\u012f, ma\u017eina \u0161vaistym\u0105 ir u\u017etikrina ritm\u0105, grie\u017etai ribodamas susirinkim\u0173 ir sprint\u0173 trukm\u0119.<\/p>\n\n\n\n<p>\u012eprastas 2 savai\u010di\u0173 sprinto laikas:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Sprinto planavimas: iki 4 valand\u0173<\/li>\n\n\n\n<li>Kasdienis \"Scrum\": 15 minu\u010di\u0173<\/li>\n\n\n\n<li>Sprinto ap\u017evalga: iki 2 valand\u0173<\/li>\n\n\n\n<li>Sprinto retrospektyva: iki 1,5 valandos<\/li>\n\n\n\n<li>Nebaigt\u0173 darb\u0173 s\u0105ra\u0161o tobulinimas: vyksta (10% paj\u0117gum\u0173)<\/li>\n<\/ul>\n\n\n\n<p>Programin\u0117s \u012frangos in\u017einerijoje \u0161ie \u012fvykiai glaud\u017eiai susij\u0119 su i\u0161leidimais, kodo \u012f\u0161aldymu ir integracijos testavimo ciklais. Komandos tur\u0117t\u0173 eksperimentuoti su darbotvark\u0117s formatais, ta\u010diau vengti praleisti renginius arba paversti juos projekt\u0173 vadov\u0173 statuso susirinkimais.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-backlog-refinement-organizing-the-backlog\">Darb\u0173 s\u0105ra\u0161o tikslinimas (Darb\u0173 s\u0105ra\u0161o organizavimas)<\/h3>\n\n\n\n<p>\"Backlog\" tikslinimas - tai pasikartojanti darbo sesija (da\u017enai kart\u0105 per savait\u0119), kurios metu produkto savininkas ir programuotojai ai\u0161kinasi, skirsto, vertina ir kei\u010dia prioritetus. \u0160ia veikla parengiami b\u016bsim\u0173 sprint\u0173 elementai, kad sprinto planavimo renginio metu b\u016bt\u0173 galima sutelkti d\u0117mes\u012f \u012f atrank\u0105 ir \u012fsipareigojim\u0105, o ne \u012f atradim\u0105.<\/p>\n\n\n\n<p>Tobulinimo veiklos pavyzd\u017eiai:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>API sutar\u010di\u0173 tarp paslaug\u0173 ai\u0161kinimas<\/li>\n\n\n\n<li>Priklausomyb\u0117s nuo kit\u0173 team nustatymas<\/li>\n\n\n\n<li>Veiklos reikalavim\u0173 pri\u0117mimo test\u0173 prid\u0117jimas<\/li>\n\n\n\n<li>Dideli\u0173 epini\u0173 k\u016brini\u0173 skaidymas \u012f sprinto dyd\u017eio istorijas<\/li>\n\n\n\n<li>Vertinimas naudojant planavimo poker\u012f arba mar\u0161kin\u0117li\u0173 dyd\u017eio nustatym\u0105<\/li>\n<\/ul>\n\n\n\n<p>Patikslinimas anksti atskleid\u017eia rizik\u0105, tod\u0117l architekt\u016bros klausimus galima aptarti dar prie\u0161 \u012fsipareigojant sprintui. Laikykit\u0117s sesij\u0173 laiko rib\u0173 - ne daugiau kaip 10% team paj\u0117gum\u0173, kad i\u0161vengtum\u0117te nesibaigian\u010dio analiz\u0117s paraly\u017eiaus.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-sprint-planning\">Sprinto planavimas<\/h3>\n\n\n\n<p>Sprinto planavimas - tai susitikimas, kuriame visa k\u016brimo grup\u0117 planuoja darbus, kurie bus atliekami per einam\u0105j\u012f sprint\u0105, nustatomas sprinto tikslas ir pasirenkami elementai i\u0161 produkto darb\u0173 s\u0105ra\u0161o. Jame atsakoma, k\u0105 galima pristatyti ir kaip bus atliekamas darbas.<\/p>\n\n\n\n<p>Pagrindiniai sprinto planavimo veiksmai:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Sprinto tikslo k\u016brimas<\/strong>: Ai\u0161kus, glaustas ir su produktu suderintas tikslas <a href=\"https:\/\/thecodest.co\/lt\/blog\/digital-transformation-roadmap\/\">keli\u0173 \u017eem\u0117lapis<\/a> kad visi team nariai ir suinteresuotosios \u0161alys suprast\u0173.<\/li>\n\n\n\n<li><strong>Pasirinkite neatliktus darbus<\/strong>: Remiantis istoriniu grei\u010diu ir team prieinamumu (atostogos, bud\u0117jimai pagal i\u0161kvietim\u0105)<\/li>\n\n\n\n<li><strong>Suskirstykite u\u017eduotis<\/strong>: Techninis po\u017ei\u016bris ir u\u017eduo\u010di\u0173 paskirstymas<\/li>\n\n\n\n<li><strong>Patvirtinkite \u012fsipareigojim\u0105<\/strong>: Visi supranta pasirinktus elementus ir auk\u0161to lygio po\u017ei\u016br\u012f<\/li>\n<\/ol>\n\n\n\n<p>Konkre\u010dios programin\u0117s \u012frangos pavyzd\u017eiai - planavimas integruoti tre\u010diosios \u0161alies mok\u0117jimo API, duomen\u0173 baz\u0117s versijos atnaujinimas ma\u017eo lankomumo metu arba naujos funkcijos v\u0117liavos paleidimas A\/B bandymams. team pateikia team ai\u0161kias gaires, kaip atrodo sprinto s\u0117km\u0117.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-daily-scrum-daily-stand-up\">Kasdienis \"Scrum\" (kasdienis parengiamasis darbas)<\/h3>\n\n\n\n<p>Kasdienis \"Scrum\", dar vadinamas \"stand-up\", yra trumpas susitikimas, vykstantis kiekvien\u0105 sprinto dien\u0105, skirtas patikrinti pa\u017eang\u0105 siekiant sprinto tikslo ir nustatyti kli\u016btis. Jis trunka grie\u017etai 15 minu\u010di\u0173, vyksta kiekvien\u0105 darbo dien\u0105 tuo pa\u010diu metu.<\/p>\n\n\n\n<p>Kasdienis \"Scrum\" susirinkimas skatina atvir\u0105 team nari\u0173 bendravim\u0105, leid\u017eiant\u012f jiems aptarti pa\u017eang\u0105, planuoti dienos darbus ir \u012fvardyti kli\u016btis, su kuriomis jie susiduria. Tai n\u0117ra b\u016bsenos ataskaita Scrum Master - tai k\u016br\u0117j\u0173 tarpusavio sinchronizacija.<\/p>\n\n\n\n<p>Veiksmingos u\u017euominos, neapsiribojan\u010dios klasikiniais trimis klausimais:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\u201cAr vis dar einame sprinto tikslo link?\u201d<\/li>\n\n\n\n<li>\u201cKurios u\u017eduotys yra u\u017eblokuotos arba kurias reikia sujungti?\u201d<\/li>\n\n\n\n<li>\u201cAr yra integracijos ta\u0161k\u0173, kuriuos \u0161iandien turime suderinti?\u201d<\/li>\n<\/ul>\n\n\n\n<p>Praktiniai patarimai: vizualizuokite darb\u0105 lentoje, apsiribokite detali\u0173 problem\u0173 sprendimu ir jas aptarkite tik po kasdieni\u0173 \"scrum\" diskusij\u0173. Nuosekl\u016bs kasdieniai \"scrums\" padeda anksti nustatyti integracijos problemas, k\u016brimo klaidas ir priklausomyb\u0117s rizik\u0105. <strong>Sprintas team<\/strong> siekti tikslo, kasdien pri\u017ei\u016brint, kad visi b\u016bt\u0173 suderinti.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-sprint-review\">Sprinto ap\u017evalga<\/h3>\n\n\n\n<p>Kiekvieno sprinto pabaigoje rengiama sprinto per\u017ei\u016bra, kurios metu team suinteresuotosioms \u0161alims parodo atlikt\u0105 darb\u0105 ir pateikia atsiliepimus, kurie gali tur\u0117ti \u012ftakos kito sprinto planavimui. Pagrindinis artefaktas yra veikianti programin\u0117 \u012franga - venkite skaidri\u0173 lenteli\u0173, pakei\u010dian\u010di\u0173 realias demonstracijas.<\/p>\n\n\n\n<p>Konkret\u016bs gr\u012f\u017etamojo ry\u0161io pavyzd\u017eiai:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Produkt\u0173 valdymo pra\u0161omi UX patobulinimai<\/li>\n\n\n\n<li>Veiklos efektyvumo problemos, apie kurias prane\u0161a operacijos<\/li>\n\n\n\n<li>Nauji teisiniai atitikties reikalavimai<\/li>\n\n\n\n<li>Funkcij\u0173 prioritet\u0173 nustatymo poky\u010diai d\u0117l klient\u0173 s\u0117km\u0117s<\/li>\n<\/ul>\n\n\n\n<p>\"Scrum\" u\u017etikrina greit\u0105 gr\u012f\u017etam\u0105j\u012f ry\u0161\u012f, leid\u017eiant\u012f koreguoti, atsi\u017evelgiant \u012f funkcijos veikim\u0105 v\u0117lesniuose sprintuose. Remdamasis \u0161ia gr\u012f\u017etam\u0105ja informacija, produkto savininkas atnaujina produkt\u0173 s\u0105ra\u0161\u0105. \u012eprastinis 2 savai\u010di\u0173 sprinto laikas - iki 2 valand\u0173. Skatinkite neformalias, interaktyvias diskusijas, o ne formalius pristatymus, kurie neleid\u017eia u\u017eduoti klausim\u0173.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-sprint-retrospective\">Sprinto retrospektyva<\/h3>\n\n\n\n<p>Sprinto retrospektyva - tai sprinto pabaigoje vykstantis susitikimas, kuriame team apm\u0105sto pra\u0117jus\u012f sprint\u0105 ir aptaria, kas pavyko gerai ir k\u0105 b\u016bt\u0173 galima patobulinti b\u016bsimiems sprintams. Tai vidin\u0117 \"Scrum\" team veikla, kurioje daugiausia d\u0117mesio skiriama \u017emon\u0117ms, santykiams, procesui, priemon\u0117ms ir \"Done\" apibr\u0117\u017e\u010diai.<\/p>\n\n\n\n<p>Gerai veikiantys strukt\u016brizuoti formatai:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Paleidimas-i\u0161jungimas-atst\u016bmimas-prat\u0119simas<\/strong>: K\u0105 tur\u0117tume prad\u0117ti daryti, ko nebedaryti, ko neatsisakyti?<\/li>\n\n\n\n<li><strong>Mad-Sad-Glad<\/strong>: Emocin\u0117 reakcija \u012f sprinto var\u017eybas<\/li>\n\n\n\n<li><strong>4Ls<\/strong>: Patiko, i\u0161moko, tr\u016bko, ilg\u0117josi<\/li>\n<\/ul>\n\n\n\n<p>\"Scrum\" didina team bendradarbiavim\u0105 ir produktyvum\u0105, nes kasdien rengiami pasitarimai ir sprinto retrospektyvos skatina bendravim\u0105. Rezultatai tur\u0117t\u0173 apimti konkre\u010dius tobulinimo veiksmus, suplanuotus ateinan\u010diuose sprintuose - \u012fvesti porin\u012f programavim\u0105 rizikingiems moduliams, automatizuoti tam tikrus regresijos testus arba pakoreguoti \"Atlikta\" apibr\u0117\u017et\u012f.<\/p>\n\n\n\n<p>Svarbus psichologinis saugumas: team s\u0105\u017einingai atspindi nes\u0117kmes, techninius \u012fsiskolinimus ir proces\u0173 spragas be kaltinim\u0173. Reguliarus praeities retrospektyvos rezultat\u0173 per\u017ei\u016br\u0117jimas leid\u017eia nuolat tobul\u0117ti, o ne kartoti problemas.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-scrum-values-and-their-impact-on-software-teams\">\"Scrum\" vertyb\u0117s ir j\u0173 poveikis programin\u0117s \u012frangos komandoms<\/h2>\n\n\n\n<p>Penkios \"Scrum\" vertyb\u0117s, kuriomis vadovaujamasi kasdien\u0117je veikloje: \u012fsipareigojimas, dr\u0105sa, susitelkimas, atvirumas ir pagarba. Tai n\u0117ra abstrakt\u016bs idealai - jos daro tiesiogin\u0119 \u012ftak\u0105 techniniams sprendimams, bendravimo modeliams ir reagavimui \u012f incidentus.<\/p>\n\n\n\n<p>\"Scrum\" sistema skatina skaidrum\u0105, kuris stiprina pasitik\u0117jim\u0105 tarp team, produkto savininko ir suinteresuot\u0173j\u0173 \u0161ali\u0173, gerina bendradarbiavim\u0105 ir bendravim\u0105. Vertyb\u0117s siejasi su scrum renginiais: atvirumas per kasdienius scrumus, pagarba ir dr\u0105sa per retrospektyvas, \u012fsipareigojimas ir susitelkimas planuojant ir vykdant sprint\u0105.<\/p>\n\n\n\n<p>Kai team spaud\u017eia terminai, nuo ver\u010di\u0173 priklauso, ar bus suma\u017einti kampai, ar problemos i\u0161kils \u012f pavir\u0161i\u0173. \"Scrum\" skatina bendradarbiavimo kult\u016br\u0105, skatindama team narius dirbti kartu, dalytis \u017einiomis ir pad\u0117ti vieni kitiems siekti sprinto tiksl\u0173.<\/p>\n\n\n\n<p>Komandos tur\u0117t\u0173 periodi\u0161kai per\u017ei\u016br\u0117ti, kaip joms sekasi \u012fgyvendinti \u0161ias vertybes, ir nustatyti kult\u016brinius poky\u010dius, reikalingus \u0161ioms vertyb\u0117ms stiprinti. Scrum team efektyvumas priklauso nuo to, ar vertyb\u0117s yra praktikuojamos, o ne tik deklaruojamos.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-commitment-and-focus\">\u012esipareigojimas ir susitelkimas<\/h3>\n\n\n\n<p>\u012esipareigojimas rei\u0161kia, kad kiekvienas b\u016brelio narys prisiima atsakomyb\u0119 u\u017e sprinto tiksl\u0105, o ne tik u\u017e atskiras u\u017eduotis. Tai taip pat rei\u0161kia, kad reikia vengti pernelyg didelio \u012fsipareigojimo d\u0117l nerealios apimties, nes tai lemia team nes\u0117km\u0119.<\/p>\n\n\n\n<p>D\u0117mes\u012f remia:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>I\u0161taisytos sprinto laiko juostos, ribojan\u010dios konteksto perjungim\u0105<\/li>\n\n\n\n<li>Nebaigtos gamybos apribojimai, neleid\u017eiantys i\u0161 dalies u\u017ebaigti darbus<\/li>\n\n\n\n<li>Ai\u0161k\u016bs gamybos incident\u0173 r\u016b\u0161iavimo procesai<\/li>\n\n\n\n<li>Prireikus budintys in\u017einieriai<\/li>\n<\/ul>\n\n\n\n<p>D\u0117mesio apsaugos pavyzd\u017eiai - ad hoc u\u017eklaus\u0173 ma\u017einimas sprinto metu ir tvaraus tempo palaikymas (vengiant nuolatini\u0173 vir\u0161valand\u017ei\u0173). Susitelkim\u0105 matuokite paprastais rodikliais: WIP limitai ir neplanuoto darbo procentin\u0117 dalis per sprint\u0105. Scrum team geriausiai veikia, kai yra apsaugotas nuo nuolatini\u0173 trukd\u017ei\u0173.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-courage-openness-and-respect\">Dr\u0105sa, atvirumas ir pagarba<\/h3>\n\n\n\n<p>Dr\u0105sa rei\u0161kia, kad reikia atskleisti technin\u0119 rizik\u0105, pripa\u017einti klaidas (pvz., klaiding\u0105 diegim\u0105) ir u\u017egin\u010dyti nerealius terminus ar trumpesnius kelius, kurie kenkia kokybei. <strong>Programin\u0117s \u012frangos k\u016br\u0117jai<\/strong> kurie jau\u010diasi saug\u016bs ir anksti pastebi problemas.<\/p>\n\n\n\n<p>Atvirumas reikalauja skaidraus bendravimo apie pa\u017eang\u0105, trukd\u017eius ir tr\u016bkumus. Tai padeda u\u017etikrinti matomos lentos, bendri prietais\u0173 skydeliai ir prieinami dokumentai. . <strong>\"Scrum\" vadovas<\/strong> pabr\u0117\u017eia, kad skaidrumas suteikia galimyb\u0119 atlikti patikrinimus ir prisitaikyti.<\/p>\n\n\n\n<p>Gerbkite visus vaidmenis - k\u016br\u0117jus, testuotojus, Scrum Master, produkto savinink\u0105 - pripa\u017eindami, kad kokybi\u0161kai programinei \u012frangai reikalingas bendradarbiavimas, o ne pavieni\u0173 asmen\u0173 \u017eygdarbiai. Pagarbi kodo per\u017ei\u016bra u\u017etikrina konstruktyv\u0173 gr\u012f\u017etam\u0105j\u012f ry\u0161\u012f ir dalijim\u0105si \u017einiomis. Tarpusavio team integracijos darbui naudingas teigiamas ketinimas.<\/p>\n\n\n\n<p>\u0160ios vertyb\u0117s sukuria aplink\u0105, kurioje klesti nuolatinis tobul\u0117jimas ir inovacijos, o tai yra labai svarbu, kad <strong>projekto s\u0117km\u0117<\/strong> sud\u0117tingoje programin\u0117s \u012frangos in\u017einerijoje.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-scrum-vs-kanban-and-hybrid-approaches-in-software-engineering\">\"Scrum\" vs. \"Kanban\" ir hibridiniai metodai Software Engineering<\/h2>\n\n\n\n<p>\"Scrum\" naudoja laiko ribas atitinkan\u010dius sprintus, fiksuotus vaidmenis ir apibr\u0117\u017etus \u012fvykius. Kanban akcentuoja nenutr\u016bkstam\u0105 sraut\u0105, WIP limitus, nenustatytus vaidmenis ir terminus. Kiekvienas metodas tinka skirtingoms aplinkyb\u0117ms.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><th>Aspektas<\/th><th>Scrum<\/th><th>Kanban<\/th><\/tr><tr><td>Iteracijos<\/td><td>Fiksuoti sprintai (1-4 savait\u0117s)<\/td><td>Nenutr\u016bkstamas srautas<\/td><\/tr><tr><td>Vaidmenys<\/td><td>PO, SM, k\u016br\u0117jai<\/td><td>Nenustatyta<\/td><\/tr><tr><td>Planavimas<\/td><td>Sprinto planavimo sesijos<\/td><td>Pagal pareikalavim\u0105<\/td><\/tr><tr><td>Pakeitimai<\/td><td>Pageidautina tarp sprint\u0173<\/td><td>Bet kuriuo metu<\/td><\/tr><tr><td>Geriausiai tinka<\/td><td>Funkcij\u0173 k\u016brimas<\/td><td>Operacijos, technin\u0117 prie\u017ei\u016bra, palaikymas<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>Hibridiniai metodai, tokie kaip \"Scrumban\" ar \"Kanplan\", sujungia strukt\u016brizuot\u0105 sprinto planavim\u0105 ir per\u017ei\u016br\u0105 su \"Kanban\" stiliaus srautais ir WIP apribojimais. A <a href=\"https:\/\/thecodest.co\/lt\/blog\/maximize-your-product-vision-workshops\/\">produkt\u0173 komanda<\/a> galb\u016bt naudoja \"Scrum\" nauj\u0173 funkcij\u0173 k\u016brimui, o papildoma pagalbin\u0117 priemon\u0117 team naudoja \"Kanban\" gamybos incidentams tvarkyti, su bendru matomumu visose valdybose.<\/p>\n\n\n\n<p>Pasirinkite arba sumai\u0161ykite sistemas pagal team dyd\u012f, gaunam\u0173 darb\u0173 nepastovum\u0105 ir i\u0161leidimo nusp\u0117jamumo poreik\u012f. \"Scrum\" praktika tinka, kai suinteresuotosioms \u0161alims reikia reguliariai demonstruoti rezultatus; \"Kanban\" tinka, kai darbai gaunami nenusp\u0117jamai.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-benefits-and-challenges-of-scrum-in-software-engineering\">\"Scrum\" privalumai ir i\u0161\u0161\u016bkiai Software Engineering<\/h2>\n\n\n\n<p>\"Scrum\" suteikia ai\u0161ki\u0105 naud\u0105 - greitesn\u012f gr\u012f\u017etam\u0105j\u012f ry\u0161\u012f, geresn\u012f suderinamum\u0105 su klientais ir geresn\u012f pristatymo nusp\u0117jamum\u0105, ta\u010diau kyla sunkum\u0173, kai ji neteisingai suprantama arba blogai \u012fgyvendinama. S\u0117kmingam sprinto u\u017ebaigimui reikia ir sistemos supratimo, ir organizacinio palaikymo.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-quality-metrics-and-customer-satisfaction\">Kokyb\u0117, rodikliai ir klient\u0173 pasitenkinimas<\/h3>\n\n\n\n<p>D\u0117l trump\u0173 sprint\u0173 ir reguliaraus derinimo \"Scrum\" leid\u017eia team greitai reaguoti \u012f naujus reikalavimus ir poky\u010dius, tod\u0117l nuolat \u012ftraukiamas gr\u012f\u017etamasis ry\u0161ys. Kokyb\u0117 ger\u0117ja d\u0117l to, kad testavimas, kodo per\u017ei\u016bra ir nuolatin\u0117 integracija \u012ftraukiami \u012f sprinto darbo eig\u0105, o ne laikomi atskiru etapu.<\/p>\n\n\n\n<p>Naudingos \"agile\" metrikos <a href=\"https:\/\/thecodest.co\/lt\/dictionary\/what-is-the-role-of-project-management-in-software-development\/\">projekt\u0173 valdymas<\/a> sistemos steb\u0117jimas:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Sprinto grei\u010dio tendencijos (paprastai 20-40 ta\u0161k\u0173 per sprint\u0105, kai jis stabilus)<\/li>\n\n\n\n<li>Parengimo laikas ir ciklo trukm\u0117<\/li>\n\n\n\n<li>Defekt\u0173 tankis ir i\u0161nyk\u0119 defektai (&lt;5% tikslas)<\/li>\n\n\n\n<li>Klient\u0173 pasitenkinimo balai, gauti i\u0161 atsiliepim\u0173 apie i\u0161leidim\u0105<\/li>\n<\/ul>\n\n\n\n<p>Sprinto ap\u017evalgos ir da\u017eni i\u0161leidimai didina klient\u0173 pasitenkinim\u0105, nes parodo pa\u017eang\u0105 ir leid\u017eia klientams daryti \u012ftak\u0105 veiksm\u0173 planui. Retrospektyv\u0173 metu rodiklius naudokite kaip mokymosi priemones, o ne kaip veiklos tikslus, kuriais galima \u017eaisti.<\/p>\n\n\n\n<p>Kai kurie teigia, kad naudojant \"Scrum\" padid\u0117ja 200-400% na\u0161umas, o apklausos rodo 95% laiku pristatyt\u0173 darb\u0173 rodiklius, kai jie tinkamai \u012fgyvendinami. Ta\u010diau \"Scrum\" i\u0161\u0161\u016bki\u0173 gali kilti d\u0117l masto didinimo problem\u0173, neplanuoto darbo, neai\u0161ki\u0173 prioritet\u0173 ir standart\u0173 tr\u016bkumo, o tai gali trukdyti efektyviam \u012fgyvendinimui. Apie 58% \"Scrum\" diegimo sunkum\u0173 kyla d\u0117l prasto mokymo.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-organizational-structure-and-scaling-scrum\">Organizacin\u0117 strukt\u016bra ir \"Scrum\" masto didinimas<\/h3>\n\n\n\n<p>\"Scrum\" poveikis organizacinei strukt\u016brai da\u017enai rei\u0161kia, kad vietoj laikin\u0173 projekt\u0173 team formuojamos ilgalaik\u0117s tarpfunkcin\u0117s produkto team. Tyrimai rodo, kad ilgalaik\u0117s produkto team grup\u0117s padidina darbuotoj\u0173 i\u0161laikym\u0105 ma\u017edaug 30%.<\/p>\n\n\n\n<p>Norint i\u0161pl\u0117sti iki keli\u0173 team, reikia:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Bendr\u0173 produkt\u0173 tiksl\u0173 ir integruot\u0173 darb\u0173 plan\u0173 derinimas<\/li>\n\n\n\n<li>Nuosekli s\u0105vokos \"Atlikta\" apibr\u0117\u017etis visose team<\/li>\n\n\n\n<li>Reguliari kry\u017emin\u0117-team sinchronizacija priklausomybi\u0173 valdymui<\/li>\n\n\n\n<li>Praktikos bendruomen\u0117s, u\u017etikrinan\u010dios technin\u012f nuoseklum\u0105<\/li>\n<\/ul>\n\n\n\n<p>D\u0117l fiksuoto \"Scrum\" sprint\u0173 laiko kartais gali b\u016bti pamir\u0161ti svarb\u016bs projekto aspektai, nes per ribot\u0105 laik\u0105 gali b\u016bti \u012fgyvendinti ne visi reikalavimai. Siekiant u\u017ekirsti keli\u0105 technin\u0117ms skoloms kauptis, reikia skirti apie 20% paj\u0117gum\u0173.<\/p>\n\n\n\n<p>Pl\u0117skite palaipsniui: prad\u0117kite nuo vieno ar dviej\u0173 team, nuodugniai i\u0161mokite \"Scrum\", tada i\u0161pl\u0117skite praktik\u0105. Didel\u0117s pertvarkos paprastai b\u016bna sud\u0117tingos. In\u017einieriams team naudingas instruktavimas ir bandomasis diegimas, kuris parodo s\u0117km\u0119 prie\u0161 pradedant taikyti pla\u010diau.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-getting-started-with-scrum-in-your-software-team\">\"Scrum\" prad\u017eia j\u016bs\u0173 programin\u0117s \u012frangos komandoje<\/h2>\n\n\n\n<p>Ar esate pasireng\u0119 taikyti \"Scrum\"? \u0160tai praktin\u0117 seka:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Sukurti tarpfunkcin\u012f team<\/strong>&nbsp;5-9 \u017emoni\u0173, turin\u010di\u0173 vis\u0173 reikiam\u0173 \u012fg\u016bd\u017ei\u0173, kad gal\u0117t\u0173 teikti<\/li>\n\n\n\n<li><strong>Paskirkite produkto savinink\u0105<\/strong>&nbsp;atskaitomyb\u0117 u\u017e atsilikimo ir vert\u0117s sprendimus.<\/li>\n\n\n\n<li><strong>Pasirinkite arba apmokykite Scrum Master<\/strong>&nbsp;treniruoti team ir palengvinti renginius.<\/li>\n\n\n\n<li><strong>Apibr\u0117\u017ekite pradin\u012f produkt\u0173 s\u0105ra\u0161\u0105<\/strong>&nbsp;su prioritetiniais elementais, paruo\u0161tais sprintams.<\/li>\n\n\n\n<li><strong>Prad\u0117kite nuo 2 savai\u010di\u0173 sprinto<\/strong>&nbsp;optimaliai subalansuoti gr\u012f\u017etam\u0105j\u012f ry\u0161\u012f ir planavimo prid\u0117tines i\u0161laidas.<\/li>\n<\/ol>\n\n\n\n<p>I\u0161 prad\u017ei\u0173 naudokite minimalias priemones - pakanka paprastos lentos ir pagrindinio atsilikimo \u012frankio. Automatizuotas metrik\u0173 lenteles prid\u0117kite tik tada, kai to reikia d\u0117l konkre\u010di\u0173 skaud\u017ei\u0173 viet\u0173.<\/p>\n\n\n\n<p>Investuokite \u012f \"scrum\" team nari\u0173 mokymus, ypa\u010d \u012f Scrum Master ir produkto savininko vaidmenis. Prie\u0161 priimdami svarbius procesinius sprendimus, prad\u0117kite nuo bandomojo projekto, vykdydami bent 3-4 sprintus. Retrospektyvos nuo pat pirmojo sprinto leid\u017eia nuolat tobul\u0117ti, atsi\u017evelgiant \u012f j\u016bs\u0173 team kontekst\u0105 ir produkto poreikius.<\/p>\n\n\n\n<p>Projekt\u0173 valdymas naudojant \"Scrum\" reikalauja kantryb\u0117s. I\u0161mokite \"Scrum\" pagrind\u0173, nuosekliai praktikuokit\u0117s ir prisitaikykite pagal tai, k\u0105 pasteb\u0117jote.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-faq\">DUK<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-how-long-should-a-sprint-be-for-a-software-engineering-team\">Kiek laiko tur\u0117t\u0173 trukti sprintas programin\u0117s \u012frangos in\u017einerijoje team?<\/h3>\n\n\n\n<p>Dauguma programin\u0117s \u012frangos team pasirenka 1-4 savai\u010di\u0173 sprinto trukm\u0119, o 2026 m. da\u017eniausiai pasirenkamos 2 savait\u0117s, nes taip suderinamas gr\u012f\u017etamojo ry\u0161io greitis ir planavimo i\u0161laidos. Rinkdamiesi atsi\u017evelkite \u012f diegimo da\u017enum\u0105, suinteresuot\u0173j\u0173 \u0161ali\u0173 galimybes dalyvauti per\u017ei\u016brose ir tipin\u012f reik\u0161ming\u0173 prieaugi\u0173 dyd\u012f.<\/p>\n\n\n\n<p>Nustat\u0119 sprinto trukm\u0119 i\u0161laikykite stabili\u0105. Po keli\u0173 sprint\u0173 persvarstykite tik tada, jei yra ai\u0161ki\u0173 \u012frodym\u0173, kad kitokia trukm\u0117 pagerint\u0173 rezultatus. Komandos, turin\u010dios greitesni\u0173 diegimo galimybi\u0173, kartais naudoja 1 savait\u0117s sprintus; komandos, turin\u010dios sud\u0117ting\u0173 integracijos poreiki\u0173, gali rinktis 3-4 savai\u010di\u0173 sprintus.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-can-scrum-be-used-for-maintenance-and-operations-work\">Ar \"Scrum\" gali b\u016bti naudojamas technin\u0117s prie\u017ei\u016bros ir eksploatavimo darbams?<\/h3>\n\n\n\n<p><a href=\"https:\/\/thecodest.co\/en\/dictionary\/scrum\/\">Scrum<\/a> gali b\u016bti pritaikytas funkcij\u0173 k\u016brimui ir techninei prie\u017ei\u016brai, ta\u010diau dideliam nenusp\u0117jamo operatyvinio darbo kiekiui geriau tinka \"Kanban\" arba mi\u0161rus modelis. Apsvarstykite galimyb\u0119 kiekvien\u0105 sprint\u0105 rezervuoti fiksuot\u0105 team talpos bufer\u012f (15-20%) neplanuotiems darbams.<\/p>\n\n\n\n<p>Rotuojamas budintis in\u017einierius, sprend\u017eiantis skubius klausimus, gali apsaugoti likusius team sprinto \u012fsipareigojimus. Kad ir kok\u012f metod\u0105 naudotum\u0117te, i\u0161saugokite ai\u0161k\u0173 sprinto tiksl\u0105, o ne nuolat trikdykite \u012fsipareigot\u0105 darb\u0105.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-do-all-scrum-teams-need-a-dedicated-scrum-master\">Ar visiems \"Scrum\" team reikia specialaus Scrum Master?<\/h3>\n\n\n\n<p>Specialus Scrum Master idealiai tinka, ypa\u010d mokantis \"Scrum\" arba dirbant sud\u0117tingoje aplinkoje. Ma\u017eesn\u0117se organizacijose vienas Scrum Master gali aptarnauti 2-3 team arba team narys gali prisiimti atsakomyb\u0119 ne vis\u0105 darbo dien\u0105, ta\u010diau tam reikia disciplinos.<\/p>\n\n\n\n<p>Jei vaidmuo per daug i\u0161skaidomas, team gr\u012f\u017eta prie sen\u0173 \u012fpro\u010di\u0173 ir praranda \"Scrum\" naud\u0105. Siekiant pagerinti team veikl\u0105, Scrum Master trenerio, kli\u016b\u010di\u0173 \u0161alinimo ir palengvinimo pareigos nusipelno realaus laiko ir d\u0117mesio.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-how-does-scrum-handle-technical-debt-and-architecture-work\">Kaip \"Scrum\" sprend\u017eia technini\u0173 skol\u0173 ir architekt\u016bros klausimus?<\/h3>\n\n\n\n<p>Technin\u0117s skolos ir architekt\u016briniai patobulinimai tur\u0117t\u0173 b\u016bti ai\u0161kiai \u012ftraukti \u012f produkt\u0173 s\u0105ra\u0161\u0105 ir jiems tur\u0117t\u0173 b\u016bti teikiamas prioritetas kartu su funkcijomis. Daugelis team 15-30% sprinto paj\u0117gum\u0173 skiria pertvarkymui, na\u0161umo derinimui ir infrastrukt\u016bros atnaujinimui.<\/p>\n\n\n\n<p>Technini\u0173 skol\u0173 ignoravimas l\u0117tina b\u016bsimus sprintus ir ma\u017eina kokyb\u0119. Produkto savininkas ir programuotojai turi glaud\u017eiai bendradarbiauti, kad suderint\u0173 naujas funkcijas ir technin\u0119 b\u016bkl\u0119. Padarykite skol\u0105 matom\u0105, \u012fvertinkite jos poveik\u012f ir palaipsniui spr\u0119skite j\u0105 per kit\u0105 sprint\u0105 ir v\u0117liau.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-what-tools-are-commonly-used-by-scrum-software-teams\">Kokius \u012frankius da\u017eniausiai naudoja \"Scrum\" programin\u0117s \u012frangos team?<\/h3>\n\n\n\n<p>\u012eprastos \u012franki\u0173 kategorijos yra \u0161ios:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Problem\u0173 steb\u0117jimas ir nei\u0161spr\u0119st\u0173 klausim\u0173<\/strong>: \"Jira\", \"Azure\" DevOps, \"Linear\", \"Asana<\/li>\n\n\n\n<li><strong>Kod\u0173 priegloba ir per\u017ei\u016bra<\/strong>: \"GitHub\", \"GitLab\", \"Bitbucket<\/li>\n\n\n\n<li><strong>CI\/CD pipelines<\/strong>: \"Jenkins\", \"GitHub\" veiksmai, \"CircleCI<\/li>\n\n\n\n<li><strong>Bendravimas<\/strong>: \"Slack\", \"Microsoft Teams\" (ypa\u010d nutolusiems team)<\/li>\n<\/ul>\n\n\n\n<p>\u012erankiai tur\u0117t\u0173 pad\u0117ti kurti matomus atsilikimo planus, ai\u0161kius sprinto planus ir skaidrius rodiklius, ta\u010diau patys netur\u0117t\u0173 tapti d\u0117mesio centre. Prad\u0117kite nuo paprast\u0173 priemoni\u0173, o sud\u0117tingum\u0105 didinkite tik tada, kai jos pad\u0117s i\u0161spr\u0119sti konkre\u010dius skaudulius j\u016bs\u0173 \"Scrum\" procese. Scrum modelis nenurodo konkre\u010di\u0173 \u012franki\u0173 - team pasirenka tai, kas tinka j\u0173 kontekstui.<\/p>\n\n\n\n<p><a href=\"https:\/\/calendar.google.com\/calendar\/u\/0\/appointments\/schedules\/AcZssZ1yVHCQbP3sxc8iCBXZMC_rbd8Tay51Xd85LAM_UK16mhr0HaFeNSaS8Y20gac636RetGdQW-8A\"><br><br><\/a><\/p>","protected":false},"excerpt":{"rendered":"<p>If your software team struggles with shifting requirements, missed deadlines, or disconnected stakeholders, you\u2019re not alone. scrum in software engineering is an agile framework particularly effective for developing complex products, thanks to its iterative processes, transparency, and adaptability. This guide breaks down exactly how Scrum works, who does what, and how to implement it effectively [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":11169,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[10],"tags":[20],"class_list":["post-11167","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-project-management","tag-software-development"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.3 (Yoast SEO v27.3) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Scrum in Software Engineering - The Codest<\/title>\n<meta name=\"description\" content=\"Learn how scrum in software engineering improves project management, adaptability, and transparency in product development.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/thecodest.co\/lt\/tinklarastis\/scrum-programines-irangos-inzinerijoje\/\" \/>\n<meta property=\"og:locale\" content=\"lt_LT\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Scrum in Software Engineering\" \/>\n<meta property=\"og:description\" content=\"Learn how scrum in software engineering improves project management, adaptability, and transparency in product development.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/thecodest.co\/lt\/tinklarastis\/scrum-programines-irangos-inzinerijoje\/\" \/>\n<meta property=\"og:site_name\" content=\"The Codest\" \/>\n<meta property=\"article:published_time\" content=\"2025-05-19T15:37:16+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-05-19T13:37:24+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/thecodest.co\/app\/uploads\/2026\/05\/scrum-in-software-engineering.png\" \/>\n\t<meta property=\"og:image:width\" content=\"960\" \/>\n\t<meta property=\"og:image:height\" content=\"540\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"thecodest\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"thecodest\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"20 minu\u010di\u0173\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/scrum-in-software-engineering\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/scrum-in-software-engineering\\\/\"},\"author\":{\"name\":\"thecodest\",\"@id\":\"https:\\\/\\\/thecodest.co\\\/#\\\/schema\\\/person\\\/7e3fe41dfa4f4e41a7baad4c6e0d4f76\"},\"headline\":\"Scrum in Software Engineering\",\"datePublished\":\"2025-05-19T15:37:16+00:00\",\"dateModified\":\"2026-05-19T13:37:24+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/scrum-in-software-engineering\\\/\"},\"wordCount\":4525,\"publisher\":{\"@id\":\"https:\\\/\\\/thecodest.co\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/scrum-in-software-engineering\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/thecodest.co\\\/app\\\/uploads\\\/2026\\\/05\\\/scrum-in-software-engineering.png\",\"keywords\":[\"software development\"],\"articleSection\":[\"Project Management\"],\"inLanguage\":\"lt-LT\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/scrum-in-software-engineering\\\/\",\"url\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/scrum-in-software-engineering\\\/\",\"name\":\"Scrum in Software Engineering - The Codest\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/thecodest.co\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/scrum-in-software-engineering\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/scrum-in-software-engineering\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/thecodest.co\\\/app\\\/uploads\\\/2026\\\/05\\\/scrum-in-software-engineering.png\",\"datePublished\":\"2025-05-19T15:37:16+00:00\",\"dateModified\":\"2026-05-19T13:37:24+00:00\",\"description\":\"Learn how scrum in software engineering improves project management, adaptability, and transparency in product development.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/scrum-in-software-engineering\\\/#breadcrumb\"},\"inLanguage\":\"lt-LT\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/thecodest.co\\\/blog\\\/scrum-in-software-engineering\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"lt-LT\",\"@id\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/scrum-in-software-engineering\\\/#primaryimage\",\"url\":\"https:\\\/\\\/thecodest.co\\\/app\\\/uploads\\\/2026\\\/05\\\/scrum-in-software-engineering.png\",\"contentUrl\":\"https:\\\/\\\/thecodest.co\\\/app\\\/uploads\\\/2026\\\/05\\\/scrum-in-software-engineering.png\",\"width\":960,\"height\":540,\"caption\":\"Illustration by The Codest showing circular arrows surrounding a gear icon, symbolizing agile workflows, iteration cycles, and Scrum processes in software engineering.\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/scrum-in-software-engineering\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/thecodest.co\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Scrum in Software Engineering\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/thecodest.co\\\/#website\",\"url\":\"https:\\\/\\\/thecodest.co\\\/\",\"name\":\"The Codest\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/thecodest.co\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/thecodest.co\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"lt-LT\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/thecodest.co\\\/#organization\",\"name\":\"The Codest\",\"url\":\"https:\\\/\\\/thecodest.co\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"lt-LT\",\"@id\":\"https:\\\/\\\/thecodest.co\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/thecodest.co\\\/app\\\/uploads\\\/2024\\\/03\\\/thecodest-logo.svg\",\"contentUrl\":\"https:\\\/\\\/thecodest.co\\\/app\\\/uploads\\\/2024\\\/03\\\/thecodest-logo.svg\",\"width\":144,\"height\":36,\"caption\":\"The Codest\"},\"image\":{\"@id\":\"https:\\\/\\\/thecodest.co\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/pl.linkedin.com\\\/company\\\/codest\",\"https:\\\/\\\/clutch.co\\\/profile\\\/codest\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/thecodest.co\\\/#\\\/schema\\\/person\\\/7e3fe41dfa4f4e41a7baad4c6e0d4f76\",\"name\":\"thecodest\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"lt-LT\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/5dbfe6a1e8c86e432e8812759e34e6fe82ebac75119ae3237a6c1311fa19caf4?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/5dbfe6a1e8c86e432e8812759e34e6fe82ebac75119ae3237a6c1311fa19caf4?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/5dbfe6a1e8c86e432e8812759e34e6fe82ebac75119ae3237a6c1311fa19caf4?s=96&d=mm&r=g\",\"caption\":\"thecodest\"},\"url\":\"https:\\\/\\\/thecodest.co\\\/lt\\\/author\\\/thecodest\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"\"Scrum\" Software Engineering - The Codest","description":"Su\u017einokite, kaip \"scrum\" programin\u0117s \u012frangos in\u017einerijoje pagerina projekt\u0173 valdym\u0105, pritaikomum\u0105 ir skaidrum\u0105 kuriant produktus.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/thecodest.co\/lt\/tinklarastis\/scrum-programines-irangos-inzinerijoje\/","og_locale":"lt_LT","og_type":"article","og_title":"Scrum in Software Engineering","og_description":"Learn how scrum in software engineering improves project management, adaptability, and transparency in product development.","og_url":"https:\/\/thecodest.co\/lt\/tinklarastis\/scrum-programines-irangos-inzinerijoje\/","og_site_name":"The Codest","article_published_time":"2025-05-19T15:37:16+00:00","article_modified_time":"2026-05-19T13:37:24+00:00","og_image":[{"width":960,"height":540,"url":"https:\/\/thecodest.co\/app\/uploads\/2026\/05\/scrum-in-software-engineering.png","type":"image\/png"}],"author":"thecodest","twitter_card":"summary_large_image","twitter_misc":{"Written by":"thecodest","Est. reading time":"20 minu\u010di\u0173"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/thecodest.co\/blog\/scrum-in-software-engineering\/#article","isPartOf":{"@id":"https:\/\/thecodest.co\/blog\/scrum-in-software-engineering\/"},"author":{"name":"thecodest","@id":"https:\/\/thecodest.co\/#\/schema\/person\/7e3fe41dfa4f4e41a7baad4c6e0d4f76"},"headline":"Scrum in Software Engineering","datePublished":"2025-05-19T15:37:16+00:00","dateModified":"2026-05-19T13:37:24+00:00","mainEntityOfPage":{"@id":"https:\/\/thecodest.co\/blog\/scrum-in-software-engineering\/"},"wordCount":4525,"publisher":{"@id":"https:\/\/thecodest.co\/#organization"},"image":{"@id":"https:\/\/thecodest.co\/blog\/scrum-in-software-engineering\/#primaryimage"},"thumbnailUrl":"https:\/\/thecodest.co\/app\/uploads\/2026\/05\/scrum-in-software-engineering.png","keywords":["software development"],"articleSection":["Project Management"],"inLanguage":"lt-LT"},{"@type":"WebPage","@id":"https:\/\/thecodest.co\/blog\/scrum-in-software-engineering\/","url":"https:\/\/thecodest.co\/blog\/scrum-in-software-engineering\/","name":"\"Scrum\" Software Engineering - The Codest","isPartOf":{"@id":"https:\/\/thecodest.co\/#website"},"primaryImageOfPage":{"@id":"https:\/\/thecodest.co\/blog\/scrum-in-software-engineering\/#primaryimage"},"image":{"@id":"https:\/\/thecodest.co\/blog\/scrum-in-software-engineering\/#primaryimage"},"thumbnailUrl":"https:\/\/thecodest.co\/app\/uploads\/2026\/05\/scrum-in-software-engineering.png","datePublished":"2025-05-19T15:37:16+00:00","dateModified":"2026-05-19T13:37:24+00:00","description":"Su\u017einokite, kaip \"scrum\" programin\u0117s \u012frangos in\u017einerijoje pagerina projekt\u0173 valdym\u0105, pritaikomum\u0105 ir skaidrum\u0105 kuriant produktus.","breadcrumb":{"@id":"https:\/\/thecodest.co\/blog\/scrum-in-software-engineering\/#breadcrumb"},"inLanguage":"lt-LT","potentialAction":[{"@type":"ReadAction","target":["https:\/\/thecodest.co\/blog\/scrum-in-software-engineering\/"]}]},{"@type":"ImageObject","inLanguage":"lt-LT","@id":"https:\/\/thecodest.co\/blog\/scrum-in-software-engineering\/#primaryimage","url":"https:\/\/thecodest.co\/app\/uploads\/2026\/05\/scrum-in-software-engineering.png","contentUrl":"https:\/\/thecodest.co\/app\/uploads\/2026\/05\/scrum-in-software-engineering.png","width":960,"height":540,"caption":"Illustration by The Codest showing circular arrows surrounding a gear icon, symbolizing agile workflows, iteration cycles, and Scrum processes in software engineering."},{"@type":"BreadcrumbList","@id":"https:\/\/thecodest.co\/blog\/scrum-in-software-engineering\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/thecodest.co\/"},{"@type":"ListItem","position":2,"name":"Scrum in Software Engineering"}]},{"@type":"WebSite","@id":"https:\/\/thecodest.co\/#website","url":"https:\/\/thecodest.co\/","name":"The Codest","description":"","publisher":{"@id":"https:\/\/thecodest.co\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/thecodest.co\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"lt-LT"},{"@type":"Organization","@id":"https:\/\/thecodest.co\/#organization","name":"The Codest","url":"https:\/\/thecodest.co\/","logo":{"@type":"ImageObject","inLanguage":"lt-LT","@id":"https:\/\/thecodest.co\/#\/schema\/logo\/image\/","url":"https:\/\/thecodest.co\/app\/uploads\/2024\/03\/thecodest-logo.svg","contentUrl":"https:\/\/thecodest.co\/app\/uploads\/2024\/03\/thecodest-logo.svg","width":144,"height":36,"caption":"The Codest"},"image":{"@id":"https:\/\/thecodest.co\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/pl.linkedin.com\/company\/codest","https:\/\/clutch.co\/profile\/codest"]},{"@type":"Person","@id":"https:\/\/thecodest.co\/#\/schema\/person\/7e3fe41dfa4f4e41a7baad4c6e0d4f76","name":"thecodest","image":{"@type":"ImageObject","inLanguage":"lt-LT","@id":"https:\/\/secure.gravatar.com\/avatar\/5dbfe6a1e8c86e432e8812759e34e6fe82ebac75119ae3237a6c1311fa19caf4?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/5dbfe6a1e8c86e432e8812759e34e6fe82ebac75119ae3237a6c1311fa19caf4?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/5dbfe6a1e8c86e432e8812759e34e6fe82ebac75119ae3237a6c1311fa19caf4?s=96&d=mm&r=g","caption":"thecodest"},"url":"https:\/\/thecodest.co\/lt\/author\/thecodest\/"}]}},"_links":{"self":[{"href":"https:\/\/thecodest.co\/lt\/wp-json\/wp\/v2\/posts\/11167","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/thecodest.co\/lt\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/thecodest.co\/lt\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/thecodest.co\/lt\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/thecodest.co\/lt\/wp-json\/wp\/v2\/comments?post=11167"}],"version-history":[{"count":2,"href":"https:\/\/thecodest.co\/lt\/wp-json\/wp\/v2\/posts\/11167\/revisions"}],"predecessor-version":[{"id":11181,"href":"https:\/\/thecodest.co\/lt\/wp-json\/wp\/v2\/posts\/11167\/revisions\/11181"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/thecodest.co\/lt\/wp-json\/wp\/v2\/media\/11169"}],"wp:attachment":[{"href":"https:\/\/thecodest.co\/lt\/wp-json\/wp\/v2\/media?parent=11167"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/thecodest.co\/lt\/wp-json\/wp\/v2\/categories?post=11167"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/thecodest.co\/lt\/wp-json\/wp\/v2\/tags?post=11167"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}