[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-164296-105":53,"doc-detail-164296-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","agile-software-development-handbook-ecss-draft-standard","Agile software development handbook - ECSS draft standard","","Agile software development handbook defines description and recommendations for organizing and performing space software engineering and product assurance using an Agile approach. It covers the Agile software development lifecycle for space projects, including how to select an Agile life cycle, key roles and competences, and example Agile activities such as planning, sprint management, progress tracking, reviews, and retrospectives. It also provides guidance for software project management and integrating ECSS reviews within Agile delivery, alongside ECSS draft standard disclaimers and change-control information.",{"@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":11,"@type":70,"position":76},"https://docshare.wps.com/template/presentations/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/agile-software-development-handbook-ecss-draft-standard/164296/",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/agile-software-development-handbook-ecss-draft-standard/164296.png","ImageObject",442,249,{"name":88,"@type":89},"Clementine","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/vnd.openxmlformats-officedocument.wordprocessingml.document","2026-09-19","2026-08-31",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 is the purpose of the Agile software development handbook in ECSS?","Question",{"text":108,"@type":109},"It provides description and recommendations to organize and perform space software engineering and product assurance using an Agile approach, intended as supporting material for ECSS standards.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"How does the handbook support selecting an Agile life cycle?",{"text":113,"@type":109},"It defines guidelines for selecting Agile and analyzes key factors such as customer, supplier, project, and team context, followed by an Agile assessment process.",{"name":115,"@type":106,"acceptedAnswer":116},"Which Agile activities and roles are covered for a Scrum-like lifecycle?",{"text":117,"@type":109},"It covers roles such as Scrum master, product owner, development team, and Agile coach, and provides exemplary activities including backlog refinement, planning, sprint backlog management, progress tracking, reviews, and retrospectives.","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},164296,1788150446,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":8,"category_name":11,"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":12,"language":135,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":136,"faqs":137,"seo_title":138,"seo_description":61,"update_tm":125,"read_time":139},1374391974564,"https://ap-avatar.wpscdn.com/avatar/14000253aa45c000a9e?x-image-process=image/resize,m_fixed,w_180,h_180&k=1779874745381141002","\u0013  \u0015\n\u0013 DOCPROPERTY  \"ECSS Discipline\"  \\* MERGEFORMAT \u0014Space engineering\u0015\nThis draft is distributed to the ECSS community for Public Review.\n(Duration: 8 weeks)\nStart of Parallel Assessment: 28 March 2017\nEND of Parallel Assessment: 29 May 2017\nDRRs shall be submitted using the Online DRR form from the ECSS Website.\nDISCLAIMER (for drafts)\nThis document is an ECSS Draft Standard. It is subject to change without any notice and may not be referred to as an ECSS Standard until published as such.\n\u0013 SUBJECT  \\* FirstCap  \\* MERGEFORMAT \u0014Agile software development handbook\u0015\nECSS Secretariat\nESA-ESTEC\nRequirements & Standards Division\nNoordwijk, The Netherlands\nForeword\nThis Handbook is one document of the series of ECSS Documents intended to be used as supporting material for ECSS Standards in space projects and applications. ECSS is a cooperative effort of the European Space Agency, national space agencies and European industry associations for the purpose of developing and maintaining common standards.\nThe material in this Handbook is defined in terms of description and recommendation how to organize and perform the work of space software engineering and product assurance following an Agile approach.\nThis handbook has been prepared by the \u0013 DOCPROPERTY  \"ECSS Working Group\"  \\* MERGEFORMAT \u0014ECSS-E-HB-40-01A\u0015 Working Group, reviewed by the ECSS Executive Secretariat and approved by the ECSS Technical Authority.\nDisclaimer\nECSS does not provide any warranty whatsoever, whether expressed, implied, or statutory, including, but not limited to, any warranty of merchantability or fitness for a particular purpose or any warranty that the contents of the item are error-free. In no respect shall ECSS incur any liability for any damages, including, but not limited to, direct, indirect, special, or consequential damages arising out of, resulting from, or in any way connected to the use of this document, whether or not based upon warranty, business agreement, tort, or otherwise; whether or not injury was sustained by persons or property or otherwise; and whether or not loss was sustained from, or arose out of, the results of, the item, or any services that may be provided by ECSS.\nPublished by: \tESA Requirements and Standards Division\nESTEC, P.O. Box 299,\n2200 AG Noordwijk\nThe Netherlands\nCopyright: \t2017© by the European Space Agency for the members of ECSS\nChange log\nTable of contents\n\u0013 TOC \\o \"3-3\" \\t \"Heading 1,1,Heading 2,2\" \u0014Introduction\t\u0013 PAGEREF _Toc476642104 \\h \u00149\u0015\n1 Scope\t\u0013 PAGEREF _Toc476642105 \\h \u001410\u0015\n2 References\t\u0013 PAGEREF _Toc476642106 \\h \u001411\u0015\n3 Terms, definitions and abbreviated terms\t\u0013 PAGEREF _Toc476642107 \\h \u001413\u0015\n3.1\tTerms from other documents\t\u0013 PAGEREF _Toc476642108 \\h \u001413\u0015\n3.2\tTerms specific to the present document\t\u0013 PAGEREF _Toc476642109 \\h \u001413\u0015\n3.3\tAbbreviated terms\t\u0013 PAGEREF _Toc476642110 \\h \u001415\u0015\n4 Introduction to the Agile software development approach\t\u0013 PAGEREF _Toc476642111 \\h \u001417\u0015\n4.1\tIntroduction to Agile\t\u0013 PAGEREF _Toc476642112 \\h \u001417\u0015\n4.1.2\tAgile characteristics\t\u0013 PAGEREF _Toc476642113 \\h \u001418\u0015\n4.1.3\tLean management\t\u0013 PAGEREF _Toc476642114 \\h \u001420\u0015\n4.1.4\tAgile Methodologies\t\u0013 PAGEREF _Toc476642115 \\h \u001421\u0015\n4.2\tGeneral issues implementing Agile\t\u0013 PAGEREF _Toc476642116 \\h \u001421\u0015\n5 Guidelines for Agile life cycle selection\t\u0013 PAGEREF _Toc476642117 \\h \u001424\u0015\n5.1\tSelecting Agile\t\u0013 PAGEREF _Toc476642118 \\h \u001424\u0015\n5.2\tAnalysis of key factors for Agile selection\t\u0013 PAGEREF _Toc476642119 \\h \u001424\u0015\n5.2.1\tCustomer context\t\u0013 PAGEREF _Toc476642120 \\h \u001426\u0015\n5.2.2\tSupplier context\t\u0013 PAGEREF _Toc476642121 \\h \u001426\u0015\n5.2.3\tProject context\t\u0013 PAGEREF _Toc476642122 \\h \u001426\u0015\n5.2.4\tTeam context\t\u0013 PAGEREF _Toc476642123 \\h \u001427\u0015\n5.3\tAgile assessment process\t\u0013 PAGEREF _Toc476642124 \\h \u001428\u0015\n6 Reference Model for Scrum-like Agile software lifecycle\t\u0013 PAGEREF _Toc476642125 \\h \u001429\u0015\n6.1\tIntroduction\t\u0013 PAGEREF _Toc476642126 \\h \u001429\u0015\n6.2\tRoles and competences\t\u0013 PAGEREF _Toc476642127 \\h \u001429\u0015\n6.2.1\tScrum master\t\u0013 PAGEREF _Toc476642128 \\h \u001429\u0015\n6.2.2\tProduct owner\t\u0013 PA","cbCaicHQZVaxiDiB","https://ap.wps.com/l/cbCaicHQZVaxiDiB","docx",1314012,"English","# Introduction\n# Scope\n# References\n# Terms, definitions and abbreviated terms\n# Introduction to the Agile software development approach\n## Introduction to Agile\n## Agile characteristics\n## Lean management\n## Agile Methodologies\n# Guidelines for Agile life cycle selection\n## Selecting Agile\n## Analysis of key factors for Agile selection\n## Agile assessment process\n# Reference Model for Scrum-like Agile software lifecycle\n## Roles and competences\n## Exemplary Agile activities\n# Guidelines for Software Project Management","[{\"question\":\"What is the purpose of the Agile software development handbook in ECSS?\",\"answer\":\"It provides description and recommendations to organize and perform space software engineering and product assurance using an Agile approach, intended as supporting material for ECSS standards.\"},{\"question\":\"How does the handbook support selecting an Agile life cycle?\",\"answer\":\"It defines guidelines for selecting Agile and analyzes key factors such as customer, supplier, project, and team context, followed by an Agile assessment process.\"},{\"question\":\"Which Agile activities and roles are covered for a Scrum-like lifecycle?\",\"answer\":\"It covers roles such as Scrum master, product owner, development team, and Agile coach, and provides exemplary activities including backlog refinement, planning, sprint backlog management, progress tracking, reviews, and retrospectives.\"}]","Agile software development handbook - ECSS draft standard | DOCX",31]