{"id":12634,"date":"2024-05-22T18:34:25","date_gmt":"2024-05-22T15:34:25","guid":{"rendered":"https:\/\/itsm.com\/?p=12634"},"modified":"2024-09-20T18:45:12","modified_gmt":"2024-09-20T15:45:12","slug":"6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny","status":"publish","type":"post","link":"https:\/\/itsm.com\/tr\/blog\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny\/","title":{"rendered":"Yaz\u0131l\u0131m geli\u015ftirmede her zaman ge\u00e7erli olan 6 risk"},"content":{"rendered":"<p>Yaz\u0131l\u0131m geli\u015ftirme bir\u00e7ok t\u00fcrde i\u00e7 ve d\u0131\u015f risk i\u00e7erir ve bunlar\u0131n tespiti kaliteli bir \u00fcr\u00fcn yaratmak i\u00e7in kritik \u00f6nem ta\u015f\u0131r. <a href=\"https:\/\/www.statista.com\/statistics\/1345127\/integrated-risk-management-security-spending-worldwide\/\">Statista<\/a>&#8216;ya g\u00f6re, 2024 y\u0131l\u0131 sonuna kadar BT sekt\u00f6r\u00fcnde kapsaml\u0131 risk y\u00f6netimi i\u00e7in k\u00fcresel olarak yakla\u015f\u0131k 5.473 milyon dolar harcanacak.<\/p>\n<p>Yaz\u0131l\u0131m geli\u015ftirme sekt\u00f6r\u00fcnde \u00e7al\u0131\u015fanlar i\u00e7in, etkili bir \u015fekilde yan\u0131t verebilmek amac\u0131yla potansiyel riskleri anlamak \u00f6nemlidir.<\/p>\n<p>Bu makalede yaz\u0131l\u0131m geli\u015ftirmedeki \u00e7e\u015fitli riskler, bunlar\u0131n nas\u0131l en aza indirilece\u011fi ve risk y\u00f6netiminin \u015firketlerin i\u015f stratejilerine dahil edilmesinin \u00f6nemi ayr\u0131nt\u0131l\u0131 olarak ele al\u0131nacakt\u0131r.<\/p>\n<h2>Yaz\u0131l\u0131m geli\u015ftirmede risk y\u00f6netimi neden \u00f6nemlidir?&#8221;<\/h2>\n<p>Potansiyel risklerin belirlenmesi, yaz\u0131l\u0131m \u00fcr\u00fcnleri ve hizmetleri geli\u015ftirilirken dikkate al\u0131nmas\u0131 gereken \u00f6nemli bir husustur. Risk y\u00f6netiminin temel amac\u0131 potansiyel tehditleri azaltmakt\u0131r, ancak bunun ba\u015fka nedenleri de vard\u0131r:<\/p>\n<p><strong>1) Sonu\u00e7lar\u0131 en \u00fcst d\u00fczeye \u00e7\u0131karmak ve son teslim tarihlerine uymak<\/strong><\/p>\n<p>Risk y\u00f6netimi, belirlenen b\u00fct\u00e7e dahilinde tamamlanabilmesi i\u00e7in yaz\u0131l\u0131m geli\u015ftirme maliyetinin d\u00fc\u015f\u00fcr\u00fclmesine yard\u0131mc\u0131 olur. Geli\u015ftirme s\u00fcreci s\u0131ras\u0131nda olas\u0131 tehditleri \u00f6ng\u00f6rerek, i\u015f ak\u0131\u015f\u0131 s\u0131ras\u0131nda kar\u0131 en \u00fcst d\u00fczeye \u00e7\u0131kar\u0131r ve maliyetleri en aza indirirsiniz.<\/p>\n<p><strong>2) &#8220;Y\u00fcksek&#8221; riskin \u00fcstesinden gelmek i\u00e7in b\u00fct\u00e7e ay\u0131r\u0131n<\/strong><\/p>\n<p>Riskler i\u00e7in planlama yaparken, bunlar\u0131 ger\u00e7ekle\u015fme olas\u0131l\u0131\u011f\u0131na ve olas\u0131 sonu\u00e7lar\u0131na g\u00f6re \u00f6nceliklendirebilirsiniz. Tipik olarak, d\u00fc\u015f\u00fck riskli durumlar\u0131n \u00fcr\u00fcn geli\u015ftirmenin performans\u0131, maliyeti veya program\u0131 \u00fczerinde \u00e7ok az etkisi vard\u0131r veya hi\u00e7 etkisi yoktur. Program\u0131 aksatan veya performans sorunlar\u0131na yol a\u00e7an b\u00fcy\u00fck olaylar\u0131n riski, \u00f6nemli bir b\u00fct\u00e7e art\u0131\u015f\u0131na neden olabilir. Bu nedenle, \u015firket kritik bir durumda y\u00fcksek riskle ba\u015fa \u00e7\u0131kmaya haz\u0131r olmal\u0131d\u0131r.<\/p>\n<p><strong>3) Ba\u015far\u0131 i\u00e7in bir strateji planlama<\/strong><\/p>\n<p>Risk y\u00f6netiminin temeli, projelerle ili\u015fkili t\u00fcm d\u0131\u015f risklerin kapsaml\u0131 bir listesini derlemektir. Risk de\u011ferlendirme s\u00fcreci, olas\u0131l\u0131\u011f\u0131n, proje ba\u015far\u0131s\u0131 \u00fczerindeki etkinin ve \u00f6nerilen eylemlerin belirlenmesini i\u00e7erir. Sa\u011flam bir strateji kullan\u0131larak ba\u015far\u0131 garanti alt\u0131na al\u0131n\u0131r.<\/p>\n<p><em>A\u015fa\u011f\u0131daki b\u00f6l\u00fcmde yaz\u0131l\u0131m geli\u015ftirmedeki ba\u015fl\u0131ca riskler tart\u0131\u015f\u0131lacak ve bunlarla ba\u015fa \u00e7\u0131kmak i\u00e7in stratejiler \u00f6nerilecektir.<\/em><\/p>\n<h2>Yaz\u0131l\u0131m geli\u015ftirmede organizasyonel riskler<\/h2>\n<h4>Etkin olmayan proje y\u00f6netimi<\/h4>\n<p><strong>Nedir:<\/strong> Etkisiz y\u00f6netim &#8211; yetersiz planlama, a\u00e7\u0131k ileti\u015fim eksikli\u011fi, kaynak tahsisi, eylemlerin yetersiz izlenmesi ve kontrol\u00fc.<\/p>\n<p><strong>Olas\u0131 Sonu\u00e7lar:<\/strong> K\u00f6t\u00fc y\u00f6netimin sonu\u00e7lar\u0131 \u00f6nemli olabilir ve teslim tarihlerinin ka\u00e7\u0131r\u0131lmas\u0131na, b\u00fct\u00e7e a\u015f\u0131mlar\u0131na, kalitenin d\u00fc\u015fmesine ve ekip \u00e7al\u0131\u015fmas\u0131n\u0131n zorlanmas\u0131na, payda\u015f g\u00fcveninin kaybolmas\u0131na, itibar\u0131n zedelenmesine ve hatta proje &#8220;ba\u015far\u0131s\u0131zl\u0131\u011f\u0131na&#8221; neden olabilir.<\/p>\n<p><strong>Nas\u0131l \u00f6nlenir:<\/strong><\/p>\n<ul>\n<li><strong>Gerekli liderlik becerilerine,<\/strong> alan bilgisine ve yaz\u0131l\u0131m geli\u015ftirme projelerini y\u00f6netme deneyimine sahip deneyimli bir proje y\u00f6neticisini i\u015fe al\u0131n. Yetkin bir proje y\u00f6neticisi, proje boyunca potansiyel risklerin belirlenmesine ve y\u00f6netilmesine yard\u0131mc\u0131 olacakt\u0131r.<\/li>\n<li><strong>\u00c7evik bir yakla\u015f\u0131m benimseyin:<\/strong> \u00c7evik metodolojilerin (Scrum veya Kanban) kullan\u0131lmas\u0131 y\u00f6netim etkinli\u011fini art\u0131rabilir. Bu metodolojiler yinelemeli geli\u015ftirmeyi, s\u00fcrekli ekip i\u015fbirli\u011fini te\u015fvik eder, de\u011fi\u015fen gereksinimlere daha iyi uyum sa\u011flamaya ve i\u00e7 ve d\u0131\u015f risklerin erken tan\u0131mlanmas\u0131na olanak tan\u0131r.<\/li>\n<\/ul>\n<h4>Belirsiz veya \u00e7eli\u015fkili gereksinimler<\/h4>\n<p><strong>Nedir:<\/strong> Hedefler, i\u015flevsellik veya performans kriterleri hakk\u0131nda belirsizlik veya anla\u015fmazl\u0131k oldu\u011funda belirsiz veya \u00e7eli\u015fkili gereksinimler ortaya \u00e7\u0131kar. Bu risk, \u00f6zellikle yaz\u0131l\u0131m geli\u015ftirmeye dahil olan \u00e7ok say\u0131da payda\u015f varsa veya gereksinim toplama ba\u015flamadan \u00f6nce proje fikri olu\u015fturulmam\u0131\u015fsa yayg\u0131nd\u0131r.<\/p>\n<p><strong>Olas\u0131 Sonu\u00e7lar:<\/strong> Belirsiz veya \u00e7eli\u015fkili gereksinimler, \u00fcr\u00fcn geli\u015ftirmenin gecikmesine, de\u011fi\u015fiklikler nedeniyle maliyetlerin artmas\u0131na ve payda\u015f veya pazar ihtiya\u00e7lar\u0131n\u0131 kar\u015f\u0131lamayan nihai bir \u00fcr\u00fcne neden olabilir.<\/p>\n<p><strong>Nas\u0131l \u00f6nlenir:<\/strong><\/p>\n<ul>\n<li><strong>Bir SOW <em>(Statement of work)<\/em> olu\u015fturun:<\/strong> \u00dcr\u00fcn i\u00e7in hedefleri, \u00e7\u0131kt\u0131lar\u0131, zaman \u00e7izelgelerini ve teslimat kriterlerini a\u00e7\u0131klayan ayr\u0131nt\u0131l\u0131 bir SOW geli\u015ftirin; bu, hedefe ula\u015fmak i\u00e7in net bir yol haritas\u0131 sa\u011flayacak, yeterince a\u00e7\u0131k olmayan veya \u00e7eli\u015fen gereksinim riskini en aza indirecek ve geli\u015ftirme \u015firketinin m\u00fc\u015fterinin ne istedi\u011fini net bir \u015fekilde anlamas\u0131na yard\u0131mc\u0131 olacakt\u0131r.<\/li>\n<\/li>\n<li><strong>Gereksinim dok\u00fcmantasyon s\u00fcrecini iyile\u015ftirin:<\/strong> gereksinimleri toplamak, belgelemek ve do\u011frulamak i\u00e7in yap\u0131land\u0131r\u0131lm\u0131\u015f bir s\u00fcre\u00e7 uygulay\u0131n &#8211; \u00f6rne\u011fin, gereksinimleri d\u00fczenlemek ve tan\u0131mlamak i\u00e7in MoSCoW <em>(g\u00f6rev \u00f6nceliklendirme y\u00f6ntemi)<\/em> kullan\u0131n.<\/li>\n<\/ul>\n<h2>Yaz\u0131l\u0131m geli\u015ftirmede operasyonel riskler<\/h2>\n<h4>Yetersiz test<\/h4>\n<p><strong>Nedir:<\/strong> Test, sorunlar\u0131 zaman\u0131nda tespit etmek i\u00e7in planlama a\u015famas\u0131ndan geli\u015ftirme ya\u015fam d\u00f6ng\u00fcs\u00fc boyunca s\u00fcrekli teste kadar yaz\u0131l\u0131m geli\u015ftirmenin ayr\u0131lmaz bir par\u00e7as\u0131 olmal\u0131d\u0131r. Uygun olmayan testler, plana dahil edilmezse veya zaman, kaynak, beceri, de\u011fi\u015fikliklere uyum sa\u011flama yetene\u011fi eksikli\u011fi varsa ortaya \u00e7\u0131kabilir ve bu da nihai \u00fcr\u00fcnde sorunlara yol a\u00e7abilir.<\/p>\n<p><strong>Olas\u0131 Sonu\u00e7lar:<\/strong> Hatal\u0131 olarak piyasaya s\u00fcr\u00fclen yaz\u0131l\u0131mlar k\u00f6t\u00fc bir kullan\u0131c\u0131 deneyimine ve potansiyel g\u00fcvenlik a\u00e7\u0131klar\u0131na yol a\u00e7abilir ve sonu\u00e7ta \u015firket i\u00e7in mali ve itibar kay\u0131plar\u0131na neden olabilir.<\/p>\n<p><strong>Nas\u0131l \u00f6nlenir:<\/strong><\/p>\n<ul>\n<li><strong>Kapsaml\u0131 bir QA test plan\u0131 geli\u015ftirin:<\/strong> Detayl\u0131 ve kapsaml\u0131 bir test plan\u0131, yaz\u0131l\u0131m\u0131n her bile\u015feninin tam olarak te\u015fhis edilmesini sa\u011flamak i\u00e7in kritik \u00f6neme sahiptir. QA ekibinin sistematik ve etkili testler ger\u00e7ekle\u015ftirmesi i\u00e7in bir rehber olabilir.<\/li>\n<li><strong>Otomatik testler uygulay\u0131n:<\/strong> otomatik testler, tekrarlayan testleri ger\u00e7ekle\u015ftirmek ve sorunlar\u0131 belirlemek i\u00e7in h\u0131zl\u0131 ve verimli bir yol sa\u011flayarak manuel test \u00e7abalar\u0131n\u0131 tamamlayabilir. B\u00f6ylece manuel testler karma\u015f\u0131k kullan\u0131m senaryolar\u0131na daha fazla odaklanabilir.<\/li>\n<\/ul>\n<h4>UI\/UX tasar\u0131m ihmali<\/h4>\n<p><strong>Nedir:<\/strong> Yaz\u0131l\u0131m geli\u015ftirme, yaz\u0131l\u0131m\u0131n son kullan\u0131c\u0131lar i\u00e7in ne kadar sezgisel, eri\u015filebilir ve \u00e7ekici oldu\u011funu dikkate almadan teknik y\u00f6nlere ve i\u015flevselli\u011fe a\u015f\u0131r\u0131 odakland\u0131\u011f\u0131nda kullan\u0131c\u0131 aray\u00fcz\u00fc ihmali ortaya \u00e7\u0131kabilir.<\/p>\n<p><strong>Olas\u0131 Sonu\u00e7lar:<\/strong> K\u00f6t\u00fc tasarlanm\u0131\u015f bir UI\/UX kullan\u0131c\u0131 memnuniyetsizli\u011fine, kullan\u0131c\u0131 etkile\u015fiminin azalmas\u0131na ve potansiyel gelir kayb\u0131na yol a\u00e7abilir. Buna ek olarak, marka itibar\u0131 zarar g\u00f6rebilir ve kusurlar\u0131 yeniden i\u015flemek ve d\u00fczeltmek i\u00e7in ek maliyetler ortaya \u00e7\u0131kabilir.<\/p>\n<p><strong>Nas\u0131l \u00f6nlenir:<\/strong><\/p>\n<ul>\n<li><strong>Kullan\u0131c\u0131 ara\u015ft\u0131rmas\u0131 yap\u0131n:<\/strong> Kullan\u0131c\u0131 ara\u015ft\u0131rmas\u0131, ba\u015far\u0131l\u0131 UI\/UX tasar\u0131m\u0131n\u0131n ilk ad\u0131m\u0131d\u0131r. Bu s\u00fcre\u00e7, kullan\u0131c\u0131lar\u0131n ihtiya\u00e7lar\u0131n\u0131, tercihlerini ve davran\u0131\u015flar\u0131n\u0131 anlamay\u0131 i\u00e7erir ve onlar\u0131n ihtiya\u00e7lar\u0131n\u0131 kar\u015f\u0131layan ve beklentilerini a\u015fan bir \u00fcr\u00fcn tasarlaman\u0131za olanak tan\u0131r.<\/li>\n<\/li>\n<li><strong>Bir Storyboard Geli\u015ftirin:<\/strong> Storyboard, kullan\u0131c\u0131n\u0131n yaz\u0131l\u0131mla etkile\u015fimini g\u00f6rselle\u015ftirmenin bir y\u00f6ntemidir. Kullan\u0131c\u0131lar\u0131n bir \u00fcr\u00fcn\u00fc kullan\u0131rken izledikleri yolu g\u00f6rselle\u015ftirmeye, olas\u0131 sorunlar\u0131 belirlemeye ve en iyi kullan\u0131c\u0131 deneyimini elde etmek i\u00e7in deneyimi optimize etmeye yard\u0131mc\u0131 olur.<\/li>\n<\/li>\n<\/ul>\n<h2>Yaz\u0131l\u0131m geli\u015ftirmede teknik riskler<\/h2>\n<h4>G\u00fcvenilmez teknolojiler ve ara\u00e7lar<\/h4>\n<p><strong>Nedir:<\/strong> Teknoloji h\u0131zla geli\u015fmektedir ve bir zamanlar m\u00fckemmellik standard\u0131 olarak kabul edilen ara\u00e7lar art\u0131k eski olarak kabul edilebilir. Yaz\u0131l\u0131m uygularken g\u00fcvenilmez, kan\u0131tlanmam\u0131\u015f veya eski teknolojilerin kullan\u0131lmas\u0131 proje risklerini art\u0131rabilir.<\/p>\n<p><strong>Olas\u0131 sonu\u00e7lar:<\/strong> G\u00fcvenilir olmayan ve eski teknolojilerin kullan\u0131lmas\u0131 sistem istikrars\u0131zl\u0131\u011f\u0131na ve bilgi g\u00fcvenli\u011fi risklerine yol a\u00e7ar. Proje kod taban\u0131nda \u00f6nemli de\u011fi\u015fiklikler yap\u0131lmas\u0131 gerekebilir. Sonu\u00e7 olarak, sorun giderme ve problem \u00e7\u00f6zme s\u00fcresi ve maliyeti artar, bu da proje uygulamas\u0131n\u0131n ertelenmesine yol a\u00e7ar.<\/p>\n<p><strong>Nas\u0131l \u00f6nlenir:<\/strong><\/p>\n<ul>\n<li><strong>Uygun bir yaz\u0131l\u0131m mimarisi geli\u015ftirin:<\/strong> Geli\u015ftirmeye ba\u015flamadan \u00f6nce, proje i\u00e7in sa\u011flam bir temel olu\u015fturacak ve uzun vadede teknik sorunlardan ka\u00e7\u0131nman\u0131za yard\u0131mc\u0131 olacak etkili bir yaz\u0131l\u0131m mimarisi olu\u015fturman\u0131z gerekir.<\/li>\n<li><strong>Teknolojileri de\u011ferlendirin:<\/strong> Bir teknoloji veya ara\u00e7 se\u00e7meden \u00f6nce, ne kadar sa\u011flam oldu\u011funu, mevcut teknoloji y\u0131\u011f\u0131n\u0131yla uyumlu oldu\u011funu ve proje gereksinimlerini kar\u015f\u0131lad\u0131\u011f\u0131n\u0131 anlamak i\u00e7in kapsaml\u0131 bir de\u011ferlendirme yap\u0131lmal\u0131d\u0131r.<\/li>\n<li><strong>Bir prototip geli\u015ftirin:<\/strong> \u00fcr\u00fcn\u00fcn bir test s\u00fcr\u00fcm\u00fc, se\u00e7ilen teknolojilerin uygulanabilirli\u011fini ve uyumlulu\u011funu sa\u011flayacakt\u0131r.<\/li>\n<\/ul>\n<h2>Yaz\u0131l\u0131m geli\u015ftirmede g\u00fcvenlik riskleri<\/h2>\n<h4>Uygun olmayan g\u00fcvenlik \u00f6nlemleri<\/h4>\n<p><strong>Nedir:<\/strong> Genellikle yaz\u0131l\u0131m geli\u015ftirme i\u015flevsellik, uygulama h\u0131z\u0131 ve kullan\u0131labilirli\u011fe odaklan\u0131rken g\u00fcvenlik arka planda b\u0131rak\u0131l\u0131r. Ancak, d\u00fc\u015f\u00fck kaliteli kod, zay\u0131f veri korumas\u0131, kullan\u0131c\u0131 eri\u015fim kontrollerinin eksikli\u011fi, g\u00fcvenlik a\u00e7\u0131\u011f\u0131 testi, g\u00fcvenli olmayan harici bile\u015fenlerin kullan\u0131m\u0131, yaz\u0131l\u0131m\u0131n yanl\u0131\u015f yap\u0131land\u0131r\u0131lmas\u0131, g\u00fcncellemelerin ihmal edilmesi ve bilgi s\u0131z\u0131nt\u0131s\u0131 i\u00e7in bir plan\u0131n olmamas\u0131 gibi nedenlerle g\u00fcvenlik riskleri \u00f6nemli olabilir.<\/p>\n<p><strong>Olas\u0131 Sonu\u00e7lar:<\/strong> Uygun g\u00fcvenlik \u00f6nlemlerinin al\u0131nmamas\u0131 ciddi sonu\u00e7lara yol a\u00e7abilir &#8211; gizli bilgilerin s\u0131zd\u0131r\u0131lmas\u0131, sisteme yetkisiz eri\u015fim vb. Bu olaylar \u015firketin itibar\u0131na zarar verebilir, \u00f6nemli mali kay\u0131plara yol a\u00e7abilir ve kullan\u0131c\u0131 g\u00fcvenini sarsabilir.<\/p>\n<p><strong>Nas\u0131l \u00f6nlenir:<\/strong><\/p>\n<ul>\n<li><strong>DevSecOps uygulamalar\u0131n\u0131 hayata ge\u00e7irin:<\/strong> DevSecOps, yaz\u0131l\u0131m geli\u015ftirme ya\u015fam d\u00f6ng\u00fcs\u00fcn\u00fcn \u00e7ok erken a\u015famalar\u0131nda koruma sa\u011flayan ve b\u00f6ylece tehdit olas\u0131l\u0131\u011f\u0131n\u0131 azaltan g\u00fcvenlik testlerini yaz\u0131l\u0131m geli\u015ftirme sistemine entegre etme uygulamas\u0131d\u0131r. DevSecOps, g\u00fcvenlik riski y\u00f6netimini t\u00fcm ekip \u00fcyelerinin ortak sorumlulu\u011fu haline getirerek bir g\u00fcvenlik bilinci k\u00fclt\u00fcr\u00fcn\u00fc te\u015fvik eder.<\/li>\n<li><strong>G\u00fcvenli teknolojiler kullan\u0131n:<\/strong> G\u00fcvenilirli\u011fi ile bilinen ve aktif topluluk deste\u011fine sahip teknolojileri se\u00e7in. Bu, yaz\u0131l\u0131m\u0131n g\u00fcvenli bir temel \u00fczerine in\u015fa edilmesini ve olas\u0131 sald\u0131r\u0131lara etkili bir \u015fekilde dayanabilmesini sa\u011flayacakt\u0131r.<\/li>\n<\/li>\n<\/ul>\n<h2>&#8220;Yaz\u0131l\u0131m geli\u015ftirmede riskler nas\u0131l belirlenir ve y\u00f6netilir?&#8221;<\/h2>\n<p>Sistematik risk y\u00f6netimi, yaz\u0131l\u0131m geli\u015ftirme risklerini hem de\u011ferlendirmek hem de kontrol etmek i\u00e7in \u00f6nlemler gerektirir.<\/p><p>S\u00fcre\u00e7 tipik olarak 6 ad\u0131mdan olu\u015fur:<\/p>\n<p><strong>1. Tan\u0131mlama ve s\u0131n\u0131fland\u0131rma<\/strong><\/p>\n<p>Y\u00f6netimde ilk ad\u0131m potansiyel riskleri belirlemektir. Bunlar aras\u0131nda teknik engeller, b\u00fct\u00e7e k\u0131s\u0131tlamalar\u0131, kaynak k\u0131s\u0131tlamalar\u0131 ve zamanlama sorunlar\u0131 yer al\u0131r. Her ad\u0131m, potansiyel riskleri belirlemek i\u00e7in proje planlamas\u0131ndan da\u011f\u0131t\u0131ma kadar SDLC s\u00fcrecinin kapsaml\u0131 bir analizini gerektirebilir.<\/p>\n<p><strong>2. De\u011ferlendirme ve \u00f6nceliklendirme<\/strong><\/p>\n<p>Bu a\u015fama \u015funlar\u0131 i\u00e7erir:<\/p>\n<ul>\n<li>Projeler i\u00e7in tehdit olu\u015fturan sorunlar\u0131n belirlenmesi;<\/li>\n<li>risk olu\u015fma olas\u0131l\u0131\u011f\u0131n\u0131n belirlenmesi;<\/li>\n<li>risk etkisinin belirlenmesi;<\/li>\n<li>1 ila 10 aral\u0131\u011f\u0131nda olas\u0131l\u0131k ve etki de\u011ferlerinin atanmas\u0131;<\/li>\n<li>riske maruz kalma fakt\u00f6r\u00fcn\u00fcn belirlenmesi.<\/li>\n<\/ul>\n<p>Proje y\u00f6neticisi t\u00fcm de\u011ferleri i\u00e7eren bir tablo haz\u0131rlamal\u0131 ve riskleri riske maruz kalma fakt\u00f6r\u00fcne g\u00f6re s\u0131ralamal\u0131d\u0131r.<\/p>\n<p><strong>3. Bir etki azaltma stratejisi geli\u015ftirin<\/strong><\/p>\n<p>Bu stratejiler aras\u0131nda bir acil durum plan\u0131 geli\u015ftirmek, ek kaynaklar getirmek, i\u015fi d\u0131\u015far\u0131dan temin etmek veya program\u0131 ayarlamak yer al\u0131r.<\/p>\n<p><strong>4. S\u00fcrekli izleme ve azaltma <\/strong><\/p>\n<p>Risk, yeniden de\u011ferlendirilmesi, etkisi ve tekrarlanma olas\u0131l\u0131\u011f\u0131 yeniden de\u011ferlendirilerek s\u00fcrekli olarak izlenmelidir. Bu a\u015famada \u00e7al\u0131\u015fmak, tehlikelerin tan\u0131mlanmas\u0131n\u0131 ve azalt\u0131lmas\u0131n\u0131 ve riskin b\u00fcy\u00fckl\u00fc\u011f\u00fcn\u00fcn ve etkisinin de\u011ferlendirilmesini sa\u011flar. Buna ek olarak, eylemlerin objektif, zaman\u0131nda ve do\u011fru olmas\u0131n\u0131 sa\u011flamak i\u00e7in risk y\u00f6netimi stratejisi d\u00fczenli olarak g\u00f6zden ge\u00e7irilmeli ve g\u00fcncellenmelidir. Risk azaltma, tamamen \u00f6nlenemedikleri durumlarda olumsuz sonu\u00e7lar\u0131n etkisini azalt\u0131r.<\/p>\n<h2>Sonu\u00e7<\/h2>\n<p>Geli\u015ftirme s\u00fcreci, tasar\u0131mdan dok\u00fcmantasyona, geli\u015ftirmeden teste kadar \u00e7e\u015fitli a\u015famalar\u0131 kapsar ve bunlar\u0131n hepsi \u00f6nemli derecede teknolojik ve y\u00f6netimsel uzmanl\u0131k gerektirir. Projede her biri farkl\u0131 g\u00f6revleri yerine getiren \u00e7ok say\u0131da uzman yer ald\u0131\u011f\u0131ndan, belirli risklerin ortaya \u00e7\u0131kmas\u0131 ka\u00e7\u0131n\u0131lmazd\u0131r.<\/p>\n<p>Risk y\u00f6netimi, her yaz\u0131l\u0131m \u00fcr\u00fcn\u00fcn\u00fcn geli\u015ftirilmesinde \u00f6ncelik verilmesi gereken kilit bir bile\u015fendir, \u00e7\u00fcnk\u00fc hem s\u00fcre\u00e7lerin verimlili\u011fi ve etkinli\u011fi hem de i\u015fletmenin karl\u0131l\u0131\u011f\u0131 buna ba\u011fl\u0131d\u0131r. Bu durumda en iyi \u00e7\u00f6z\u00fcm, t\u00fcm yaz\u0131l\u0131m \u00fcr\u00fcn\u00fc geli\u015ftirme ya\u015fam d\u00f6ng\u00fcs\u00fcn\u00fc desteklemek i\u00e7in yap\u0131land\u0131r\u0131lm\u0131\u015f ve sistematik bir yakla\u015f\u0131m sa\u011flayan ve ayn\u0131 zamanda ekipleri y\u00f6netmenize, g\u00f6revleri g\u00f6rselle\u015ftirmenize ve olas\u0131 risklerin sonu\u00e7lar\u0131n\u0131 \u00f6nlemek ve en aza indirmek i\u00e7in kaynaklar\u0131 planlaman\u0131za olanak tan\u0131yan <a href=\"https:\/\/itsm.com\/tr\/sdlc\/?utm_source=article_risks\">SimpleOne SDLC<\/a> olabilir.<\/p>\n<p>Riskler y\u00f6netilebilir ve y\u00f6netilmelidir &#8211; bunu yapmak i\u00e7in \u015firketlerin risk y\u00f6netimini i\u015f s\u00fcre\u00e7lerine dahil etmesi ve tehditleri \u00f6nleyici kontrol y\u00f6ntemine g\u00f6re y\u00f6netmesi, t\u00fcm \u00e7al\u0131\u015fanlar\u0131n proje risklerinin fark\u0131nda oldu\u011fundan ve ortaya \u00e7\u0131kan sorunlara h\u0131zl\u0131 ve etkili bir \u015fekilde yan\u0131t vermek i\u00e7in do\u011fru ara\u00e7lar\u0131 kulland\u0131\u011f\u0131ndan emin olmas\u0131 gerekir.<\/p>\n<p>&nbsp;<\/p>","protected":false},"excerpt":{"rendered":"<p>Yaz\u0131l\u0131m geli\u015ftirme bir\u00e7ok t\u00fcrde i\u00e7 ve d\u0131\u015f risk i\u00e7erir ve bunlar\u0131n tespiti kaliteli bir \u00fcr\u00fcn yaratmak i\u00e7in kritik \u00f6nem ta\u015f\u0131r. Statista&#8216;ya g\u00f6re, 2024 y\u0131l\u0131 sonuna kadar BT sekt\u00f6r\u00fcnde kapsaml\u0131 risk y\u00f6netimi i\u00e7in k\u00fcresel olarak yakla\u015f\u0131k 5.473 milyon dolar harcanacak. Yaz\u0131l\u0131m geli\u015ftirme sekt\u00f6r\u00fcnde \u00e7al\u0131\u015fanlar i\u00e7in, etkili bir \u015fekilde yan\u0131t verebilmek amac\u0131yla potansiyel riskleri anlamak \u00f6nemlidir. Bu [&hellip;]<\/p>\n","protected":false},"author":48,"featured_media":12635,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[2],"tags":[58],"yoast_head":"<title>Yaz\u0131l\u0131m geli\u015ftirmede her zaman ge\u00e7erli olan 6 risk - SimpleOne - Business Process Automation Platform<\/title>\n<meta name=\"description\" content=\"Blog SimpleOne - Business Process Automation Platform Yaz\u0131l\u0131m geli\u015ftirmede her zaman ge\u00e7erli olan 6 risk\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<meta property=\"og:locale\" content=\"tr_TR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Yaz\u0131l\u0131m geli\u015ftirmede her zaman ge\u00e7erli olan 6 risk - SimpleOne - Business Process Automation Platform\" \/>\n<meta property=\"og:description\" content=\"Blog SimpleOne - Business Process Automation Platform Yaz\u0131l\u0131m geli\u015ftirmede her zaman ge\u00e7erli olan 6 risk\" \/>\n<meta property=\"og:url\" content=\"https:\/\/itsm.com\/blog\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny\/\" \/>\n<meta property=\"og:site_name\" content=\"SimpleOne - Business Process Automation Platform\" \/>\n<meta property=\"article:published_time\" content=\"2024-05-22T15:34:25+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/itsm.com\/wp-content\/uploads\/2024\/09\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny-oblozhka.png\" \/>\n\t<meta property=\"og:image:width\" content=\"921\" \/>\n\t<meta property=\"og:image:height\" content=\"641\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Organization\",\"@id\":\"https:\/\/itsm.com\/#organization\",\"name\":\"SimpleOne\",\"url\":\"https:\/\/itsm.com\/\",\"sameAs\":[],\"logo\":{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/itsm.com\/#logo\",\"inLanguage\":\"tr\",\"url\":\"\/wp-content\/uploads\/2023\/11\/main_logo-1.png\",\"contentUrl\":\"\/wp-content\/uploads\/2023\/11\/main_logo-1.png\",\"width\":166,\"height\":23,\"caption\":\"SimpleOne\"},\"image\":{\"@id\":\"https:\/\/itsm.com\/#logo\"}},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/itsm.com\/#website\",\"url\":\"https:\/\/itsm.com\/\",\"name\":\"SimpleOne - Business Process Automation Platform\",\"description\":\"\u3164\",\"publisher\":{\"@id\":\"https:\/\/itsm.com\/#organization\"},\"inLanguage\":\"tr\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/itsm.com\/blog\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny\/#primaryimage\",\"inLanguage\":\"tr\",\"url\":\"\/wp-content\/uploads\/2024\/09\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny-oblozhka.png\",\"contentUrl\":\"\/wp-content\/uploads\/2024\/09\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny-oblozhka.png\",\"width\":921,\"height\":641},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/itsm.com\/blog\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny\/#webpage\",\"url\":\"https:\/\/itsm.com\/blog\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny\/\",\"name\":\"[:en]6 risks in software development that are always relevant[:pb]6 riscos no desenvolvimento de software que s\u00e3o sempre relevantes[:tr]Yaz\u0131l\u0131m geli\u015ftirmede her zaman ge\u00e7erli olan 6 risk[:ru]6 \u0440\u0438\u0441\u043a\u043e\u0432 \u043f\u0440\u0438 \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0435 \u041f\u041e, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0432\u0441\u0435\u0433\u0434\u0430 \u0430\u043a\u0442\u0443\u0430\u043b\u044c\u043d\u044b[:] - SimpleOne - Business Process Automation Platform\",\"isPartOf\":{\"@id\":\"https:\/\/itsm.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/itsm.com\/blog\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny\/#primaryimage\"},\"datePublished\":\"2024-05-22T15:34:25+00:00\",\"dateModified\":\"2024-09-20T15:45:12+00:00\",\"description\":\"Blog SimpleOne - Business Process Automation Platform [:en]6 risks in software development that are always relevant[:pb]6 riscos no desenvolvimento de software que s\u00e3o sempre relevantes[:tr]Yaz\u0131l\u0131m geli\u015ftirmede her zaman ge\u00e7erli olan 6 risk[:ru]6 \u0440\u0438\u0441\u043a\u043e\u0432 \u043f\u0440\u0438 \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0435 \u041f\u041e, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0432\u0441\u0435\u0433\u0434\u0430 \u0430\u043a\u0442\u0443\u0430\u043b\u044c\u043d\u044b[:]\",\"breadcrumb\":{\"@id\":\"https:\/\/itsm.com\/blog\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny\/#breadcrumb\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/itsm.com\/blog\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/itsm.com\/blog\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/itsm.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"6 risks in software development that are always relevant\"}]},{\"@type\":\"Article\",\"@id\":\"https:\/\/itsm.com\/blog\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/itsm.com\/blog\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny\/#webpage\"},\"author\":{\"@id\":\"https:\/\/itsm.com\/#\/schema\/person\/c7515bc91e745fb07aed438cb94d6358\"},\"headline\":\"Yaz\u0131l\u0131m geli\u015ftirmede her zaman ge\u00e7erli olan 6 risk\",\"datePublished\":\"2024-05-22T15:34:25+00:00\",\"dateModified\":\"2024-09-20T15:45:12+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/itsm.com\/blog\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny\/#webpage\"},\"wordCount\":6270,\"publisher\":{\"@id\":\"https:\/\/itsm.com\/#organization\"},\"image\":{\"@id\":\"https:\/\/itsm.com\/blog\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny\/#primaryimage\"},\"thumbnailUrl\":\"\/wp-content\/uploads\/2024\/09\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny-oblozhka.png\",\"keywords\":[\"SDLC\"],\"articleSection\":[\"Blog\"],\"inLanguage\":\"tr\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/itsm.com\/#\/schema\/person\/c7515bc91e745fb07aed438cb94d6358\",\"name\":\"lyubov azarenko\",\"url\":\"https:\/\/itsm.com\/tr\/author\/lyubov-azarenko\/\"}]}<\/script>","yoast_head_json":{"title":"[:en]6 risks in software development that are always relevant[:pb]6 riscos no desenvolvimento de software que s\u00e3o sempre relevantes[:tr]Yaz\u0131l\u0131m geli\u015ftirmede her zaman ge\u00e7erli olan 6 risk[:ru]6 \u0440\u0438\u0441\u043a\u043e\u0432 \u043f\u0440\u0438 \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0435 \u041f\u041e, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0432\u0441\u0435\u0433\u0434\u0430 \u0430\u043a\u0442\u0443\u0430\u043b\u044c\u043d\u044b[:] - SimpleOne - Business Process Automation Platform","description":"Blog SimpleOne - Business Process Automation Platform Yaz\u0131l\u0131m geli\u015ftirmede her zaman ge\u00e7erli olan 6 risk","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"og_locale":"tr_TR","og_type":"article","og_title":"Yaz\u0131l\u0131m geli\u015ftirmede her zaman ge\u00e7erli olan 6 risk - SimpleOne - Business Process Automation Platform","og_description":"Blog SimpleOne - Business Process Automation Platform Yaz\u0131l\u0131m geli\u015ftirmede her zaman ge\u00e7erli olan 6 risk","og_url":"https:\/\/itsm.com\/blog\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny\/","og_site_name":"SimpleOne - Business Process Automation Platform","article_published_time":"2024-05-22T15:34:25+00:00","og_image":[{"width":921,"height":641,"url":"https:\/\/itsm.com\/wp-content\/uploads\/2024\/09\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny-oblozhka.png","type":"image\/png"}],"twitter_card":"summary_large_image","schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Organization","@id":"https:\/\/itsm.com\/#organization","name":"SimpleOne","url":"https:\/\/itsm.com\/","sameAs":[],"logo":{"@type":"ImageObject","@id":"https:\/\/itsm.com\/#logo","inLanguage":"tr","url":"\/wp-content\/uploads\/2023\/11\/main_logo-1.png","contentUrl":"\/wp-content\/uploads\/2023\/11\/main_logo-1.png","width":166,"height":23,"caption":"SimpleOne"},"image":{"@id":"https:\/\/itsm.com\/#logo"}},{"@type":"WebSite","@id":"https:\/\/itsm.com\/#website","url":"https:\/\/itsm.com\/","name":"SimpleOne - Business Process Automation Platform","description":"\u3164","publisher":{"@id":"https:\/\/itsm.com\/#organization"},"inLanguage":"tr"},{"@type":"ImageObject","@id":"https:\/\/itsm.com\/blog\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny\/#primaryimage","inLanguage":"tr","url":"\/wp-content\/uploads\/2024\/09\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny-oblozhka.png","contentUrl":"\/wp-content\/uploads\/2024\/09\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny-oblozhka.png","width":921,"height":641},{"@type":"WebPage","@id":"https:\/\/itsm.com\/blog\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny\/#webpage","url":"https:\/\/itsm.com\/blog\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny\/","name":"[:en]6 risks in software development that are always relevant[:pb]6 riscos no desenvolvimento de software que s\u00e3o sempre relevantes[:tr]Yaz\u0131l\u0131m geli\u015ftirmede her zaman ge\u00e7erli olan 6 risk[:ru]6 \u0440\u0438\u0441\u043a\u043e\u0432 \u043f\u0440\u0438 \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0435 \u041f\u041e, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0432\u0441\u0435\u0433\u0434\u0430 \u0430\u043a\u0442\u0443\u0430\u043b\u044c\u043d\u044b[:] - SimpleOne - Business Process Automation Platform","isPartOf":{"@id":"https:\/\/itsm.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/itsm.com\/blog\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny\/#primaryimage"},"datePublished":"2024-05-22T15:34:25+00:00","dateModified":"2024-09-20T15:45:12+00:00","description":"Blog SimpleOne - Business Process Automation Platform [:en]6 risks in software development that are always relevant[:pb]6 riscos no desenvolvimento de software que s\u00e3o sempre relevantes[:tr]Yaz\u0131l\u0131m geli\u015ftirmede her zaman ge\u00e7erli olan 6 risk[:ru]6 \u0440\u0438\u0441\u043a\u043e\u0432 \u043f\u0440\u0438 \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0435 \u041f\u041e, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0432\u0441\u0435\u0433\u0434\u0430 \u0430\u043a\u0442\u0443\u0430\u043b\u044c\u043d\u044b[:]","breadcrumb":{"@id":"https:\/\/itsm.com\/blog\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny\/#breadcrumb"},"inLanguage":"tr","potentialAction":[{"@type":"ReadAction","target":["https:\/\/itsm.com\/blog\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/itsm.com\/blog\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/itsm.com\/"},{"@type":"ListItem","position":2,"name":"6 risks in software development that are always relevant"}]},{"@type":"Article","@id":"https:\/\/itsm.com\/blog\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny\/#article","isPartOf":{"@id":"https:\/\/itsm.com\/blog\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny\/#webpage"},"author":{"@id":"https:\/\/itsm.com\/#\/schema\/person\/c7515bc91e745fb07aed438cb94d6358"},"headline":"Yaz\u0131l\u0131m geli\u015ftirmede her zaman ge\u00e7erli olan 6 risk","datePublished":"2024-05-22T15:34:25+00:00","dateModified":"2024-09-20T15:45:12+00:00","mainEntityOfPage":{"@id":"https:\/\/itsm.com\/blog\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny\/#webpage"},"wordCount":6270,"publisher":{"@id":"https:\/\/itsm.com\/#organization"},"image":{"@id":"https:\/\/itsm.com\/blog\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny\/#primaryimage"},"thumbnailUrl":"\/wp-content\/uploads\/2024\/09\/6-riskov-pri-razrabotke-po-kotorye-vsegda-aktualny-oblozhka.png","keywords":["SDLC"],"articleSection":["Blog"],"inLanguage":"tr"},{"@type":"Person","@id":"https:\/\/itsm.com\/#\/schema\/person\/c7515bc91e745fb07aed438cb94d6358","name":"lyubov azarenko","url":"https:\/\/itsm.com\/tr\/author\/lyubov-azarenko\/"}]}},"acf":[],"_links":{"self":[{"href":"https:\/\/itsm.com\/tr\/wp-json\/wp\/v2\/posts\/12634"}],"collection":[{"href":"https:\/\/itsm.com\/tr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/itsm.com\/tr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/itsm.com\/tr\/wp-json\/wp\/v2\/users\/48"}],"replies":[{"embeddable":true,"href":"https:\/\/itsm.com\/tr\/wp-json\/wp\/v2\/comments?post=12634"}],"version-history":[{"count":3,"href":"https:\/\/itsm.com\/tr\/wp-json\/wp\/v2\/posts\/12634\/revisions"}],"predecessor-version":[{"id":12648,"href":"https:\/\/itsm.com\/tr\/wp-json\/wp\/v2\/posts\/12634\/revisions\/12648"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/itsm.com\/tr\/wp-json\/wp\/v2\/media\/12635"}],"wp:attachment":[{"href":"https:\/\/itsm.com\/tr\/wp-json\/wp\/v2\/media?parent=12634"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/itsm.com\/tr\/wp-json\/wp\/v2\/categories?post=12634"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/itsm.com\/tr\/wp-json\/wp\/v2\/tags?post=12634"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}