36C10B24R0052 0001.docx
DOCX document 57 KB Posted
- Solicitation number
- 36C10B24R0052
About this file
This document is a Performance Work Statement (PWS) for Behavior Driven Development (BDD) training in support of the Department of Veterans Affairs (VA) Office of Management, Financial Management Business Transformation (FMBT) program. The PWS outlines the requirements for the contractor to provide certified BDD instructor(s), training materials, and a 2-day training session for up to 25 participants. Key details include:
The training will be delivered in a hybrid format with the instructor onsite, and the contractor must provide the training materials in electronic format at least 5 days prior to the session. The instructor must have a Scaled Agile Framework (SAFe) certification and at least 5 years of experience teaching or facilitating BDD training, with a preference for Certified SAFe Agile Software Engineer experience and federal agency experience. The training is to be tool-agnostic, focusing on the BDD methodology rather than specific software tools. The PWS also includes general IT and enterprise framework requirements for the contractor to follow, such as the Veteran Focused Integration Process (VIP) and Product Line Management (PLM).
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 36C10B24R0052_3.docx | DOCX document | |
| 36C10B24R0052_2.docx | DOCX document | |
| 36C10B24R0052 - BDD Training.docx | DOCX document | |
| 36C10B24R0052_1.docx | DOCX document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
36C10B24R0052 0001
5. PROJECT NUMBER (if applicable)
CODE
7. ADMINISTERED BY
2. AMENDMENT/MODIFICATION NUMBER
CODE
6. ISSUED BY
8. NAME AND ADDRESS OF CONTRACTOR
4. REQUISITION/PURCHASE REQ. NUMBER
3. EFFECTIVE DATE
9A. AMENDMENT OF SOLICITATION NUMBER
9B. DATED
PAGE OF PAGES
10A. MODIFICATION OF CONTRACT/ORDER NUMBER
10B. DATED
BPA NO.
1. CONTRACT ID CODE
FACILITY CODE
CODE
Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:
The above numbered solicitation is amended as set forth in Item 14 The hour and date specified for receipt of Offers
E. IMPORTANT:
is extended,
(a) By completing Items 8 and 15, and returning __________ copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c) By separate letter or electronic communication which includes a reference to the solicitation and amendment numbers
FAILURE OF YOUR
ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY is not extended.
12. ACCOUNTING AND APPROPRIATION DATA
(REV. 11/2016)
is required to sign this document and return ___________ copies to the issuing office.
is not, A. THIS CHANGE ORDER IS ISSUED PURSUANT TO:
Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER NO. IN ITEM 10A.
15C. DATE SIGNED
B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).
RESULT IN REJECTION OF YOUR OFFER
If by virtue of this amendment you desire to change an offer already submitted, such change may be made by letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.
C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:
D. OTHER
Contractor
16C. DATE SIGNED
14. DESCRIPTION OF AMENDMENT/MODIFICATION
16B. UNITED STATES OF AMERICA
Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.
15A. NAME AND TITLE OF SIGNER
16A. NAME AND TITLE OF CONTRACTING OFFICER
15B. CONTRACTOR/OFFEROR
STANDARD FORM 30
PREVIOUS EDITION NOT USABLE
Prescribed by GSA - FAR (48 CFR) 53.243 (Type or print) (Type or print) (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)
(Number, street, county, State and ZIP Code) (If other than Item 6) (Specify type of modification and authority) (such as changes in paying office, appropriation date, etc.)
(If required)
(SEE ITEM 11)
(SEE ITEM 13)
(X)
CHECK
ONE
13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS,
IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.
11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT
(Signature of person authorized to sign) (Signature of Contracting Officer)
VA-24-00103371
Department of Veterans Affairs Technology Acquisition Center 23 Christopher Way Eatontown NJ 07724 Department of Veterans Affairs Technology Acquisition Center 23 Christopher Way Eatontown NJ 07724 To all Offerors/Bidders
36C10B24R0052 09-05-2024
X X X
See Page 2
Kendra M. Casebolt Contracting Officer
1. The purpose of this amendment is to provide a revised Section B.4, Performance Work Statement (PWS). The PWS revision provides additional information to section 4.0, Specific Tasks and Deliverables. Please see PWS section 4.0 yellow highlighted paragraph.
2. Except as provided herein, all other terms and conditions remain unchanged and in effect.
B.4 PERFORMANCE WORK STATEMENT
36C10B24R0052 0001
Page 1 of Page 1 of
PERFORMANCE WORK STATEMENT (PWS)
DEPARTMENT OF VETERANS AFFAIRS
OFFICE OF INFORMATION & TECHNOLOGY
OFFICE OF MANAGEMENT, FINANCIAL MANAGEMENT BUSINESS TRANSFORMATION (FMBT)
BEHAVIOR DRIVEN DEVELOPMENT (BDD) TRAINING
Date: August 26, 2024
VA-24-00103371
PWS Version Number: 2.0
1.0 DESCRIPTION OF SERVICES
The Department of Veterans Affairs (VA), Office of Management, Financial Management Business Transformation (FMBT) program is seeking Behavior Driven Development (BDD) training. FMBT wants to enhance current agile software development practices with BDD methods to foster collaboration among customers, developers, and testers in defining desired system behaviors.
2.0 APPLICABLE DOCUMENTS
In the performance of the tasks associated with this Performance Work Statement, the Contractor shall comply with the following:
| 1. | 44 U.S.C. § 3541-3549, “Federal Information Security Management Act (FISMA) of 2002” |
| 2. | “Federal Information Security Modernization Act of 2014” |
| 3. | Federal Information Processing Standards (FIPS) Publication 140-2, “Security Requirements for Cryptographic Modules” |
| 4. | FIPS Pub 199. “Standards for Security Categorization of Federal Information and Information Systems,” February 2004 |
| 5. | FIPS Pub 200, “Minimum Security Requirements for Federal Information and Information Systems,” March 2006 |
| 6. | FIPS Pub 201-2, “Personal Identity Verification of Federal Employees and Contractors,” August 2013 |
| 7. | 10 U.S.C. § 2224, "Defense Information Assurance Program" |
| 8. | 5 U.S.C. § 552a, as amended, “The Privacy Act of 1974” |
| 9. | Public Law 109-461, Veterans Benefits, Health Care, and Information Technology Act of 2006, Title IX, Information Security Matters |
| 10. | 42 U.S.C. § 2000d “Title VI of the Civil Rights Act of 1964” |
| 11. | VA Directive 0710, “Personnel Security and Suitability Program,” June 4, 2010, https://www.va.gov/vapubs/index.cfm |
| 12. | VA Handbook 0710, Personnel Security and Suitability Program,” May 2, 2016, https://www.va.gov/vapubs/index.cfm |
| 13. | VA Directive and Handbook 6102, “Internet/Intranet Services,” August 5, 2019 |
| 14. | 36 C.F.R. Part 1194 “Information and Communication Technology Standards and Guidelines,” January 18, 2017 |
| 15. | OMB Circular A-130, “Managing Federal Information as a Strategic Resource,” July 28, 2016 |
| 16. | 32 C.F.R. Part 199, “Civilian Health and Medical Program of the Uniformed Services (CHAMPUS)” |
| 17. | NIST SP 800-66 Rev. 1, “An Introductory Resource Guide for Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule,” October 2008 |
| 18. | Sections 504 and 508 of the Rehabilitation Act (29 U.S.C. § 794d), as amended, January 18, 2017 |
| 19. | Homeland Security Presidential Directive (12) (HSPD-12), August 27, 2004 |
| 20. | VA Directive 6500, “VA Cybersecurity Program,” February 24, 2021 |
| 21. | VA Handbook 6500, “Risk Management Framework for VA Information Systems VA Information Security Program,” February 24, 2021 |
| 22. | VA Handbook 6500.2, “Management of Breaches Involving Sensitive Personal Information (SPI),” March 12, 2019 |
| 23. | VA Handbook, 6500.5, “Incorporating Security and Privacy in System Development Lifecycle.” March 22, 2010 |
| 24. | VA Handbook 6500.6, “Contract Security,” March 12, 2010 |
| 25. | VA Handbook 6500.8, “Information System Contingency Planning,” April 6, 2011 |
| 26. | VA Handbook 6500.10, “Mobile Device Security Policy,” February 15, 2018 |
| 27. | VA Handbook 6500.11, “VA Firewall Configuration,” August 22, 2017 |
| 28. | OIT Process Asset Library (PAL), https://www.va.gov/process. Reference Process Maps at https://www.va.gov/process/maps.asp and Artifact templates at https://www.va.gov/process/artifacts.asp |
| 29. | One VA Technical Reference Model (TRM) (reference at https://www.va.gov/trm/TRMHomePage.aspx) |
| 30. | National Institute Standards and Technology (NIST) Special Publications |
| 31. | VA Directive 6508, “Implementation of Privacy Threshold Analysis and VA Privacy Impact Assessment,” October 15, 2014 |
| 32. | VA Handbook 6508.1, “Procedures for Privacy Threshold Analysis and Privacy Impact Assessment,” July 30, 2015 |
| 33. | VA Handbook 6510, “VA Identity and Access Management,” January 15, 2016 |
| 34. | VA Directive and Handbook 6513, “Secure External Connections,” October 12, 2017 |
| 35. | VA Directive 6300, “Records and Information Management,” September 21, 2018 |
| 36. | VA Handbook, 6300.1, “Records Management Procedures,” March 24, 2010 |
| 37. | NIST SP 800-37 Rev 2, “Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy,” December 2018 |
| 38. | NIST SP 800-53 Rev. 5, “Security and Privacy Controls for Federal Information Systems and Organizations,” September 23, 2020 (includes updates as of 12/10/2020) |
| 39. | VA Directive 0735, “Homeland Security Presidential Directive 12 (HSPD-12) Program,” October 26, 2015 |
| 40. | VA Handbook 0735, “Homeland Security Presidential Directive 12 (HSPD-12) Program,” March 24, 2014 |
| 41. | OMB Memorandum 05-24, “Implementation of Homeland Security Presidential Directive (HSPD) 12 – Policy for a Common Identification Standard for Federal Employees and Contractors,” August 5, 2005 |
| 42. | OMB Memorandum M-19-17, “Enabling Mission Delivery Through Improved Identity, Credential, and Access Management,” May 21, 2019 |
| 43. | OMB Memorandum, “Guidance for Homeland Security Presidential Directive (HSPD) 12 Implementation,” May 23, 2008 |
| 44. | Federal Identity, Credential, and Access Management (FICAM) Roadmap and Implementation Guidance, December 2, 2011, (NOTE: Part A of the FICAM Roadmap and Implementation Guidance, v2.0, was replaced in 2015 with an updated Architecture (https://arch.idmanagement.gov/#what-is-the-ficam-architecture) |
| 45. | NIST SP 800-116 Rev 1, “Guidelines for the Use of Personal Identity Verification (PIV) Credentials in Facility Access,” June 2018 |
| 46. | NIST SP 800-63-3, 800-63A, 800-63B, 800-63C, “Digital Identity Guidelines,” updated March 02, 2020 |
| 47. | Draft NIST SP 800-157, “Guidelines for Derived PIV Credentials,” December 2014 |
| 48. | NIST SP 800-164, “Guidelines on Hardware-Rooted Security in Mobile Devices (Draft),” October 2012 |
| 49. | Draft National Institute of Standards and Technology Interagency Report (NISTIR) 7981, ”Mobile, PIV, and Authentication,” March 2014 |
| 50. | VA Memorandum, VAIQ #7100147, “Continued Implementation of Homeland Security Presidential Directive 12 (HSPD-12),” April 29, 2011 (reference https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514 |
| 51. | IAM Identity Management Business Requirements Guidance document, May 2013, (reference https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514) |
| 52. | VA Memorandum “Personal Identity Verification (PIV) Logical Access Policy Clarification,” July 17, 2019, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896 |
| 53. | Trusted Internet Connections (TIC) 3.0 Core Guidance Documents, https://www.cisa.gov/publication/tic-30-core-guidance-documents |
| 54. | OMB Memorandum M-19-26, “Update to the Trusted Internet Connections (TIC) Initiative,” September 12, 2019 |
| 55. | OMB Memorandum M-08-23, “Securing the Federal Government’s Domain Name System Infrastructure,” August 22, 2008 |
| 56. | Sections 524 and 525 of the Energy Independence and Security Act of 2007, (Public Law 110–140), December 19, 2007 |
| 57. | Section 104 of the Energy Policy Act of 2005, (Public Law 109–58), August 8, 2005 |
| 58. | Executive Order 13834, “Efficient Federal Operations,” dated May 17, 2018 |
| 59. | Executive Order 13221, “Energy-Efficient Standby Power Devices,” August 2, 2001 |
| 60. | VA Directive 0058, “VA Green Purchasing Program,” July 19, 2013 |
| 61. | VA Handbook 0058, “VA Green Purchasing Program,” July 19, 2013 |
| 62. | Office of Information Security (OIS) VAIQ #7424808 Memorandum, “Remote Access,” January 15, 2014, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28 |
| 63. | Clinger-Cohen Act of 1996, 40 U.S.C. §11101 and §11103 |
| 64. | “Veteran Focused Integration Process (VIP) Guide 4.0,” January 2021, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371 |
| 65. | VA Memorandum “Proper Use of Email and Other Messaging Services,” January 2, 2018, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28 |
| 66. | “DevSecOps Product Line Management Playbook” version 2.0, May 2021, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946 |
| 67. | NIST SP 500-267B Revision 1, ”USGv6 Profile,” November 2020 |
| 68. | OMB Memorandum M-21-07, “Completing the Transition to Internet Protocol Version 6 (IPv6),“ November 19, 2020 |
| 69. | Social Security Number (SSN) Fraud Prevention Act of 2017 |
| 70. | Section 240 of the Consolidated Appropriations Act (CAA) 2018, March 23, 2018 |
| 3.0 | PERFORMANCE DETAILS |
| 3.1 | PERFORMANCE PERIOD |
The period of performance (PoP) shall be after contract award, training shall be scheduled and completed within 3 months.
3.2 PLACE OF PERFORMANCE
Tasks under this PWS shall be performed in VA facilities located in VA Acquisition Academy (VAAA), 7485 New Horizon Way, Frederick, MD 21703.
Training will be provided in a hybrid format (trainees will participate in-person or virtually) with the instructor onsite at the training location.
4.0 SPECIFIC TASKS AND DELIVERABLES
The Contractor shall perform the following:
1. Provide certified instructor(s), training guide and materials shall be delivered in electronic form (in pdf form) to VA Program Manager and students not later than five (5) business days prior to the Training Session start date, and expertise to facilitate an instructor-led training for a maximum of 25 participants for a duration of 2 workdays.
2. The contractor shall provide training guide and materials in English and the instructor will be able to communicate fluently in English to match the needs of the training participants.
3. The instructor shall possess a Scaled Agile Framework (SAFe) Certificatiion and demonstrate at least 5 years teaching or facilitating BDD trainings. Preferred Certified SAFe Agile Software Engineer (ASE) and experience working with federal agencies.
4. The training shall be agnostic of software tools, as the desire is to learn and understand the BDD methodology, not to learn tools that interpret BDD syntax.
| 5. | Instructor Expectations |
| • | The instructor shall present information in a clear and concise manner, explaining the content to ensure all learners understand the key topics listed in the training material. |
| • | The contractor shall ensure that the instructor is ready to present at the facility at the scheduled date and time. |
| • | Backup instructor shall be provided should the intended instructor become unavailable for scheduled date and time. |
| 6. | Session evaluations: |
| • | The COR will collect participants session evaluations and provide consolidated feedback to the Contractor Any work at the Government site shall not take place on Federal holidays or weekends unless directed by the Contracting Officer (CO). |
Deliverable:
| A. | Training Guide And Materials |
| 5.0 | GENERAL REQUIREMENTS |
| 5.1 | ENTERPRISE AND IT FRAMEWORK |
| 5.1.1 | VETERAN FOCUSED INTEGRATION PROCESS (VIP) AND PRODUCT LINE MANAGEMENT (PLM) |
The Contractor shall support VA efforts IAW the updated Veteran Focused Integration Process (VIP) and Product Line Management (PLM). The major focus of the new VIP is on Governance and Reporting and is less prescriptive, with a focus on outcomes and continuous delivery of value. Product Line Management (PLM) is a framework that focuses on delivering functional products that provide the highest priority work to customers while delivering simplified, reliable, and practical solutions to the business, medical staff, and our Veterans. The VIP Guide is a companion guide to the PLM Playbook and can be found at: https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371 and the PLM Playbook can be found at https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946. The PLM Playbook pivots from project-centric to product-centric delivery and contains descriptive practices that focuses on outcomes. The PLM Playbook contains a set of “plays” that implement Development, Security, and Operations (DevSecOps) principles and processes such as automated development, continuous integration/continuous delivery, and release on demand. The PLM Playbook details how product lines implement Lean-Agile principles, methods, practices, and techniques through levels of maturity. VIP and PLM are the authoritative processes that IT projects must follow to ensure development and delivery of IT products.
5.1.2 PROCESS ASSET LIBRARY (PAL)
The Contractor shall perform their duties consistent with the processes defined in the OIT Process Asset Library (PAL). The PAL scope includes the full spectrum of OIT functions and activities, such as VIP project management, operations, service delivery, communications, acquisition, and resource management. PAL serves as an authoritative and informative repository of searchable processes, activities or tasks, roles, artifacts, tools and applicable standards and guides to assist the OIT workforce, Government and Contractor personnel. The Contractor shall follow the PAL processes to ensure compliance with policies and regulations and to meet VA quality standards. The PAL includes the contractor onboarding process consistent with Section 6.2.2 and can be found at https://www.va.gov/PROCESS/artifacts/maps/process_CONB_ext.pdf. The main PAL can be accessed at www.va.gov/process.
5.1.3 AUTHORITATIVE DATA SOURCES
The VA Enterprise Architecture Repository (VEAR) is one component within the overall EA that establishes the common framework for data taxonomy for describing the data architecture used to develop, operate, and maintain enterprise applications. The Contractor shall comply with the department’s Authoritative Data Source (ADS) requirement that VA systems, services, and processes throughout the enterprise shall access VA data solely through official VA ADSs where applicable, see below. The Information Classes which compose each ADS are located in the VEAR, in the Data & Information domain. The Contractor shall ensure that all delivered applications and system solutions support:
| 1. | Interfacing with VA’s Master Person Index (MPI) (formerly the Master Veteran Index (MVI)) to provision identity attributes, if the solution relies on VA user identities. MPI is the authoritative source for VA user identity data. |
| 2. | Interfacing with Capital Asset Inventory (CAI) to conduct real property record management actions, if the solution relies on real property records data. CAI is the authoritative source for VA real property record management data. |
| 3. | Interfacing with electronic Contract Management System (eCMS) for access to contract, contract line item, purchase requisition, offering vendor and vendor, and solicitation information above the micro-purchase threshold, if the solution relies on procurement data. ECMS is the authoritative source for VA procurement actions data. |
| 4. | Interfacing with HRSmart Human Resources Information System to conduct personnel action processing, on-boarding, benefits management, and compensation management, if the solution relies on personnel data. HRSmart is the authoritative source for VA personnel information data. |
| 5. | Interfacing with Vet360 to access personal contact information, if the solution relies on VA Veteran personal contact information data. Vet360 is the authoritative source for VA Veteran Personal Contact Data. |
| 6. | Interfacing with VA/Department of Defense (DoD) Identity Repository (VADIR) for determining eligibility for VA benefits under Title 38, if the solution relies on qualifying active duty military service data. VADIR is the authoritative source for Qualifying Active Duty military service in VA. |
5.1.4 SOCIAL SECURITY NUMBER (SSN) REDUCTION
The Contractor solution shall support the Social Security Number (SSN) Fraud Prevention Act (FPA) of 2017 which prohibits the inclusion of SSNs on any document sent by mail. The Contractor support shall also be performed in accordance with Section 240 of the Consolidated Appropriations Act (CAA) 2018, enacted March 23, 2018, which mandates VA to discontinue using SSNs to identify individuals in all VA information systems as the Primary Identifier. The Contractor shall ensure that any new IT solution discontinues the use of SSN as the Primary Identifier to replace the SSN with the ICN in all VA information systems for all individuals. The Contractor shall ensure that all Contractor delivered applications and systems integrate with the VA Master Person Index (MPI) for identity traits to include the use of the ICN as the Primary Identifier. The Contractor solution may only use a Social Security Number to identify an individual in an information system if and only if the use of such number is required to obtain information VA requires from an information system that is not under the jurisdiction of VA.
5.2 INFORMATION SECURITY CONSIDERATIONS:
The Assessment and Authorization (A&A) requirements do not apply and a Security Accreditation Package is not required.
5.3 POINTS OF CONTACT
VA Program Manager: Provided at Award.
Name:
Voice:
Email:
Contracting Officer’s Representative: Provide at Award
Name:
Voice:
Email:
Contracting Officer:
| Name: | Kendra Casebolt |
| Voice: | 848-377-5042 |
Email: Kendra.Casebolt@va.gov
Contract Specialist:
| Name: | Angel Santos |
| Voice: | 848-377-5096 |
| Email: | Angel.Santos@va.gov |
image1.jpeg
File details come from the government source that posted it. Updated .