{"id":848,"date":"2024-02-01T10:14:24","date_gmt":"2024-02-01T15:14:24","guid":{"rendered":"https:\/\/digital.va.gov\/software-factory\/?page_id=848"},"modified":"2025-05-12T06:31:28","modified_gmt":"2025-05-12T10:31:28","slug":"intake","status":"publish","type":"page","link":"https:\/\/digital.va.gov\/software-factory\/intake\/","title":{"rendered":"Intake"},"content":{"rendered":"

Frequently Asked Questions<\/h3>\n\n
Expand All<\/a><\/div><\/div>\n\n

Do you have a list of solutions in your inventory that you look at when you get a software request? If so, is that list public? <\/h3>\n\nThe Integrated Intake Team reviews the requirements against the current programs on the VA network and those outside as well. The input used to provide a play recommendation, not a specific solution, is derived from several repositories: Software as a Service (SaaS)\/Platform as a Service (PaaS) Marketplace, Commercial Off-the-Shelf (COTS) products available, and Low Code\/No Code (LC\/NC) options. There is not one consolidated list available to choose play recommendations from. \n\n

Do customers need to use the Software Product Management (SPM) software intake process now instead of going directly to VA Enterprise Cloud (VAEC) or VA Platform One (VAPO)? 
<\/h3>\n\nSPM\u2019s goal is to streamline the intake process for all requests to a single point of entry. We are working through the details to provide that consolidated, single front door; however, we have not reached that level of maturity and are focused on new Software Requests only for now. As we continue to fold in the additional IT services, we will provide updates to the process as additional services become available through ServiceNow.   \n\n

Intake<\/h3>\n\nVA\u2019s Software Factory (SWF) Model integrates advanced tools and innovative methodologies to deliver Better, Faster, and Safer<\/b> software solutions. This approach enhances services for our Veterans, ensuring a superior software delivery experience aligned with our commitment to The VA Way of software development and delivery. Through the SWF Model, we strive to consistently meet and exceed the needs of those we serve, driving continuous improvement and innovation. The Intake process is crucial as it ensures that all projects are carefully evaluated and aligned with our strategic goals, allowing us to allocate resources effectively and maximize impact.\n\n
\"Software<\/figure>\n\n

Play Decisions<\/h3>\n\n

Commodity, Customized Commodity, or Highly Differentiated<\/h3>\n\n\n\n
\"Diagram<\/a><\/figure>\n\nNOTE:<\/b> Deciding on the right play mirrors the act of picking the optimal tool for a job. By aligning the project’s needs with the most fitting play, the SWF Model ensures streamlined, effective, and efficient software development, always keeping VA’s strategic goals at the forefront. \n\n
\"Logo<\/figure>\n\n

Intake Resources<\/h3>\n\nAll links require PIV or CAG access. \n\n

Simplifying Software Delivery with a Centralized Intake Process<\/h3>\n\n

Does the Software Factory (SWF) replace SPM teams for delivering and managing products? 
<\/h3>\n\nRather than replacing SPM teams for delivering and managing products, the SWF model provides a framework that leverages SPM resources to deliver products using a standardized set of criteria, tools, teaming, processes, and metrics. The SWF strategy seeks to deliver better, faster, and safer software by aligning each SWF to a key play decision and ensuring that the delivery modality is optimized to the user’s needs. SPM teams work within the SWF Model to deliver and manage these products.   ","protected":false},"excerpt":{"rendered":"

Frequently Asked Questions Do you have a list of solutions in your inventory that you look at when you get a software request? If so, is that list public?  The Integrated Intake Team reviews the requirements against the current programs on the VA network and those outside as well. The input used to provide a […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"footnotes":""},"wf_page_folders":[],"class_list":["post-848","page","type-page","status-publish","hentry"],"acf":[],"meta_box":[],"_links":{"self":[{"href":"https:\/\/digital.va.gov\/software-factory\/wp-json\/wp\/v2\/pages\/848","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/digital.va.gov\/software-factory\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/digital.va.gov\/software-factory\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/digital.va.gov\/software-factory\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/digital.va.gov\/software-factory\/wp-json\/wp\/v2\/comments?post=848"}],"version-history":[{"count":72,"href":"https:\/\/digital.va.gov\/software-factory\/wp-json\/wp\/v2\/pages\/848\/revisions"}],"predecessor-version":[{"id":2680,"href":"https:\/\/digital.va.gov\/software-factory\/wp-json\/wp\/v2\/pages\/848\/revisions\/2680"}],"wp:attachment":[{"href":"https:\/\/digital.va.gov\/software-factory\/wp-json\/wp\/v2\/media?parent=848"}],"wp:term":[{"taxonomy":"wf_page_folders","embeddable":true,"href":"https:\/\/digital.va.gov\/software-factory\/wp-json\/wp\/v2\/wf_page_folders?post=848"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}