{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2026,4,27]],"date-time":"2026-04-27T11:54:50Z","timestamp":1777290890369,"version":"3.51.4"},"reference-count":8,"publisher":"Walter de Gruyter GmbH","issue":"2","license":[{"start":{"date-parts":[[2020,12,1]],"date-time":"2020-12-01T00:00:00Z","timestamp":1606780800000},"content-version":"unspecified","delay-in-days":0,"URL":"http:\/\/creativecommons.org\/licenses\/by\/4.0"}],"content-domain":{"domain":[],"crossmark-restriction":false},"short-container-title":[],"published-print":{"date-parts":[[2020,12,1]]},"abstract":"<jats:title>Abstract<\/jats:title>\n                  <jats:p>Software development method, which does not have any faults or gaps in project implementation, has not been elaborated so far. Due to this reason, the authors have decided to perform this study to make it easier for the companies, which use one of the agile development methods, to better foresee potential risks and to deal with their consequences. The aim of the research is to identify and classify risks in agile software development methods and the related projects based on the obtained survey data. To achieve the goal, the authors have developed evaluation criteria, as well as implemented practical questionnaire in various software development companies. From the obtained survey data, the risks are classified according to various factors, i.e., the changing highest and lowest priorities and needs in various projects. Thus, the obtained research results can be applied in various areas of project development, changing the order of priority factors.<\/jats:p>","DOI":"10.2478\/acss-2020-0012","type":"journal-article","created":{"date-parts":[[2021,1,13]],"date-time":"2021-01-13T03:13:12Z","timestamp":1610507592000},"page":"105-116","source":"Crossref","is-referenced-by-count":3,"title":["Survey on Risk Classification in Agile Software Development Projects in Latvia"],"prefix":"10.2478","volume":"25","author":[{"ORCID":"https:\/\/orcid.org\/0000-0001-7983-3088","authenticated-orcid":false,"given":"Oksana","family":"\u0145ikiforova","sequence":"first","affiliation":[{"name":"Riga Technical University , Riga , Latvia"}],"role":[{"role":"author","vocabulary":"crossref"}]},{"given":"Kristaps","family":"Babris","sequence":"additional","affiliation":[{"name":"Riga Technical University , Riga , Latvia"}],"role":[{"role":"author","vocabulary":"crossref"}]},{"given":"J\u0101nis","family":"Kristapsons","sequence":"additional","affiliation":[{"name":"Riga Technical University , Riga , Latvia"}],"role":[{"role":"author","vocabulary":"crossref"}]}],"member":"374","published-online":{"date-parts":[[2020,12,28]]},"reference":[{"key":"2026042709091789400_j_acss-2020-0012_ref_001_w2aab3b7b5b1b6b1ab1ab1Aa","unstructured":"[1] D. Duka, \u201cAdoption of Agile Methodology in Software Development,\u201d in 2013 36th International Convention on Information and Communication Technology, Electronics and Microelectronics (MIPRO), IEEE, 20\u201324 May 2013, Opatija, Croatia, 2013."},{"key":"2026042709091789400_j_acss-2020-0012_ref_002_w2aab3b7b5b1b6b1ab1ab2Aa","doi-asserted-by":"crossref","unstructured":"[2] A. Albadarneh, I. Albadarneh, & A. Qusef, \u201cRisk Management in Agile Software Development: a Comparative Study,\u201d in 2015 IEEE Jordan Conference on Applied Electrical Engineering and Computing Technologies (AEECT), 3\u20135 Nov. 2015. Amman, Jordan: IEEE, 2015. https:\/\/doi.org\/10.1109\/AEECT.2015.736057310.1109\/AEECT.2015.7360573","DOI":"10.1109\/AEECT.2015.7360573"},{"key":"2026042709091789400_j_acss-2020-0012_ref_003_w2aab3b7b5b1b6b1ab1ab3Aa","doi-asserted-by":"crossref","unstructured":"[3] H. Andrat, & S. Jaswal, \u201cAn Alternative Approach for Risk Assessment in Scrum,\u201d in 2015 International Conference on Computing and Network Communications (CoCoNet), 16\u201319 Dec. 2015. Trivandrum, India: IEEE, 2016. https:\/\/doi.org\/10.1109\/CoCoNet.2015.741123910.1109\/CoCoNet.2015.7411239","DOI":"10.1109\/CoCoNet.2015.7411239"},{"key":"2026042709091789400_j_acss-2020-0012_ref_004_w2aab3b7b5b1b6b1ab1ab4Aa","doi-asserted-by":"crossref","unstructured":"[4] R. C. Williams, J. A. Walker, & A. J. Dorofee, \u201cPutting Risk Management into Practice,\u201d IEEE Software, 1997, vol. 14, no. 3, pp. 75\u201382. https:\/\/doi.org\/10.1109\/52.58924010.1109\/52.589240","DOI":"10.1109\/52.589240"},{"key":"2026042709091789400_j_acss-2020-0012_ref_005_w2aab3b7b5b1b6b1ab1ab5Aa","doi-asserted-by":"crossref","unstructured":"[5] K. Ghane, \u201cQuantitative Planning and Risk Management of Agile Software Development,\u201d in 2017 IEEE Technology & Engineering Management Conference (TEMSCON), 8\u201310 June, 2017. Santa Clara, CA, USA. https:\/\/doi.org\/10.1109\/TEMSCON.2017.799836210.1109\/TEMSCON.2017.7998362","DOI":"10.1109\/TEMSCON.2017.7998362"},{"key":"2026042709091789400_j_acss-2020-0012_ref_006_w2aab3b7b5b1b6b1ab1ab6Aa","doi-asserted-by":"crossref","unstructured":"[6] M. Hammad, I. Inayat, & M. Zahid, \u201cRisk Management in Agile Software Development: A Survey,\u201d in 2019 International Conference on Frontiers of Information Technology (FIT), 16\u201318 Dec. 2019. Islamabad, Pakistan: IEEE, 2020. https:\/\/doi.org\/10.1109\/FIT47737.2019.0003910.1109\/FIT47737.2019.00039","DOI":"10.1109\/FIT47737.2019.00039"},{"key":"2026042709091789400_j_acss-2020-0012_ref_007_w2aab3b7b5b1b6b1ab1ab7Aa","unstructured":"[7] D. Raphael-Rene, Common Risks in Agile Projects and How to Deal with Them [Online]. 2018 [accessed 23 May 2020]. Available from: https:\/\/www.gratasoftware.com\/common-risks-agile-projects-deal."},{"key":"2026042709091789400_j_acss-2020-0012_ref_008_w2aab3b7b5b1b6b1ab1ab8Aa","unstructured":"[8] Project Management Docs [online]. [Viewed 10 April 2020]. Available from: https:\/\/www.projectmanagementdocs.com\/#axzz6ODpjFhs9"}],"container-title":["Applied Computer Systems"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/content.sciendo.com\/view\/journals\/acss\/25\/2\/article-p105.xml","content-type":"text\/html","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/reference-global.com\/pdf\/10.2478\/acss-2020-0012","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2026,4,27]],"date-time":"2026-04-27T11:20:09Z","timestamp":1777288809000},"score":1,"resource":{"primary":{"URL":"https:\/\/reference-global.com\/article\/10.2478\/acss-2020-0012"}},"subtitle":[],"short-title":[],"issued":{"date-parts":[[2020,12,1]]},"references-count":8,"journal-issue":{"issue":"2","published-online":{"date-parts":[[2020,12,28]]},"published-print":{"date-parts":[[2020,12,1]]}},"alternative-id":["10.2478\/acss-2020-0012"],"URL":"https:\/\/doi.org\/10.2478\/acss-2020-0012","relation":{},"ISSN":["2255-8691"],"issn-type":[{"value":"2255-8691","type":"electronic"}],"subject":[],"published":{"date-parts":[[2020,12,1]]}}}