Digital Services Playbook - TeraLogics/TotalBriecall GitHub Wiki
| Digital Service Plays | Evidence | |
|---|---|---|
| 1 | Understand what people need | The delivery team spends time directly with end users to understand their needs and how they intend to use the application. The team interaction is primarily through iterative user interviews, design reviews and hands-on usability testing. Requirements and user feedback translate to user stories or requirements that are prioritized for sprint execution. [User Feedback Group] (https://github.com/TeraLogics/TotalBriecall/wiki/user-feedback-group) [Human Centered Design] (https://github.com/TeraLogics/TotalBriecall/wiki/human-centered-design) [Usability Testing] (https://github.com/TeraLogics/TotalBriecall/wiki/usability-testing) [Responsive Design] (https://github.com/TeraLogics/TotalBriecall/wiki/Responsive-Design) |
| 2 | Address the whole experience, from start to finish | Our design approach takes into account the multiple ways in which users interact with the application, whether it's through a desktop browser or on their mobile device. We work with end users throughout the agile development lifecycle to ensure we solve for their primary pain points and enhance their overall experience. [Usability Testing] (https://github.com/TeraLogics/TotalBriecall/wiki/usability-testing) [Front End Design Evoluton] (https://github.com/TeraLogics/TotalBriecall/wiki/Front-End-Design-Evolution) |
| 3 | Make it simple and intuitive | Throughout the agile development process, our goal is always to make applications simple, intuitive, and easy to use. Our approach for the prototype was to develop a design style guide that was flexible enough to meet end user needs and present information in a clear and meaningful way. [Design Style Guide] (https://github.com/TeraLogics/TotalBriecall/wiki/style-guide) |
| 4 | Build the service using agile and iterative practices | Our small development team built the prototype application following an iterative two-day sprint cycle approach. Each cycle focused on planning, designing, developing, testing, and deploying a solution based on prioritized backlog of user requirements. We elicited user feedback throughout the first cycle to drive the priorities for the second cycle. [Development and Design Process] (https://github.com/TeraLogics/TotalBriecall/wiki/Development-and-Design-Process) [Continuous Integration] (https://github.com/TeraLogics/TotalBriecall/wiki/Continuous-Integration) [Continuous Monitoring] (https://github.com/TeraLogics/TotalBriecall/wiki/Continuous-Monitoring) Front End Design Evolution Back End Design Evolution |
| 5 | Structure budgets and contracts to support delivery | Although this play was not required for the 18F ADS I RFQ response, our team has significant experience with scheduling, budgeting, and execution for agile development projects/contracts. Our team works with various government and private-sector contracting offices to ensure agile deliverables are focused, innovative, and impactful, while minimizing cost and schedule risks. |
| 6 | Assign one leader and hold that person accountable | Our team assigned the Product Manager as the primary Product Owner who is accountable for the delivery of the prototype application. Our Product Owner worked with end users to set the appropriate goals, tasks, and assignments for the sprints. The Product Owner advised the development team on technical solutions as needed to ensure that the final solution aligned with end user needs. [Agile Delivery Team] (https://github.com/TeraLogics/TotalBriecall/wiki/Agile-Delivery-Team) |
| 7 | Bring in experienced teams | Our team combines skills and experience across various software-development and delivery platforms to build high-impact and robust solutions. We bring tools and processes refined through years of experience designing, developing, and deploying web applications for critical mission systems. Our expertise was put into action as part of the working prototype delivered for the 18F ADS I RFQ response. [Agile Delivery Team] (https://github.com/TeraLogics/TotalBriecall/wiki/Agile-Delivery-Team) [Tools] (https://github.com/TeraLogics/TotalBriecall/wiki/Tools) [Develop and Design Process] (https://github.com/TeraLogics/TotalBriecall/wiki/Development-and-Design-Process) [Continuous Integration] (https://github.com/TeraLogics/TotalBriecall/wiki/Continuous-Integration) [Continuous Monitoring] (https://github.com/TeraLogics/TotalBriecall/wiki/Continuous-Monitoring) |
| 8 | Choose a modern technology stack | The team used various modern, open-source technologies for building out the prototype. Information on which technologies we used in each layer are included in the following wiki links. [Front End Technologies] (https://github.com/TeraLogics/TotalBriecall/wiki/frontend-technologies) [Back End Techologies] (https://github.com/TeraLogics/TotalBriecall/wiki/Backend-Technologies) |
| 9 | Deploy in a flexible hosting environment | Our team is experienced in multiple IaaS and PaaS solutions, and selected Heroku for our RFQ response. Our application can easily scale up for production by simply deploying additional front and backend instances on the PaaS. Platform as a Service |
| 10 | Automate testing and deployments | Our team uses best-of-breed tools to automate testing and continuously deploy to development and production servers throughout the sprint cycles. We deploy our code to production quickly and prevent errors through robust automated testing and thorough code coverage. [Continuous Integration] (https://github.com/TeraLogics/TotalBriecall/wiki/Continuous-Integration) [Continuous Monitoring] (https://github.com/TeraLogics/TotalBriecall/wiki/Continuous-Monitoring) |
| 11 | Manage security and privacy through reusable processes | Although security and privacy requirements are not explicitly called out in the 18F ADS I RFQ response, we have applied best practices to our solution. We use SSL encryption between client and server and store user information in a secure database. |
| 12 | Use data to drive decisions | Our application uses several different monitoring technologies to monitor system uptime, throughput, response time, and memory utilization. These tools ensure we are aware of how well the application is running and whether there are issues impacting our users. [Continuous Monitoring] (https://github.com/TeraLogics/TotalBriecall/wiki/Continuous-Monitoring) |
| 13 | Default to open | The prototype application and associated source code are available through our public Github repository under the MIT license. This repository contains a detailed overview of our Agile development processes, including this document. Documentation for our API is available on the deployment itself at /docs/api. [Open Source Repository] (https://github.com/TeraLogics/TotalBriecall) API Documentation [Agile Tools] (https://github.com/TeraLogics/TotalBriecall/wiki/Tools) |