[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-163147-105":53,"doc-detail-163147-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","process-asset-library-product-documentation-process-maps","Process Asset Library - Product Documentation Process Maps","","Product Documentation Process Maps define required deliverables and workflows for the Office of Information and Technology (OIT). The process establishes how documentation artifacts are developed in line with standards and best practices so they remain accurate, complete, clear, and usable by internal teams and end users. It covers planning via a Project Management Plan, creation of deployment and installation guides, technical manuals, user guides, optional online help, version description documentation, and structured review and peer review activities.",{"@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/process-asset-library-product-documentation-process-maps/163147/",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/process-asset-library-product-documentation-process-maps/163147.png","ImageObject",442,249,{"name":88,"@type":89},"Dozel","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/vnd.openxmlformats-officedocument.wordprocessingml.document","2026-09-28","2026-08-31",true,{"@type":98,"interactionType":99,"userInteractionCount":101},"InteractionCounter",{"@type":100},"ViewAction",6,{"@type":103,"mainEntity":104},"FAQPage",[105,111,115],{"name":106,"@type":107,"acceptedAnswer":108},"What is the purpose of the Product Documentation process for OIT?","Question",{"text":109,"@type":110},"It provides required documentation artifacts aligned to defined requirements and processes, ensuring accuracy, completeness, clarity, and usability for both internal teams and end users during development and sustainment.","Answer",{"name":112,"@type":107,"acceptedAnswer":113},"Which key goals does the process address?",{"text":114,"@type":110},"It covers maintaining the Project Management Plan, creating deployment/installation and back-out/rollback guides, producing technical manuals or POMs, creating user guides, maintaining VDD, and optionally creating online help.",{"name":116,"@type":107,"acceptedAnswer":117},"What determines whether release notes are required?",{"text":118,"@type":110},"The project manager, as the authoritative source in consultation with the technical writer, decides based on whether changes involve major technical specification or end-user functionality impacts.","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},163147,1788138768,{"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":35,"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":126,"read_time":101},962085662650,"https://ap-avatar.wpscdn.com/davatar_29158cc5080c5b710cf443261637dec0","Product Documentation\nProcess Asset Library\u000bOffice of Information and Technology\nTable of Contents\n\u0013 TOC \\h \\z \\u \\t \"Heading 2,1,Heading 3,2,Heading 4,3\" \u0014\u0013 HYPERLINK \\l \"_Toc225242272\" \u0014Process Maps: Product Documentation\t\u0013 PAGEREF _Toc225242272 \\h \u00141\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc225242273\" \u0014Product Documentation: Description and Goals\t\u0013 PAGEREF _Toc225242273 \\h \u00142\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc225242274\" \u0014Description\t\u0013 PAGEREF _Toc225242274 \\h \u00142\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc225242275\" \u0014Goals\t\u0013 PAGEREF _Toc225242275 \\h \u00142\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc225242276\" \u0014Business Problem?\t\u0013 PAGEREF _Toc225242276 \\h \u00142\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc225242277\" \u0014Associated Activities Information\t\u0013 PAGEREF _Toc225242277 \\h \u00143\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc225242278\" \u0014Activity Name: (DOC-01) Maintain Project Management Plan\t\u0013 PAGEREF _Toc225242278 \\h \u00143\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc225242279\" \u0014Activity Name: (DOC-02) Create Deployment, Installation, Back-Out, and Rollback Guide\t\u0013 PAGEREF _Toc225242279 \\h \u00144\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc225242280\" \u0014Activity Name: (DOC-03) Create Technical Manual or Production Operations Manual (POM)\t\u0013 PAGEREF _Toc225242280 \\h \u00145\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc225242281\" \u0014Activity Name: (DOC-04) Create User Guide(s)\t\u0013 PAGEREF _Toc225242281 \\h \u00147\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc225242282\" \u0014Activity Name: (DOC-05) GUI or Web-based Software?\t\u0013 PAGEREF _Toc225242282 \\h \u00148\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc225242283\" \u0014Activity Name: (DOC-06) Create Online Help for GUI and Web-based Software\t\u0013 PAGEREF _Toc225242283 \\h \u00149\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc225242284\" \u0014Activity Name: (DOC-07) Maintain Version Description Document (VDD)\t\u0013 PAGEREF _Toc225242284 \\h \u001410\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc225242285\" \u0014Activity Name: (DOC-08) Conduct Peer Review of Product Documentation\t\u0013 PAGEREF _Toc225242285 \\h \u001412\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc225242286\" \u0014Activity Name: (DOC-09) Conduct Formal Review of Product Documentation\t\u0013 PAGEREF _Toc225242286 \\h \u001413\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc225242287\" \u0014Associated Tools and Websites Information\t\u0013 PAGEREF _Toc225242287 \\h \u001415\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc225242288\" \u0014Associated Artifacts Information\t\u0013 PAGEREF _Toc225242288 \\h \u001415\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc225242289\" \u0014Associated Standards Information\t\u0013 PAGEREF _Toc225242289 \\h \u001416\u0015\u0015\n\u0013 HYPERLINK \\l \"_Toc225242290\" \u0014Associated Acronyms\t\u0013 PAGEREF _Toc225242290 \\h \u001416\u0015\u0015\n\u0015\nProcess Maps: Product Documentation\nProduct Documentation: Description and Goals\nDescription\nThis process provides required artifacts for the Office of Information and Technology (OIT) currently defined requirements and processes. It ensures necessary documentation is developed according to standards and best practices and is accurate, complete, and clear for both internal teams and end users for continued development and sustainment efforts.\nGoals\nMaintain Project Management Plan (PMP)\nCreate Deployment, Installation, Back-Out, and Rollback Guide\nCreate Production Operations Manual (POM) or Technical Manual (for VistA applications)\nCreate User Guide(s)\nCreate Online Help (optional)\nMaintain Version Description Document (VDD)\nBusiness Problem?\nHow does a project develop or update required artifacts for the Office of Information and Technology (OIT) currently defined requirements and processes, ensuring accurate, complete, and clear documentation is available to both internal teams and end users for both continued development and sustainment efforts?\nAssociated Activities Information\nActivity Name: (DOC-01) Maintain Project Management Plan\nPrevious Activity\nProcess Begins\nActivity Description\nThe Project Manager, in conjunction with the Stakeholder designated Project Team Membership, updates the Project Management Plan and obtains Sponsor and Member signatures as required.\nResponsible Role\nProject Manager\nAccountable Role\nProgram Manager\nConsulted Role\nStakeholders\u000bTechnical Writer\nInformed Role\nApplication Project Team\nConcurrent Activity\nDOC-02: Create Deployment, Installation, Back-Out, and Rollback Guide\u000bDOC-03: Create Technical Manual or Production Operations Manual (POM)\u000bDOC-04: Create User Guide(s)","cbCaifo9zud1WKqQ","https://ap.wps.com/l/cbCaifo9zud1WKqQ","docx",196614,"English","# Process Maps: Product Documentation\n## Product Documentation: Description and Goals\n## Description\n## Goals\n## Business Problem?\n## Associated Activities Information\n## Associated Tools and Websites Information\n## Associated Artifacts Information\n## Associated Standards Information\n## Associated Acronyms","[{\"question\":\"What is the purpose of the Product Documentation process for OIT?\",\"answer\":\"It provides required documentation artifacts aligned to defined requirements and processes, ensuring accuracy, completeness, clarity, and usability for both internal teams and end users during development and sustainment.\"},{\"question\":\"Which key goals does the process address?\",\"answer\":\"It covers maintaining the Project Management Plan, creating deployment/installation and back-out/rollback guides, producing technical manuals or POMs, creating user guides, maintaining VDD, and optionally creating online help.\"},{\"question\":\"What determines whether release notes are required?\",\"answer\":\"The project manager, as the authoritative source in consultation with the technical writer, decides based on whether changes involve major technical specification or end-user functionality impacts.\"}]","Process Asset Library - Product Documentation Process Maps | DOCX"]