[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-243799-105":53,"doc-detail-243799-en":126},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","prioritizing-tasks-in-software-development-a-systematic-literature-review","Prioritizing tasks in software development - A systematic literature review","","Task prioritization is a central research topic in software development, yet the growing volume of publications makes it difficult for practitioners to identify suitable ranking tools and techniques. This work performs a systematic literature review to assess current research and industrial practice, guided by the PRISMA statement. Findings show that many approaches focus on bug prioritization, while newer studies increasingly examine pull request and issue prioritization. Quality is most often measured using f-score, precision, recall, and accuracy.",{"@graph":63,"@context":118},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":46,"@type":70,"position":76},"https://docshare.wps.com/template/paper-templates/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/prioritizing-tasks-in-software-development-a-systematic-literature-review/243799/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/prioritizing-tasks-in-software-development-a-systematic-literature-review/243799.png","ImageObject",442,249,{"name":88,"@type":89},"Lucas Vance","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-06","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":47},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What is the main goal of the systematic literature review?","Question",{"text":108,"@type":109},"To review the state of research and practice on task prioritization in software engineering and identify the most effective ranking tools and techniques used in industry.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"Which prioritization strategies are most commonly studied according to the review?",{"text":113,"@type":109},"Most approaches developed so far involve bug prioritization.",{"name":115,"@type":106,"acceptedAnswer":116},"How is the quality of a prioritization model commonly measured?",{"text":117,"@type":109},"The review reports frequent use of f-score, precision, recall, and accuracy.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},243799,1789208681,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":45,"category_name":46,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":47,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":135,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":125,"read_time":8},549768064622,"https://ap-avatar.wpscdn.com/davatar_6f874abed73319feea01a86fa6f0fab8","PLOS ONE  \nOPEN ACCESS  \nCitation: Bugayenko Y, Bakare A, Cheverda A, Farina M, Kruglov A, Plaksin Y, et al. (2023) Prioritizing tasks in software development: A systematic literature review. PLoS ONE 18(4):  \ne0283838 . [https://doi.org/10.1371/journal](https://doi.org/10.1371/journal). pone.0283838  \nEditor: Bilal Alatas, Firat Universitesi, TURKEY  \nReceived: January 4, 2023  \nAccepted: March 17, 2023  \nPublished: April 6, 2023  \nCopyright: © 2023 Bugayenko et al. This is an open access article distributed under the terms of the Creative Commons Attribution License, which permits unrestricted use, distribution, and reproduction in any medium, provided the original author and source are credited.  \nData Availability Statement: Data are all contained within the paper and/or Supporting information files.  \nFunding: This research was supported by Huawei Technologies. The funders had no role in study design, data collection and analysis, decision to publish, or preparation of the manuscript.  \nCompeting interests: The authors have declared that no competing interests exist.  \nRESEARCH ARTICLE  \nPrioritizing tasks in software development: A systematic literature review  \nYegor Bugayenko1, Ayomide Bakare2, Arina Cheverda2, Mirko Farina3 *, Artem Kruglov2 *, Yaroslav Plaksin2, Witold Pedrycz4, Giancarlo Succi5  \n1 Huawei, Moscow, Russia, 2 Institute of Software Development and Engineering, Innopolis University, Innopolis, Russia, 3 Institute of Human and Social Sciences, Innopolis University, Innopolis, Russia,  \n4 Department of Electrical and Computer Engineering, University of Alberta, Edmonton, Canada,  \n5 Department of Computer Science and Engineering, University of Bologna, Bologna, Italy  \n* [m.farina@innopolis.ru](m.farina@innopolis.ru) (MF); a. kruglov@innopolis. ru (AK)  \nAbstract  \nTask prioritization is one of the most researched areas in software development. Given the huge number of papers written on the topic, it might be challenging for IT practitioners–software developers, and IT project managers–to find the most appropriate tools or methods developed to date to deal with this important issue. The main goal of this work is therefore to review the current state of research and practice on task prioritization in the Software Engineering domain and to individuate the most effective ranking tools and techniques used in the industry. For this purpose, we conducted a systematic literature review guided and inspired by the Preferred Reporting Items for Systematic Reviews and Meta-Analyses, otherwise known as the PRISMA statement. Based on our analysis, we can make a number of important observations for the field. Firstly, we found that most of the task prioritization approaches developed to date involve a specific type of prioritization strategy—bug prioritization. Secondly, the most recent works we review investigate task prioritization in terms of“pull request prioritization” and “issue prioritization,”(and we speculate that the number of such works will significantly increase due to the explosion of version control and issue management software systems) . Thirdly, we remark that the most frequently used metrics for measuring the quality of a prioritization model are f-score, precision, recall, and accuracy.  \nIntroduction  \nIn software development, the vast majority of tasks do not have mandatory dependencies and it is up to the project manager to decide which task should be completed first. The proper continuous prioritization of tasks (known as backlog refinement in agile terminology) becomes a critical success factor for any software development project, as it guarantees that the company’s crucial goals are in focus and can be met [ 1] .  \nWhat is a task, though? The term “task” in software engineering refers to the smallest unit of work subject to management accountability that needs to be completed as part ofa software development project [2] . So, in the context of software development, the term task is an umbrell","cbCaiekJty835ENk","https://ap.wps.com/l/cbCaiekJty835ENk","pdf",2938099,31,"English","# Abstract\n# Introduction\n# Task prioritization background\n## What is a task\n## Prioritization approaches and frameworks\n## Evaluation metrics","[{\"question\":\"What is the main goal of the systematic literature review?\",\"answer\":\"To review the state of research and practice on task prioritization in software engineering and identify the most effective ranking tools and techniques used in industry.\"},{\"question\":\"Which prioritization strategies are most commonly studied according to the review?\",\"answer\":\"Most approaches developed so far involve bug prioritization.\"},{\"question\":\"How is the quality of a prioritization model commonly measured?\",\"answer\":\"The review reports frequent use of f-score, precision, recall, and accuracy.\"}]","Prioritizing tasks in software development - A systematic literature review | PDF"]