[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-241625-105":53,"doc-detail-241625-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","iso-29119-3-examples-agile-process","ISO 29119-3 Examples Agile Process","","This document outlines the agile testing process within Agile Corporation, focusing on the guidelines for deviation from organizational test practices, the degree of independence for testers, and the test environment and data requirements. It details that each team must use the same templates for requirement/story management, defect management, and test management, with test documentation templates being tailorable. Testers report to the Delivery Lead but can also report risks to the Head of Testing (HoT), who works with the Chief Technology Officer. The test organization is technically, managerially, and financially independent. Testers actively participate in self-organizing teams reporting to their Delivery Lead. Developers conduct unit and integration testing in the development environment. Testers handle story/system and system integration testing in the system test environment. Users conduct acceptance testing in the pre-production environment, alongside performance, accessibility, penetration, and disaster/recovery testing. Production verification and penetration testing occur in the production environment, utilizing obfuscated production data to remove or mask private information. The document also presents a flowchart illustrating the test documentation structure, including test policy, organizational test practices, project test plan, level and type test plans, test status report, test completion report, test model specification, test case specification, test procedure specification, test data requirements, test environment requirements, actual results and test result, test execution log, test incident report, test data readiness report, and test environment readiness report. Additionally, it provides a detailed Test Policy for Agile Corporation, emphasizing objectives of testing, adherence to ISO/IEC/IEEE 29119-2 and agile methodologies, utilization of TDD and ATDD, test organization structure, required tester training, and ethical guidelines.",{"@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/iso-29119-3-examples-agile-process/241625/",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/iso-29119-3-examples-agile-process/241625.png","ImageObject",442,249,{"name":88,"@type":89},"Graffin","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-09-20","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":79},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What is the primary purpose of testing at Agile Corporation?","Question",{"text":108,"@type":109},"The primary purpose of testing is to provide sufficient information to determine the quality and release readiness of each product under test.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"How are testers organized within Agile Corporation?",{"text":113,"@type":109},"Testers are allocated to agile development teams from a central pool, with each tester reporting to their agile Delivery Lead. Central experts are also available for test consultancy.",{"name":115,"@type":106,"acceptedAnswer":116},"What testing methodologies are utilized by Agile Corporation?",{"text":117,"@type":109},"Agile Corporation utilizes automated Test-Driven Development (TDD) for unit testing and Acceptance Test Driven Development (ATDD) for system and regression testing, aligning with ISO/IEC/IEEE 29119-2.","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},241625,1789178248,{"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":79,"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":140},3573418547284,"https://eur-avatar.wpscdn.com/davatar_994ba38a5ba835b3df7d355c54d3ed8d","ISO 29119-3  \nOverview  \n• ISO 29119-3 provides two examples of test processes:  \n• A traditional approach based on a waterfall-type process that is fully conformant to the standard.  \n• An agile process that provides an example of a “tailored” approach to conformance where the decision on what to include is risk-driven .  \n• We will look at the agile process – please look at the traditional process  \n• The standard specifies the main elements of test documentation and what they should record:  \n• 6. Organizational test process documentation  \n• 7. Test management processes documentation  \n• 8 Dynamic test processes documentation  \nOverview of test documentation  \nExample Process: Traditional  \n• Traditional Ltd is a small company that produces advanced analysis equipment for the farming industry. Some of their products are safety-critical, in the sense that incorrect analysis results risk causing the prescription of incorrect fertilizer doses (either too much or too little) . The organization is hence required to produce the product according to an international standard that demonstrates and retains evidence of correct behaviour during testing, along with solid test planning, traceability and reporting. The example project features the development of the PC-based portion of a product called UV/TRT-14 33a. It is an apparatus to measure fertilizer components and their concentration in earth samples. The apparatus has a user interface working on a PC with wireless connection to the measuring system.  \nExample Process: Agile  \nTest Policy: Agile  \nTest Policy: Agile  \nOrganizational Test Practices: Agile  \nOrganizational Test Practices: Agile  \nOrganizational Test Practices: Agile","cbCaiusx5r4jX9Yk","https://ap.wps.com/l/cbCaiusx5r4jX9Yk","pdf",2570328,20,"English","# Test Policy – Agile Corporation\n# Organizational Test Practices – Agile\n## Guidelines for deviation from Organizational Test Practices\n## Degree of independence\n## Test environment & data","[{\"question\":\"What is the primary purpose of testing at Agile Corporation?\",\"answer\":\"The primary purpose of testing is to provide sufficient information to determine the quality and release readiness of each product under test.\"},{\"question\":\"How are testers organized within Agile Corporation?\",\"answer\":\"Testers are allocated to agile development teams from a central pool, with each tester reporting to their agile Delivery Lead. Central experts are also available for test consultancy.\"},{\"question\":\"What testing methodologies are utilized by Agile Corporation?\",\"answer\":\"Agile Corporation utilizes automated Test-Driven Development (TDD) for unit testing and Acceptance Test Driven Development (ATDD) for system and regression testing, aligning with ISO/IEC/IEEE 29119-2.\"}]","ISO 29119-3 Examples Agile Process | PDF",7]