[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-244195-105":53,"doc-detail-244195-en":127},{"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":120,"head_meta":122,"extra_data":124,"updated_unix":126},105,"en","a-systematic-literature-review-on-quality-criteria-for-agile-requirements-specifications-quality-criteria-and-recommendations","A Systematic Literature Review on Quality Criteria for Agile Requirements Specifications - Quality Criteria and Recommendations","","Agile requirements specifications face uncertainty in how traditional correctness-oriented quality criteria translate to lightweight, evolving documentation. A systematic literature review identifies quality criteria used to assess the correctness of written agile requirements and consolidates evidence across selected studies. Sixteen papers are used to derive sixteen studies’ coverage, yielding 28 distinct quality criteria. The findings categorize and analyze these criteria, compare them with traditional requirements engineering, and provide practitioner recommendations and a research agenda.",{"@graph":63,"@context":119},[64,80,102],{"@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":36,"@type":70,"position":76},"https://docshare.wps.com/template/forms/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/a-systematic-literature-review-on-quality-criteria-for-agile-requirements-specifications-quality-criteria-and-recommendations/244195/",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/a-systematic-literature-review-on-quality-criteria-for-agile-requirements-specifications-quality-criteria-and-recommendations/244195.png","ImageObject",442,249,{"name":88,"@type":89},"Đào","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-22","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":101},"InteractionCounter",{"@type":100},"ViewAction",6,{"@type":103,"mainEntity":104},"FAQPage",[105,111,115],{"name":106,"@type":107,"acceptedAnswer":108},"What motivates the study of quality criteria for agile requirements specifications?","Question",{"text":109,"@type":110},"Agile methods rely less on up-front standardized documentation, making the correctness of written agile requirements increasingly important when face-to-face communication is not available.","Answer",{"name":112,"@type":107,"acceptedAnswer":113},"What is the main research question of the systematic literature review?",{"text":114,"@type":110},"The review asks which known quality criteria exist for agile requirements specifications.",{"name":116,"@type":107,"acceptedAnswer":117},"What does the paper provide to practitioners and researchers?",{"text":118,"@type":110},"It categorizes and analyzes quality criteria from selected papers, compares them with traditional requirements engineering, offers recommendations for quality assessment, and outlines open points as a research agenda.","https://schema.org",{"og:url":78,"og:type":121,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":123,"canonical":78},"index,follow",{"doc_id":125,"site_id":56},244195,1790437169,{"code":4,"msg":5,"data":128},{"doc_id":125,"user_id":129,"nickname":88,"user_avatar":130,"doc_module":9,"category_id":35,"category_name":36,"doc_title":59,"doc_description":61,"doc_content":131,"file_id":132,"file_url":133,"file_type":134,"file_size":135,"view_count":101,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":136,"language":137,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":138,"faqs":139,"seo_title":140,"seo_description":61,"update_tm":141,"read_time":8},1374402968488,"https://ap-avatar.wpscdn.com/davatar_29158cc5080c5b710cf443261637dec0","Software Quality Journal manuscript No.  \n(will be inserted by the editor)  \nA Systematic Literature Review on Quality Criteria for Agile Requirements Specifications  \nPetra Heck 􀀁 Andy Zaidman  \nReceived: date / Accepted: date  \nAbstract The quality of requirements is typically considered as an important factor for the quality of the end product. For traditional up-front requirements specifications a number of standards have been defined on what constitutes good quality: requirements should be complete, unambiguous, specific, time-bounded, consistent, etc. For agile requirements specifications no new standards have been defined yet and it is not clear yet whether traditional quality criteria still apply. To investigate what quality criteria for assessing the correctness of written agile requirements exist, we have conducted a systematic literature review. Thereview resulted in a list of 16 selected papers on this topic. These selected papers describe 28 different quality criteria for agile requirements specifications. We categorize and analyze these criteria and compare them with those from traditional requirements engineering. We discuss findings from the 16 papers in the form of recommendations for practitioners on quality assessment of agile requirements. At the same time we indicate the open points in the form of a research agenda for researchers working on this topic.  \nKeywords Agile Requirement 􀀁 Just-in-Time 􀀁 Quality Assessment 􀀁 Systematic Literature Review 􀀁 Quality Criteria 􀀁 Correctness  \nP. Heck  \nFontys Applied University, Eindhoven, the Netherlands Tel.: +31-8850-89716  \n[E-mail: p.heck@fontys.nl](E-mail: p.heck@fontys.nl)  \nA. Zaidman  \nDelft University of Technology, the Netherlands  \n1 Introduction  \nRequirements engineering has been perceived as one of the key steps in successful software development since the early days of software engineering (Sillitti and Succi 2005) . Sillitti and Succi mention several standards for requirements elicitation and management, such as IEEE-830 Recommended Practice for Software Requirements Specification (IEEE 1998), that have been developed for traditional requirements engineering. They claim that agile methods do not rely on standards. Inayat et al. (2014) observe that agile requirements engineering solves the initial vagueness of agile requirements not by documenting according to standards, but by e.g., face-to-face communication or prototyping. On the other hand they remark that the practice of less documentation poses a challenge in many situations (e.g., distributed teams, large teams, complex projects) that require documented agile requirements that are fully elaborated in writing. As soon as agile teams cannot rely on face-to-face communication the correctness of written documentation becomes more and more important.  \nStandards such as IEEE-830 (IEEE 1998) define criteria for this correctness: requirement specifications should be complete, unambiguous, specific, time-bounded, consistent, etc. However, this standard focuses on traditional up-front requirements specifications. These are requirements sets that are completely specified (and used as a contract) before the start of design and development. As said, agile methods do not tend to follow such standards. However both research (Eberlein and Leite 2002; Inayat et al. 2014) and findings in practice (see e.g., Heck and Zaidman (2014) and the empirical study of Kassab (2014)) suggest that quality of requirements specifications is also an important topic for agile requirements engineering.  \nIn previous work we have developed a framework for quality criteria for agile requirements specifications (Heck and Zaidman 2014) . This resulted in a list of possible quality criteria for e.g. agile user stories. Working on this list we realized that we could not find any updated standards or best practices for agile requirements specifications, nor an extensive overview of quality criteria for agile requirements specifications. At the same time w","cbCaiu7YpdEbXwpi","https://ap.wps.com/l/cbCaiu7YpdEbXwpi","pdf",291583,31,"English","# Introduction\n## Background and motivation\n## Driving research question and scope","[{\"question\":\"What motivates the study of quality criteria for agile requirements specifications?\",\"answer\":\"Agile methods rely less on up-front standardized documentation, making the correctness of written agile requirements increasingly important when face-to-face communication is not available.\"},{\"question\":\"What is the main research question of the systematic literature review?\",\"answer\":\"The review asks which known quality criteria exist for agile requirements specifications.\"},{\"question\":\"What does the paper provide to practitioners and researchers?\",\"answer\":\"It categorizes and analyzes quality criteria from selected papers, compares them with traditional requirements engineering, offers recommendations for quality assessment, and outlines open points as a research agenda.\"}]","A Systematic Literature Review on Quality Criteria for Agile Requirements Specifications - Quality Criteria and Recommendations | PDF",1789213605]