[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-240202-105":53,"doc-detail-240202-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","planning-optimal-agile-releases-via-requirements-optimization-ieee-24th-international-requirements-engineering-conference-workshops","Planning Optimal Agile Releases via Requirements Optimization - IEEE 24th International Requirements Engineering Conference Workshops","","This paper improves requirements quality in agile projects by addressing requirements prioritization within release planning. It observes that business value alone is insufficient, since implementation cost and functional dependencies also affect the prioritization outcome. Agile prioritization is intended to remain a customer/user prerogative, which becomes difficult without decision-support. The work formulates the agile release decision problem as optimization, provides a modeling language for requirements models, and presents an online tool to generate and solve instances.",{"@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":51,"@type":70,"position":76},"https://docshare.wps.com/template/general/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/planning-optimal-agile-releases-via-requirements-optimization-ieee-24th-international-requirements-engineering-conference-workshops/240202/",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/planning-optimal-agile-releases-via-requirements-optimization-ieee-24th-international-requirements-engineering-conference-workshops/240202.png","ImageObject",442,249,{"name":88,"@type":89},"Ivy","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-09-20","2026-09-11",true,{"@type":98,"interactionType":99,"userInteractionCount":76},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What key challenge does the paper address in agile release planning?","Question",{"text":108,"@type":109},"The paper targets the challenge of determining requirements priorities for each agile release when multiple factors influence the decision, not just business value.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"Why are business value-based priority methods considered insufficient?",{"text":113,"@type":109},"The paper notes that other elements such as implementation cost and functionality dependencies affect which requirements should be selected for the next release.",{"name":115,"@type":106,"acceptedAnswer":116},"How does the paper support decision-making for agile release choices?",{"text":117,"@type":109},"It formulates the agile release decision problem as an optimization problem, introduces a modeling language for requirements models, and describes an online tool to model and solve optimization instances.","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},240202,1789158366,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":50,"category_name":51,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":76,"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":76},549758252649,"https://ap-avatar.wpscdn.com/avatar/8000253669c5317157?_k=1778319167496531819","2016 IEEE 24th International Requirements Engineering Conference Workshops  \nPlanning Optimal Agile Releases via Requirements Optimization  \nJoseph Gillain, Ivan Jureta, St´ephane Faulkner  \nData Analysis Decisions Advice (DA2 ) Research Unit  \nDepartment of Business Administration & PReCISE Research Center, University of Namur  \nAbstract—This paper focuses on improving requirements quality in agile projects by determining requirements prioritization. Current methods suggest to take into account business value in order to determine the requirements priority rank. In practice it was observed that many other factors enter into the equation, such as implementation cost and functionality dependencies. Since agile methods suggest that priority should be customer/user’s prerogative, taking all relevant factors becomes challenging without decision supporting tools. Our research question is the following: How can we formulate the agile release decision problem, and which computations can we do over requirements models to recommend solutions to that decision problem? Our contributions are the following: (i) we formulate this agile release decision problem as an optimization problem,(ii) we provide a modelling language to represent instances of this problem as requirements models, and (iii) we describe an online tool to make the models and solve the resulting optimization problem instances.  \nI. INTRODUCTION  \nA. Context: Requirements Priority in Agile Projects  \nAgile methods have become popular for organizing software development. Many benefits have been touted [1]: better knowledge transfer, active participation of the customer in the project, incremental deliveries, and so on.  \nRelative to more established methodologies (e.g., waterfall), which are based on the assumption that the problem is fully specifiable and a solution can be entirely predicted [2], agile methods are based on the assumption that customers, users, stakeholders in general are not able to specify all requirements of the system-to-be at the beginning of the software process, due to requirement or environment change, lack of experience in the problem domain, etc. [3] .  \nAgile tries to treat requirements continuously through the whole project life cycle. Development is iterative, the development team periodically delivers increments of functionality by focusing on requirements with highest priority at each release planning. It ensures that value comes continuously during the complete process and stakeholders are then being able to test and validate the most priority requirements. Those tests helping the customer clarify and refine subsequent requirements, for later releases.  \nTo make such an approach work for customers, requirements prioritization is important. The Agile Requirements Problem (ARP) is driven by elicitation of User Stories. It starts with the definition of high-level statements, epics, written from the system user’s perspective, then refined into shorter,  \nmore narrowly scoped User Stories. This refinement process is ongoing, running throughout the system engineering process. The literature suggests that the priority should be given by the customer, Product Owner, to set criteria for the prioritization of user stories.  \nIn practice, it is known that other criteria enter into account when prioritizing user stories. They can be, for instance, the effort estimated to implement each user story, or functional dependencies [4] .  \nB. Scope: Goal Models Agile Requirement Problems  \nAgile requirement methods and tools have often been opposed to traditional requirements methods [3] . However, we suggest that agile methods could benefit from traditional requirement engineering methods especially from goal modeling (GM) . Such models could be used to support agile requirements and specifically prioritization of emerging requirements.  \nSimilarly to user stories, goal models are based on arefinement process in which abstract (goals/user stories) are refined into more c","cbCaieq62MxO5V19","https://ap.wps.com/l/cbCaieq62MxO5V19","pdf",375947,7,"English","# Introduction\n## Context: Requirements Priority in Agile Projects\n## Scope: Goal Models Agile Requirement Problems\n## Problem: Which requirements to satisfy when?","[{\"question\":\"What key challenge does the paper address in agile release planning?\",\"answer\":\"The paper targets the challenge of determining requirements priorities for each agile release when multiple factors influence the decision, not just business value.\"},{\"question\":\"Why are business value-based priority methods considered insufficient?\",\"answer\":\"The paper notes that other elements such as implementation cost and functionality dependencies affect which requirements should be selected for the next release.\"},{\"question\":\"How does the paper support decision-making for agile release choices?\",\"answer\":\"It formulates the agile release decision problem as an optimization problem, introduces a modeling language for requirements models, and describes an online tool to model and solve optimization instances.\"}]","Planning Optimal Agile Releases via Requirements Optimization - IEEE 24th International Requirements Engineering Conference Workshops | PDF"]