[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-seo-242190-105":3,"detail-sidebar-cat-1-en-105":81,"doc-detail-242190-en":126},{"code":4,"msg":5,"data":6},0,"ok",{"site_id":7,"language":8,"slug":9,"title":10,"keywords":11,"description":12,"schema_data":13,"social_meta":74,"head_meta":76,"extra_data":78,"updated_unix":80},105,"en","towards-optimal-quality-requirement-documentation-in-agile-software-development-a-multiple-case-study","Towards optimal quality requirement documentation in agile software development - a multiple case study","","Agile software development encourages minimal documentation and often prioritizes functional requirements over quality requirements (QRs), which can accelerate time-to-market but complicates the documentation of QRs that are critical for software success. The study examines how practitioners perceive the importance of QR documentation and which factors shape it. A multiple case study with 12 participants from three ASD cases derives a model emphasizing time constraints, QR awareness, and communication gaps, including mitigation strategies.",{"@graph":14,"@context":73},[15,34,56],{"@type":16,"itemListElement":17},"BreadcrumbList",[18,23,27,31],{"item":19,"name":20,"@type":21,"position":22},"https://docshare.wps.com","Home","ListItem",1,{"item":24,"name":25,"@type":21,"position":26},"https://docshare.wps.com/template/","Template",2,{"item":28,"name":29,"@type":21,"position":30},"https://docshare.wps.com/template/presentations/","Presentations",3,{"item":32,"name":10,"@type":21,"position":33},"https://docshare.wps.com/template/towards-optimal-quality-requirement-documentation-in-agile-software-development-a-multiple-case-study/242190/",4,{"url":32,"name":10,"@type":35,"image":36,"author":41,"headline":10,"publisher":44,"fileFormat":47,"inLanguage":8,"description":12,"dateModified":48,"datePublished":49,"encodingFormat":47,"isAccessibleForFree":50,"interactionStatistic":51},"DigitalDocument",{"url":37,"@type":38,"width":39,"height":40},"https://docshare.wps.com/thumbnails/towards-optimal-quality-requirement-documentation-in-agile-software-development-a-multiple-case-study/242190.png","ImageObject",442,249,{"name":42,"@type":43},"Finn","Person",{"url":19,"name":45,"@type":46},"DocShare","Organization","application/pdf","2026-10-14","2026-09-12",true,{"@type":52,"interactionType":53,"userInteractionCount":55},"InteractionCounter",{"@type":54},"ViewAction",5,{"@type":57,"mainEntity":58},"FAQPage",[59,65,69],{"name":60,"@type":61,"acceptedAnswer":62},"Why is quality requirement (QR) documentation challenging in agile software development?","Question",{"text":63,"@type":64},"Agile practices often de-emphasize documentation and may prioritize functional requirements, leaving QRs underspecified or undocumented. QRs are also difficult to specify and measure, making documentation inherently challenging.","Answer",{"name":66,"@type":61,"acceptedAnswer":67},"What aspects do practitioners associate with the importance of QR documentation?",{"text":68,"@type":64},"Practitioners view QR documentation as important because it helps ensure quality, clarifies QRs, and facilitates decision-making.",{"name":70,"@type":61,"acceptedAnswer":71},"Which factors influence QR documentation according to the study’s model?",{"text":72,"@type":64},"The model focuses on time constraints, QR awareness, and communication gaps, which affect how QRs are documented and understood.","https://schema.org",{"og:url":32,"og:type":75,"og:title":10,"og:site_name":45,"og:description":12},"article",{"robots":77,"canonical":32},"index,follow",{"doc_id":79,"site_id":7},242190,1791731120,{"code":4,"msg":82,"data":83},"success",[84,88,93,98,103,108,113,118,122],{"id":85,"doc_module":22,"doc_module_name":25,"category_name":29,"show_sort_weight":86,"slug":87},11,90,"presentations",{"id":89,"doc_module":22,"doc_module_name":25,"category_name":90,"show_sort_weight":91,"slug":92},12,"Resumes",80,"resumes",{"id":94,"doc_module":22,"doc_module_name":25,"category_name":95,"show_sort_weight":96,"slug":97},14,"Invoices",70,"invoices",{"id":99,"doc_module":22,"doc_module_name":25,"category_name":100,"show_sort_weight":101,"slug":102},15,"Posters",60,"posters",{"id":104,"doc_module":22,"doc_module_name":25,"category_name":105,"show_sort_weight":106,"slug":107},16,"Social Media",50,"social-media",{"id":109,"doc_module":22,"doc_module_name":25,"category_name":110,"show_sort_weight":111,"slug":112},17,"Forms",40,"forms",{"id":114,"doc_module":22,"doc_module_name":25,"category_name":115,"show_sort_weight":116,"slug":117},18,"Letters",30,"letters",{"id":119,"doc_module":22,"doc_module_name":25,"category_name":120,"show_sort_weight":55,"slug":121},21,"Paper Templates","papers-templates",{"id":123,"doc_module":22,"doc_module_name":25,"category_name":124,"show_sort_weight":4,"slug":125},158,"General","general-158",{"code":4,"msg":82,"data":127},{"doc_id":79,"user_id":128,"nickname":42,"user_avatar":129,"doc_module":22,"category_id":85,"category_name":29,"doc_title":10,"doc_description":12,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":55,"is_deleted":4,"is_public":22,"is_downloadable":22,"audit_status":22,"page_count":135,"language":136,"language_code":8,"site_id":7,"html_lang":8,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":12,"update_tm":140,"read_time":141},34359740700684,"https://ap-avatar.wpscdn.com/avatar/1f400023980c374ae676?_k=1777273430885731487","This is a pre-print version of the accepted paper!  \nTowards optimal quality requirement documentation in agile software development: a multiple case study  \nWoubshet Behutiyea, Pilar Rodríguezb, Markku Oivoa, Sanja Aaramaac, Jari Partanend and Antonin Abhervée  \na: M3S Empirical Software Engineering research unit, University of Oulu, Oulu, Finland  \nb: Universidad Politécnica de Madrid, Madrid, Spain  \nc: Nokia, Oulu, Finland  \nd: Bittium Wireless Ltd., Oulu, Finland  \ne: Softeam, Paris, France  \n[woubshet.behutiye@oulu.fi](woubshet.behutiye@oulu.fi), [pilar.rodriguez@upm.es](pilar.rodriguez@upm.es), [markku.oivo@oulu.fi](markku.oivo@oulu.fi), [sanja.aaramaa@nokia.com](sanja.aaramaa@nokia.com), [j](jari.partanen@bittium.com and antoin.abherve@softeam.fr)[ari.partanen@bittium.com](jari.partanen@bittium.com and antoin.abherve@softeam.fr)[ and](jari.partanen@bittium.com and antoin.abherve@softeam.fr)[ ](jari.partanen@bittium.com and antoin.abherve@softeam.fr)[antoin.abherve@softeam.fr](jari.partanen@bittium.com and antoin.abherve@softeam.fr)  \nAbstract  \nContext: Agile software development (ASD) promotes minimal documentation and often prioritizes functional requirements over quality requirements (QRs) . The minimal documentation emphasis may be beneficial in reducing time-to-market for software. However, it can also be a concern, especially with QRs, since they are challenging to specify and document and are crucial for software success. Therefore, understanding how practitioners perceive the importance of QR documentation is valuable because it can provide insight into how they approach this task. It also helps in developing models and guidelines that support the documentation of QRs in ASD, which is a research gap.  \nObjective: We aim to understand practitioners’ perceptions of QR documentation and factors influencing this task to derive a model that supports optimal QR documentation in ASD.  \nMethod: We conducted a multiple case study involving 12 participants from three cases that apply ASD.  \nResults: Practitioners identify QR documentation as important and perceive it as contributing to ensuring quality, clarifying QRs, and facilitating decision-making. Time constraints, QR awareness, and communication gaps affect QR documentation. Missing and outdated QR documentation may lead to technical debt and a lack of common understanding regarding QRs. We introduce a model to support optimal QR documentation in ASD by focusing on the factors: time constraints, QR awareness, and communication gaps. The model provides a representation and explanation of the factors affecting QR documentation in ASD and identifies mitigation strategies to overcome issues that may occur due to these factors.  \nConclusion: The study reveals the importance of documenting QRs in ASD. It introduces a model that is based on empirical knowledge of QR documentation practices in ASD. Both practitioners and researchers can potentially benefit from the model. For instance, practitioners can analyze how time constraints or QR awareness affect documentation, see potential issues that may arise from them, and utilize strategies suggested by the model to address these issues. Researchers can learn about QR documentation in ASD and utilize the model to understand the topic. They can also use the study as a baseline to investigate the topic with other cases.  \nKeywords-agile software development; documentation; quality requirements; non-functional requirements  \n1. INTRODUCTION  \nAgile software development (ASD) has been broadly adopted to meet the demands of dynamic business environments, where requirements change frequently and businesses need to remain competitive (Rodríguez et al., 2012) . Consequently, the body of literature on ASD has grown significantly and examines diverse topics, including requirements engineering, adoption challenges and benefits, large-scale adoption, and human and social aspects (Curcio et al., 2018; Dybå and Dingsøyr, 2008; Hoda et al.,","cbCaihrmYtuGnMSF","https://ap.wps.com/l/cbCaihrmYtuGnMSF","pdf",1406159,25,"English","# Abstract\n## Context\n## Objective\n## Method\n## Results\n## Conclusion\n# 1. Introduction","[{\"question\":\"Why is quality requirement (QR) documentation challenging in agile software development?\",\"answer\":\"Agile practices often de-emphasize documentation and may prioritize functional requirements, leaving QRs underspecified or undocumented. QRs are also difficult to specify and measure, making documentation inherently challenging.\"},{\"question\":\"What aspects do practitioners associate with the importance of QR documentation?\",\"answer\":\"Practitioners view QR documentation as important because it helps ensure quality, clarifies QRs, and facilitates decision-making.\"},{\"question\":\"Which factors influence QR documentation according to the study’s model?\",\"answer\":\"The model focuses on time constraints, QR awareness, and communication gaps, which affect how QRs are documented and understood.\"}]","Towards optimal quality requirement documentation in agile software development - a multiple case study | PDF",1789187678,9]