[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-241621-105":53,"doc-detail-241621-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","leading-practice-test-strategy-and-approach-in-agile-projects","Leading Practice - Test Strategy and Approach in Agile Projects","","This document provides best practices for strategizing testing of CA Project and Portfolio Management (CAPPM) within agile delivery. It defines how agile teams plan and execute testing across sprints without supplying detailed test cases, which are delivered separately. It describes testing approaches, roles and responsibilities, environments, automation tools, risk analysis, and procedures for tracking defects and linking acceptance criteria to backlog items. It also outlines test actor setup and key testing types from unit to feature testing leading into UAT.",{"@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":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/leading-practice-test-strategy-and-approach-in-agile-projects/241621/",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/leading-practice-test-strategy-and-approach-in-agile-projects/241621.png","ImageObject",442,249,{"name":88,"@type":89},"McGucket","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-14","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":101},"InteractionCounter",{"@type":100},"ViewAction",8,{"@type":103,"mainEntity":104},"FAQPage",[105,111,115],{"name":106,"@type":107,"acceptedAnswer":108},"What is covered in this document versus the separate test-case document?","Question",{"text":109,"@type":110},"This document explains testing strategy, roles, environments, and execution approach for CA CAPPM in agile projects. It does not include specific test cases; test case lists and steps are provided in a separate document.","Answer",{"name":112,"@type":107,"acceptedAnswer":113},"How should testing activities be organized across agile sprints?",{"text":114,"@type":110},"Feature testing should occur throughout each sprint, with final user acceptance testing (UAT) performed in the testing sprint before the system goes live. Sprint test plans should be created and reviewed during each sprint planning meeting.",{"name":116,"@type":107,"acceptedAnswer":117},"How should acceptance criteria be handled during release planning?",{"text":118,"@type":110},"During release planning, the team should capture acceptance criteria and immediately add them as logical test cases linked to the product backlog item, so testing remains aligned to backlog priorities.","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},241621,1791309501,{"code":4,"msg":5,"data":128},{"doc_id":125,"user_id":129,"nickname":88,"user_avatar":130,"doc_module":9,"category_id":8,"category_name":11,"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":73},1236954412713,"https://us-avatar.wpscdn.com/davatar_29158cc5080c5b710cf443261637dec0","CA SERVICES | LEADING PRACTICE  \nLeading Practice:  \nTest Strategy and Approach in Agile Projects  \nAbstract  \nThis document provides best practices on how to strategize testing CA Project and Portfolio Management (CAPPM) in an agile project. The document does not include specific test cases; the list of test cases and steps for each test case are provided in a separate document.  \nThis document should be used by the agile project team that is planning the testing activities, and by end users who perform user acceptance testing (UAT) .  \nConcepts  \n\n| Concept Description |  |\n| --- | --- |\n| Test Approach | Defines testing strategy, roles and responsibilities of various team members, and test types. |\n| Testing Environments | Outlines which testing is carried out in which environment. |\n| Testing Automation and Tools | Addresses test management and automation tools required for test execution. |\n| Risk Analysis | Defines the approach for risk identification and plans to mitigate risks as well as a contingency plan. |\n| Test Planning and Execution | Defines the approach to plan the test cases, test scripts, and execution. |\n| Review and Approval Lists individuals who should review, approve and sign off on test results. |  |\n\nTest Approach  \nThe test approach defines testing strategy, roles and responsibilities of various team members, and the test types.  \nThe first step is to define the testing strategy. It should describe how and when the testing will be conducted, who will do the testing, the type of testing being conducted, features being tested, environment(s) where the testing takes place, what testing tools are used, and how are defects tracked and managed. The testing strategy should be prepared by the agile core team. In an agile project:  \n• Feature testing occurs throughout each sprint with the final user acceptance testing (UAT) conducted in the testing sprint before going live.  \n• During the release planning meeting, the team should capture acceptance criteria and immediately add them as logical test cases linked to the product backlog item.  \n• In each sprint planning meeting, a sprint test plan should be created and reviewed.  \n• As the testing is done in each sprint, the results should be tracked along with which features have been successfully tested and which ones have defects. These results should be passed back to the CA consultant who can fix the defects.  \n• Care should be taken to distinguish defects and changes in requirements. If the team requires a change in requirement, this should be added to the product backlog and prioritized.  \nTest Actors  \nTo efficiently test the various rights assigned to the various security groups, the team should create a mini test organization by following these steps:  \n• Identify and create the various actors (‘test actors’) whose CA PPM access rights must be validated. Usually this would represent one actor for each CA PPM security group.  \n• If a reporting organizational business structure (OBS) is used in the system, create the appropriate reporting relationship for the test actors.  \n• Validate the CA PPM access rights for each of the security groups by logging in as the test actor and execute each test case.  \n• When the system goes live, the test actors should be de-activated. Whenever there is a need to conduct use case or system validation, test actors can be re-activated.  \nIn this sample organization, the following actors could be required:  \n• Project manager or scrum master (PM1, PM2)  \n• Idea manager  \n• Project team member (TM1, TM2)  \n• Resource or capacity manager  \n• Scrum product owner (presuming the organization uses this role)  \n• Project stakeholders/executives (persons interested in the project, but is not assigned any specific tasks)  \n• PMO/IT requestor  \n• IT Finance team member  \n• Governance board member  \n• Project accounting team member  \nDepending upon the test cases, these actors may need to be set up for each business unit.  \nTypes of Test","cbCaikfupanQFGlv","https://ap.wps.com/l/cbCaikfupanQFGlv","pdf",337374,6,"English","# Leading Practice: Test Strategy and Approach in Agile Projects\n## Concepts\n## Test Approach\n## Test Actors\n## Types of Testing\n### Unit Testing\n### Feature Testing","[{\"question\":\"What is covered in this document versus the separate test-case document?\",\"answer\":\"This document explains testing strategy, roles, environments, and execution approach for CA CAPPM in agile projects. It does not include specific test cases; test case lists and steps are provided in a separate document.\"},{\"question\":\"How should testing activities be organized across agile sprints?\",\"answer\":\"Feature testing should occur throughout each sprint, with final user acceptance testing (UAT) performed in the testing sprint before the system goes live. Sprint test plans should be created and reviewed during each sprint planning meeting.\"},{\"question\":\"How should acceptance criteria be handled during release planning?\",\"answer\":\"During release planning, the team should capture acceptance criteria and immediately add them as logical test cases linked to the product backlog item, so testing remains aligned to backlog priorities.\"}]","Leading Practice - Test Strategy and Approach in Agile Projects | PDF",1789178236]