[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-243188-105":53,"doc-detail-243188-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-test-practice-improvement-version-24-march-2017","Agile Test Practice Improvement - Version 2.4 - March 2017","","Agile Test Practice Improvement outlines how testing activities and processes can be improved in agile and Scrum environments. It explains why test approaches in agile projects are often insufficient, and how a tester contributes as a “center of operations” to collaborate with analysts, developers, and users. The paper describes the intended role coverage for test activities, then guides readers on how to read the document, including skills and checkpoint-based test practices across individual, team, and organizational levels.",{"@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-test-practice-improvement-version-24-march-2017/243188/",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-test-practice-improvement-version-24-march-2017/243188.png","ImageObject",442,249,{"name":88,"@type":89},"Riley","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-19","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":8},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What problem does Agile Test Practice Improvement address in agile projects?","Question",{"text":108,"@type":109},"It addresses that, in practice, the overall testing approach and process in agile projects is often less than satisfactory, requiring improvement of test activities and test processes.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"How does the document describe the tester’s role in Scrum teams?",{"text":113,"@type":109},"It states that Scrum recognizes no sub-teams in the Development Team, but in real situations developers have a specific role, especially the tester. The document aims for each team member to be capable of performing test activities, treating “tester” as anyone performing them.",{"name":115,"@type":106,"acceptedAnswer":116},"How are test practices organized for applying the TPI NEXT® checkpoints?",{"text":117,"@type":109},"Chapter 4 describes practices based on TPI NEXT® checkpoints using three operational views: P for individual developers (Professional), T for the team as a whole, and O for organizations, programs, or projects.","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},243188,1791736616,{"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":8,"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":140,"read_time":141},1374391975076,"https://ap-avatar.wpscdn.com/avatar/14000253ca4ec9f6853?x-image-process=image/resize,m_fixed,w_180,h_180&k=1783305029341752051","Agile Test Practice Improvement  \nAGILE TPI  \nVersion 2.4 March 2017  \nVersion information  \n\n| Version | Date issued | Remarks | Author |\n| --- | --- | --- | --- |\n| 0.1 | September 5, 2014 | Initial setup and concept | Gerrit de Vries |\n| 0.2 | September 24, 2014 | Added contributions from:\u003Cbr>􀁸 Yvonne van Zaanen (Triodos)\u003Cbr>􀁸 Jos Punter (Sogeti NL)\u003Cbr>􀁸 Bert Linker (Sogeti NL)\u003Cbr>􀁸 Ben Visser (Sogeti NL) | Gerrit de Vries |\n| 0.3 | September 25 | Added contributions from: James Redpath (Sogeti USA) | Gerrit de Vries |\n| 1.0 | December 2014 | Final version | Gerrit de Vries |\n| 1.1 | Februari 2015 | Minor adjustments | Gerrit de Vries |\n| 1.2 | April 2015 | Added contributions from Arne Bergs (Sogeti DE) | Gerrit de Vries |\n| 1.3 | July 2015 | Synchronized with the ATIM tool | Gerrit de Vries |\n| 1.4 | August 2016 | ATIM changed to Agile TPI | Gerrit de Vries |\n| 2.0 | August 2016 | Synchronized with Agile TPI Tool Minor changes\u003Cbr>Input from Eric Belt and Ben Visser | Gerrit de Vries |\n| 2.4 | March 2017 | Some checkpoints adapted Synchronized with Tool 2.4\u003Cbr>Input from Eric Belt and Ben Visser | Gerrit de Vries |\n|  |  |  |  |\n\nSummary  \nAgile, Scrum and TPI  \nAgile methodologies have emphasized many excellent practices from a testing perspective such as testdriven development and exploratory testing. Nevertheless, practice also shows that the overall approach and process of testing is often less than satisfactory in agile projects.  \nLike in waterfall situations there is a need for improvement of the test activities or test processes. This aspect has been elaborated in the TPI NEXT® book Business Driven Test Process Improvement 1 , where Chapter 7.2 explains how the model can be used in agile situations.  \nHowever, we learned that organizations struggle with the implementation and use of agile methods. In many situations we see that it’s Agile ‘In Name Only’, or specific elements of Scrum are adopted like the (daily) stand ups. We also learned that the professional tester is able to contribute to the agile teams with his skills and above all experience. Through his work as a tester he becomes the ‘center of operations’, closely working together with analysts, developers and users. From this position the tester is also capable of convincing others of the benefits of testing, thus creating a quality driven mindset with other team members and stakeholders.  \nBased on our test experience and our test activities in agile environments we think that this document will help organizations, project teams and individuals apply the Agile Manifesto that states:  \n\n| We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: |  |  |\n| --- | --- | --- |\n| Individuals and interactions Working software Customer collaboration Responding to change | over\u003Cbr>over\u003Cbr>over\u003Cbr>over | processes and tools comprehensive documentation contract negotiation following a plan |\n| While there is value in the items on the right, we value the items on the left more! |  |  |\n\nAlthough ‘Agile’ has many different flavors we will use the Scrum terminology for this document, as Scrum is a commonly used methodology. Furthermore we refer to “TMap NEXT® in Scrum”2 , where the authors use the Scrum methodology as a basic starting point.  \nDeveloper or tester  \nIn the ideal situation the Scrum team will consist of developers, with no specific roles or expertise: Scrum recognizes no sub-teams in the Development Team, regardless of particular domains that need to be addressed like testing or business analysis; there are no exceptions to this rule3.  \nIn the real situation however we see that the developers do have a specific role, especially the tester. With this document we do not want to challenge the Scrum Guide but, building from the practical situation, support and improve the test activities within the teams. Furthermore with this document we aim at a situation where each team member is ","cbCaihP56uRPluh6","https://ap.wps.com/l/cbCaihP56uRPluh6","pdf",1031891,24,"English","# Summary\n## Agile, Scrum and TPI\n# Developer or tester\n## Ideal vs real Scrum situation\n# How to read\n## Chapter 3: Skills for testers\n## Chapter 4: Checkpoint-based test practices\n# Tooling\n## AGILE TPI-tool and user manual","[{\"question\":\"What problem does Agile Test Practice Improvement address in agile projects?\",\"answer\":\"It addresses that, in practice, the overall testing approach and process in agile projects is often less than satisfactory, requiring improvement of test activities and test processes.\"},{\"question\":\"How does the document describe the tester’s role in Scrum teams?\",\"answer\":\"It states that Scrum recognizes no sub-teams in the Development Team, but in real situations developers have a specific role, especially the tester. The document aims for each team member to be capable of performing test activities, treating “tester” as anyone performing them.\"},{\"question\":\"How are test practices organized for applying the TPI NEXT® checkpoints?\",\"answer\":\"Chapter 4 describes practices based on TPI NEXT® checkpoints using three operational views: P for individual developers (Professional), T for the team as a whole, and O for organizations, programs, or projects.\"}]","Agile Test Practice Improvement - Version 2.4 - March 2017 | PDF",1789201019,8]