Attachment_B_-_Draft_Proposed_Technical_Evaluation_-_Instructions_and_Criteria.pdf

Attachment B

PROPOSED TECHNICAL EVALUATION – INSTRUCTIONS & CRITERIA

TECHNICAL EVALUATION INSTRUCTIONS

Each Offeror will participate in a challenge exercise that will be completed in one business day and will evaluate the Offeror’s ability to perform the scope of support required on this contract vehicle. Each Offeror will be given the same challenge exercise.

The challenge will require Offerors to leverage Agile best practices to design and develop a Minimum Viable Product (MVP). At the end of the day, the Offeror will present a 60-minute demonstration of their MVP and the processes used in producing the MVP. The government will have the ability to have short status checks with the Offeror’s team throughout the day. The Offeror shall respond to questions posed by the government.

The government plans to provide Offerors with the details of the challenge once an Offeror arrives on their respective, assigned day to complete the exercise. On the day of the exercise, the government will provide the Offeror with a backlog board and access to users. The exercise will take place at a government location. The contractor shall bring their own equipment to use during the challenge exercise, including a mobile hotspot for Internet connectivity. A projector and screen will be available for the Offeror’s presentation. The Offeror shall bring a maximum of 12 individuals to perform as a team on the challenge exercise. The prime contractor shall be represented on the team. The intent of the challenge exercise is for this onsite team to complete the work of the challenge exercise.

Government evaluators will have the ability to observe the Offeror’s activities throughout the day of the challenge exercise and those observations will be considered in the government’s evaluation. Along with the presentation, the Offeror shall provide the government with access to the Offeror’s software code repository as well as other tool data and outputs related to creating the MVP.

Attachment B

TECHNICAL EVALUATION CRITERIA

There are three technical factors (Agile, Design, and Engineering) and each evaluation factor is of equal weight. Under each factor, there are elements that will be included in the government’s technical evaluation. Ratings will be given at the factor level.

Agile

For the type of Agile methodology applied by the Offeror, the degree to which the Offeror applies the chosen Agile methodology efficiently.

The degree to which the Offeror effectively uses artifacts in their Agile process.

The degree to which the Offeror fosters efficient communication in their team.

Design

The degree to which the Offeror effectively makes tradeoff decisions between user needs, business goals, and technical feasibility.

The degree to which the Offeror’s approach to learning about users is effective.

The degree to which the design yields an optimal user-experience.

Engineering

The degree to which the Offeror utilizes automated testing best practices and uses tests to improve the quality of the MVP.

The degree to which the Offeror’s code is high quality.

The degree to which the Minimum Viable Product is operational for use by users.

The degree to which the Continuous Integration/Continuous Deployment (CI/CD) pipeline is automated to provide continuous deployment.