Common use of Development of Minimally Viable Product Clause in Contracts

Development of Minimally Viable Product. Using agile software development methods, the contractor shall develop and release to end users a minimally viable product by completing the following tasks: 1. Utilize an agile development method to write and manage epics, user stories, and acceptance criteria. 2. Conduct iteration retrospectives, release planning, backlog grooming, and other common activities associated with iterative design and agile methodologies. 3. Implement best practice methods for automated testing and code reviews. 4. Work with the agency to develop or manage continuous integration, code management processes, security, 508 compliance, privacy or any other agency policies that need to be incorporated to release the product in a live environment. 5. Test solution with end users and conduct user research activities. 6. Create and track metrics to determine whether the delivered solution meets end users’ needs and solves agency problem statement to some degree. 7. As a result of the feedback provide recommendations on what should be modified in future versions of the product. The successful solution, at a minimum, shall also include the following best practices as highlighted in the digital service playbook. The contractor shall address the different ways people will interact with USCIS services; including the actions they take online, through a mobile application, on a phone, or in person. Every encounter—whether it is online or offline— should move the user closer towards their goal. In delivery of this effort the contractor shall: 1. Understand the different points at which people will interact with the service—both online and in person. 2. Identify pain points in the current way users interact with the service and prioritize these according to user needs. 3. Design the digital parts of the service so that they are integrated with the offline touch points people use to interact with the service. 4. Develop metrics that will measure how well the service is meeting user needs at each step of the service. Successful delivery of this contract requires that the services of and products delivered will not be stressful, confusing, or daunting. Therefore, the contractor shall build and release a digital MVP that is simple and intuitive enough that users succeed the first time, unaided. In delivery of this effort the contractor shall: 1. Use a simple and flexible design style guide for the service. 2. Use the U.S. Web Design Standards as a default. 3. Use the design style guide consistently for related digital services. 4. Give users clear information about where they are in each step of the process. 5. Follow accessibility best practices to ensure all people can use the service. 6. Provide users with a way to exit and return later to complete the process. 7. Use language that is familiar to the user and easy to understand. 8. Use language and design consistently throughout the service, including online and offline touch points. At every stage of a project, the contractor shall measure how well the services are working for end-users. This includes measuring how well a system performs and how people are interacting with it in real-time. These metrics shall be reported to the Program Managers to find issues and identify which bug fixes and improvements should be prioritized. Along with monitoring tools, a feedback mechanism should be in place for people to report issues directly. In delivery of this effort the contractor shall: 1. Monitor system-level resource utilization in real time. 2. Monitor system performance in real-time (e.g. response time, latency, throughput, and error rates). 3. Track concurrent users in real-time and monitor user behaviors in the aggregate to determine how well the service meets user needs. 4. Provide metrics which may be published internally. 5. Provide metrics which may be published externally. 6. Use an experimentation tool that supports multivariate testing in production. Following the development and release of the MVP, the government and contractor team comes together to understand from a project viewpoint to identify improvement actions. In delivery of this effort the contractor shall complete the following tasks: 1. Conduct a project retrospective activity that analyzes data gathered during performance around goals, timeline, budget, major events, and success or failures. 2. Determine what roadblocks were mitigated and which ones still exist that need to be addressed. 3. Provide or update the Product Roadmap for scaling the MVP through continuous design and agile processes. 4. Ensure all system documentation, user stories, acceptance criteria and test scripts are finalized.

Appears in 2 contracts

Sources: Contract, Contract