SOW Attachment A9 - EHBs Quality Metrics.pdf
PDF 120 KB Posted
- Attached to
- Electronic Handbooks Development, Modernization, and Enhancements Federal contract opportunity
- Solicitation number
- 75R60221R00007
About this file
This attachment to a federal contract opportunity outlines quality metrics and standards for Electronic Health Benefits development projects. The contractor will be required to track metrics in several quality areas including requirements quality, meeting quality, user acceptance testing quality, release quality, and post-release evaluation. Metrics include the number of missed requirements, late deliverables, quality issues found during testing, security vulnerabilities identified, defects during releases and post-release, and customer impact from defects. The related federal contract opportunity is a solicitation from the Health Resources and Services Administration for an Indefinite Delivery/Indefinite Quantity contract to provide development, maintenance, and enhancement support for Electronic Health Benefits and integration with other HHS systems. The support includes systems architecture and program management office services.
View the file
Other files for this federal contract opportunity
Show all 50
Electronic Handbooks Development, Modernization, and Enhancements has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
EHBs Quality Metrics and Standards Attachment 9
Providing Quality services in product releases to customers are top most priority for HRSA. Below table shows the various metrics need to be tracked and reported as part of each release to assess the quality of contractors. There may additional metrics be added to the task orders.
Quality Area(s) Metrics/Delivery Standards Requirement quality /Standards
- # of times traceability to track the requirements got missed
- # of times the requirement sign off from IT leads and Business lead on time did not occur
- # of times requirement for Technical/functional Solutions were met (Functionality , Scalability, Reliability, Generic loosely coupled architecture )
Meeting Quality / Standards - # of times delivery of presentation slide and one pagers for stakeholders to review 3 business days prior to the meeting missed
- # of times the right work groups /Participants not attended to capture the requirements
- # of times the requirements are not captured as planned or missed the requirements
- # of times meeting minutes on time and not on time
- # of un-unplanned meeting conducted and cost implications
UAT Quality/ Standards - # of quality issues found in Data for UAT
- # of hours spent for setting up the data and gain feedback
- # of Issues found during UAT
- # of automated scripts for generating test data
Release Quality/Standards - # of critical , high and medium security vulnerabilities identified for the release
- # of Code Sync happened after the deadline is elapsed
- #of issues identified during Integration and QA testing at HRSA
- # of Known issues for the release
- # of Open defect during the release day
- # of slow running ETLs process if any
- # of pages not meeting the specified page load time ( 3 second target)
- # of read-only pages not using the read workload DB platform
- # of 400 errors and 500 Errors in application during the release
- % of automated unit coverage implemented
- % of open code quality issues (Technical Debt, code smells, etc...)
- # of Performance issues identified for the release
- # of backlogs due to change in requirement introduced the
- % of Technical Debt and reduction of those release by release
Post release evaluation/ Standards
- # of 45 days warranty tickets created
- # of operations tickets generated due to defect(s) introduced due to release
- # of customers impacted with the defect , if any
- # of hours lost by stakeholders/customers due to system defects, if any
- # of hours O&M spent in trouble shooting the defects
File details come from the government source that posted it. Updated .