[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-240805-105":53,"doc-detail-240805-en":119},{"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":112,"head_meta":114,"extra_data":116,"updated_unix":118},105,"en","manageit-templates","ManageIt Templates","","Project management document templates focused on defining and communicating key decisions and plans across a project lifecycle. Includes structured aids for drafting a project charter, setting drivers and priorities, building a project plan with goals and schedules, and preparing risk matrices. Also provides templates for system test strategy, weekly status reporting, project team meeting agendas, and beta test plans, including selection criteria, entry/exit conditions, and milestone-based scheduling.",{"@graph":63,"@context":111},[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/manageit-templates/240805/",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/manageit-templates/240805.png","ImageObject",442,249,{"name":88,"@type":89},"Gloria","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-24","2026-09-11",true,{"@type":98,"interactionType":99,"userInteractionCount":101},"InteractionCounter",{"@type":100},"ViewAction",9,{"@type":103,"mainEntity":104},"FAQPage",[105],{"name":106,"@type":107,"acceptedAnswer":108},"What information does the System Test Strategy template require?","Question",{"text":109,"@type":110},"It includes product revision and overview, product history, features to be tested and not tested, included/excluded configurations, environmental requirements, test approach, entry/exit criteria, and referenced documents for clarity.","Answer","https://schema.org",{"og:url":78,"og:type":113,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":115,"canonical":78},"index,follow",{"doc_id":117,"site_id":56},240805,1791072361,{"code":4,"msg":5,"data":120},{"doc_id":117,"user_id":121,"nickname":88,"user_avatar":122,"doc_module":9,"category_id":35,"category_name":36,"doc_title":59,"doc_description":61,"doc_content":123,"file_id":124,"file_url":125,"file_type":126,"file_size":127,"view_count":101,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":128,"language":129,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":130,"faqs":131,"seo_title":132,"seo_description":61,"update_tm":133,"read_time":79},2336474459895,"https://ap-avatar.wpscdn.com/avatar/22000baeef7a5ed0655?x-image-process=image/resize,m_fixed,w_180,h_180&k=1786071322749376916","Templates from  \nProject Charter Template  \n1. Vision: Concise and compelling idea behind the project  \n2. Drivers, Constraints, and Floats: What’s driving the project, what’s constraining the project, and where you have freedom to organize the project as you need.  \n3. Goals: What you might want to accomplish with the project, but not required that you do so  \n4. Success Criteria: Capabilities your product will have at the end of the project  \n5. ROI Estimate: Potential return from your project (only if your organization requires it)  \nSee the discussion in Write a Project Charter to Share These Decisions, page 11 for more details.  \n© 2007 Johanna Rothman. Use and adapt these templates. 2  \nNote: Your organization may need you to put “Company Confidential” or some other confidentiality note on each page.  \nProject Driver Matrix  \n\n| Project Priority | Rank |\n| --- | --- |\n| Release date |  |\n| Feature set |  |\n| Low defects |  |\n| Cost to release |  |\n| People and their capabilities |  |\n| Work environment |  |\n\nSee the discussion is Decide on a Driver for Your Project, p. 7 for help in defining this matrix for your project.  \n© 2007 Johanna Rothman. Use and adapt these templates. 3  \nNote: Your organization may need you to put “Company Confidential” or some other confidentiality note on each page.  \nProject Plan  \n1. Product purpose: The value of this product to your organization  \n2. History: If this is a follow-on release, briefly describe the product history  \n3. Release Criteria: The few vital product deliverables ofthe product.  \n4. Goals: Consider project, product, or team goals.  \n5. Proposed schedule: Major milestones only. If you have alternative proposals for the project, explain the schedule for each option  \n6. Project staffing: Curve of who will be on the project when  \n7. Risk list: Include the risk list here or a pointer to it  \nSee the discussion in Develop a Project Plan Template, p. 19 for more details.  \n© 2007 Johanna Rothman. Use and adapt these templates. 4  \nNote: Your organization may need you to put “Company Confidential” or some other confidentiality note on each page.  \nProject Risk Matrix  \nSee the discussion of the risk matrix on p. 25, Develop a Project Risk List, and following for more examples of and information about risks.  \n© 2007 Johanna Rothman. Use and adapt these templates. 5  \nNote: Your organization may need you to put “Company Confidential” or some other confidentiality note on each page.  \nSystem Test Strategy  \n1. Product revision and overview: Differentiate this project from any others in system test  \n2. Product history: Include defect or technical debt history  \n3. Features to be tested: Itemize the features to be tested  \n4. Features Not to be tested: Itemize the features that will not be tested  \n5. Configurations included and excluded: Make a list of all configurations, hardware and software  \n6. Environmental requirements: Discuss the necessary testing environment  \n7. System test approach: Discuss how you will integrate testing into the project  \n8. System test entry criteria: How the whole team will know when the system is ready for system test  \n9. System test exit criteria: How the whole team will know when the system test is complete  \n10. Other documents referenced: You may need to reference the project plan or schedule or risk list to make your strategy clear  \nSee the discussion in Define a Test Strategy for Your Project, starting on p. 273 for more details.  \n© 2007 Johanna Rothman. Use and adapt these templates. 6  \nNote: Your organization may need you to put “Company Confidential” or some other confidentiality note on each page.  \nWeekly Status Report  \nStatus report for \u003Cperson> for week ending mm/dd/yy  \nAccomplishments: Bullets or a brief paragraph (two to three sentences) of accomplishments for the past week.  \nFuture milestones:  \nTask Description Planned Date Expected Date Actual Date  \nIf you or your team member discovers there are organization forces prev","cbCaimrKRknY6ihd","https://ap.wps.com/l/cbCaimrKRknY6ihd","pdf",197605,10,"English","# Project Charter Template\n## Vision\n## Drivers, Constraints, and Floats\n## Goals\n## Success Criteria\n## ROI Estimate\n# Project Driver Matrix\n# Project Plan\n# Project Risk Matrix\n# System Test Strategy\n## Product revision and overview\n## Product history\n## Features to be tested\n## System test entry criteria\n## System test exit criteria\n# Weekly Status Report\n# Project Team Agenda\n# Beta Test Plan\n## Beta purpose\n## Beta customer selection\n## Beta entry criteria\n## Beta exit criteria\n# Program Plan","[{\"question\":\"What information does the System Test Strategy template require?\",\"answer\":\"It includes product revision and overview, product history, features to be tested and not tested, included/excluded configurations, environmental requirements, test approach, entry/exit criteria, and referenced documents for clarity.\"}]","ManageIt Templates | PDF",1789165943]