U.S. Digital Services PlaybookThe American people expect to interact with government through digital channels such as websites, email, and mobile applications. By building better digital services that meet the needs of the people that use our services, we can make the delivery of our policy and programs more effective.Today, too many of our digital services projects do not work well, are delivered late, or are over budget. To increase the success rate of these projects, the U.S. Government needs a new approach. We created a playbook of 13 key “plays” drawn from successful best practices from the private sector and government that, if followed together, will help government build effective digital services.U.S. CIO CouncilCIOC_6e3ed4bc-439d-11e4-a6a7-d9492e61dbbf_6e3ed7d2-439d-11e4-a6a7-d9492e61dbbfTo help government build effective digital services_6e3edb38-439d-11e4-a6a7-d9492e61dbbfNeedsUnderstand what people need_6e3edc50-439d-11e4-a6a7-d9492e61dbbfPlay 1We must begin digital projects by exploring and pinpointing the needs of the people who will use the service, and the ways in which the service will fit into their lives. Whether the users are members of the public or government employees, policy makers must include real people in their design process from the very beginning. The needs of people -- not constraints of government structures or silos -- should drive technical and design decisions. We need to continually test the products we build with real people to keep us honest about what is important... key questions: What user needs will this service address? Why does the user want or need this service? Who are your key users? Which people will have the most difficulty with your service? What research methods were used? What were the key findings from users’ current experience? How were the findings documented? Where can future team members access the documentation? How often are you testing with real people?ConsultationEarly in the project, spend time with current and prospective users of the service_6e3edd22-439d-11e4-a6a7-d9492e61dbbf1.1User ResearchUse a range of qualitative and quantitative user research methods to determine people’s goals, needs, and behaviors_6e3eddf4-439d-11e4-a6a7-d9492e61dbbf1.2be thoughtful about the time spentPrototypesTest prototypes of possible solutions with real people, in the field if possible_6e3edec6-439d-11e4-a6a7-d9492e61dbbf1.3DocumentationDocument the findings about user goals, needs, behaviors, and preferences_6e3edfa2-439d-11e4-a6a7-d9492e61dbbf1.4FindingsShare findings with the team and agency leadership_6e3ee074-439d-11e4-a6a7-d9492e61dbbf1.5Goals & PrioritiesCreate a prioritized list of user stories, which are short descriptions of the goals the user is trying to accomplish_6e3ee146-439d-11e4-a6a7-d9492e61dbbf1.6TestingAs the digital service is being built, regularly test it with potential users to ensure it will meet peoples’ needs_6e3ee218-439d-11e4-a6a7-d9492e61dbbf1.7Whole ExperienceAddress the whole experience, from start to finish_6e3ee2f4-439d-11e4-a6a7-d9492e61dbbfPlay 2We must build digital services with an understanding of the range of ways a person might interact with our service, including the actions they take online, through a mobile application, on the phone, or in person. Every encounter should move the user closer towards the desired outcome, whether that encounter is online or offline... key questions: What are the different ways (both online and offline) that people currently accomplish the task the digital service is designed to help with? Where are user pain points in the current way people accomplish the task? Where does this specific project fit into the larger way people currently obtain the service being offered? What metrics will best indicate how well the service is working for its users?Interaction PointsUnderstand the different points at which people will interact with the service – both online and in person_6e3ee3d0-439d-11e4-a6a7-d9492e61dbbf2.1Pain PointsIdentify pain points in the current way users interact with the service, and prioritize these according to user needs_6e3ee4ac-439d-11e4-a6a7-d9492e61dbbf2.2Digital ServicesDesign the digital parts of the service so that they are integrated with the offline touch points people use to interact with the service_6e3ee57e-439d-11e4-a6a7-d9492e61dbbf2.3MetricsDevelop metrics that will measure how well the service is meeting user needs, at each step of the service_6e3ee65a-439d-11e4-a6a7-d9492e61dbbf2.4Simplicity & IntuitivenessMake it simple and intuitive_6e3ee72c-439d-11e4-a6a7-d9492e61dbbfPlay 3Using a government service shouldn’t be stressful, confusing, or daunting -- it’s our job to build services that are simple and intuitive enough that users succeed the first time, unaided... key questions: What primary tasks are the user trying to accomplish? What is the reading level of the language the service uses? What languages is your service offered in? If a user needs help while using the service how do they go about getting it? How does the service’s design visually relate to other government services?Style GuideCreate or use an existing, simple, and flexible design style guide for the service_6e3ee812-439d-11e4-a6a7-d9492e61dbbf3.1Cross-Service StyleUse the design style guide across related digital services_6e3ee90c-439d-11e4-a6a7-d9492e61dbbf3.2User Process InformationProvide users with clear information about where they are in the process as they use the service_6e3eea74-439d-11e4-a6a7-d9492e61dbbf3.3AccessibilityFollow accessibility best practices to ensure all people can use the service_6e3eeb64-439d-11e4-a6a7-d9492e61dbbf3.4Exit & ReturnProvide users with a way to exit and return later to complete the process_6e3eec4a-439d-11e4-a6a7-d9492e61dbbf3.5Plain LanguageUse language that is familiar to the user and is easy to understand_6e3eed30-439d-11e4-a6a7-d9492e61dbbf3.6ConsistencyUse language and design consistently throughout the service, including in the online and offline (non-digital) touch points people use to interact with the service_6e3eee20-439d-11e4-a6a7-d9492e61dbbf3.7Agility & IterationBuild the service using agile and iterative practices_6e3eef1a-439d-11e4-a6a7-d9492e61dbbfPlay 4We should use an incremental, fast-paced style of software development to reduce the risk of failure by getting working software into users’ hands quickly, and by providing frequent opportunities for the delivery team members to adjust requirements and development plans based on watching people use prototypes and real software. A critical capability is being able to automatically test and deploy the service so that new features can be added often and easily put into production. Following agile methodologies is a proven best practice for building digital services, and will increase our ability to build services that effectively meet user needs... key questions: How long did it take to ship the MVP? If it has not shipped yet, when will it? How long does it take for a production deployment? How long in days are the iterations/sprints? Which source code version control system is being used? What tool is being used to track bugs and issue tickets? What tool is being used to manage the feature backlog? How often do you review and reprioritize the items in your feature and bug backlog? How do you collect user feedback during development and how is that feedback to improve the service? At each stage of usability testing, what gaps were identified in addressing user needs?Minimum Viable ProductShip a functioning “minimum viable product” (MVP) that solves a core user need addressed by the service as soon as possible, and not longer than three months from the beginning of any new digital project, using a “beta” or “test” period if needed_6e3ef01e-439d-11e4-a6a7-d9492e61dbbf4.1Usability TestingRun usability tests frequently to see how well the service works for users, and identify improvements that should be made_6e3ef154-439d-11e4-a6a7-d9492e61dbbf4.2CommunicationEnsure the individuals building the service are in close communication using techniques such as war rooms, daily standups, and team chat tools_6e3ef244-439d-11e4-a6a7-d9492e61dbbf4.3Delivery TeamsKeep delivery teams small and focused_6e3ef334-439d-11e4-a6a7-d9492e61dbbf4.4limit organizational layers that separate these teams from the business ownersReleasesRelease features and improvements multiple times each month_6e3ef532-439d-11e4-a6a7-d9492e61dbbf4.5Features & BugsCreate a prioritized list of features and bugs, also known as the “feature backlog” and “bug backlog”_6e3ef62c-439d-11e4-a6a7-d9492e61dbbf4.6Issue TrackingUse an “issue tracker” to catalog features and bugs_6e3ef71c-439d-11e4-a6a7-d9492e61dbbf4.7Version ControlUse a source code version control system_6e3ef83e-439d-11e4-a6a7-d9492e61dbbf4.8Team AccessEnsure entire team has access to the issue tracker and version control system_6e3ef9a6-439d-11e4-a6a7-d9492e61dbbf4.9Code ReviewsUse code reviews to ensure quality_6e3efaaa-439d-11e4-a6a7-d9492e61dbbf4.10Budgets & ContractsStructure budgets and contracts to support delivery_6e3efbb8-439d-11e4-a6a7-d9492e61dbbfPlay 5To improve our chances of success when contracting out development work, we need to work with experienced budgeting and contracting officers. In cases where we use third parties to help build a service, a well-defined contract can facilitate good development practices like conducting a research and prototyping phase, refining product requirements as the service is built, evaluating open source alternatives, ensuring frequent delivery milestones, and allowing the flexibility to purchase cloud computing resources. The TechFAR Handbook provides a detailed explanation of the flexibilities in the Federal Acquisition Regulation (FAR) that can help agencies implement this play... key questions: How frequent are the delivery milestones? What are the performance metrics defined in the contract? (i.e., response time, system uptime, time period to address priority issues, etc.)BudgetBudget includes research, discovery, and prototyping activities_6e3efcb2-439d-11e4-a6a7-d9492e61dbbf5.1DeliverablesContract is structured to request frequent deliverables and not multi-month milestones_6e3efdac-439d-11e4-a6a7-d9492e61dbbf5.2AccountabilityContract is structured to hold vendors accountable to deliverables_6e3efec4-439d-11e4-a6a7-d9492e61dbbf5.3FlexibilityContract allows the government delivery team the flexibility to adjust feature prioritization as the project evolves_6e3effe6-439d-11e4-a6a7-d9492e61dbbf5.4Open Source & COTSContract ensures open source solutions are evaluated alongside commercial solutions when technology choices are made_6e3f00e0-439d-11e4-a6a7-d9492e61dbbf5.5Public DomainContract specifies that software and data generated by third parties remains under our control, and can be reused and released to the public as appropriate and in accordance with the law_6e3f0202-439d-11e4-a6a7-d9492e61dbbf5.6Tools, Services & HostingContract allows us to use tools, services, and hosting from vendors with a variety of pricing models, including fixed fees and variable service-based models like “pay-for-what-you-use” services_6e3f0324-439d-11e4-a6a7-d9492e61dbbf5.7WarrantiesContract specifies a warranty period where defects uncovered by the public are addressed by the vendor(s) at no additional cost to the government_6e3f0432-439d-11e4-a6a7-d9492e61dbbf5.8TransitioningContract includes a transition of services period and transition-out plan_6e3f0554-439d-11e4-a6a7-d9492e61dbbf5.9Leadership & AccountabilityAssign one leader and hold that person accountable_6e3f0662-439d-11e4-a6a7-d9492e61dbbfPlay 6There must be a single product owner who has the authority and responsibility across teams to assign tasks and work elements; make business, product, and technical decisions; and is accountable for the success or failure of the overall service. This product owner is ultimately responsible for how well the service is meeting the needs of its users, which is how a service should be evaluated. The product owner is responsible for ensuring the features are built and managing the feature and bug backlogs... key questions: Who is the product owner? What organizational changes have been made to ensure the product owner has sufficient authority over and support for the project? What does it take for the product owner to add or remove a feature from the service?Product OwnerA product owner has been identified_6e3f0770-439d-11e4-a6a7-d9492e61dbbf6.1Product OwnerStakeholder AgreementAll stakeholders agree that the product owner has the authority to assign tasks and make decisions about features and technical implementation details_6e3f089c-439d-11e4-a6a7-d9492e61dbbf6.2Background & ExpertiseThe product owner has a product management background with technical experience to assess alternatives and weigh tradeoffs_6e3f09d2-439d-11e4-a6a7-d9492e61dbbf6.3Product OwnerWork PlanThe product owner has a work plan that includes budget estimates and identification of funding sources_6e3f0b76-439d-11e4-a6a7-d9492e61dbbf6.4Product OwnerRelationshipsThe product owner has a strong relationship with his or her contracting officer_6e3f0e3c-439d-11e4-a6a7-d9492e61dbbf6.5Product OwnerContracting OfficerExperienceBring in experienced teams_6e3f0f5e-439d-11e4-a6a7-d9492e61dbbfPlay 7Product ManagersProduct EngineersProduct DesignersWe need talented people working in government who have experience creating modern digital services. This includes bringing in seasoned product managers, engineers, and designers. When outside help is needed, our teams should work with contracting officers who understand how to evaluate third-party technical competency so our teams can be paired with contractors who are good at both building and delivering effective digital services. The makeup and experience requirements of the team will vary depending on the scope of the project.ExperienceMember(s) of the team have experience building popular, high-traffic digital services_6e3f1076-439d-11e4-a6a7-d9492e61dbbf7.1Mobile & Web AppsMember(s) of the team have experience designing mobile and web applications_6e3f11d4-439d-11e4-a6a7-d9492e61dbbf7.2Automated TestingMember(s) of the team have experience using automated testing frameworks_6e3f12f6-439d-11e4-a6a7-d9492e61dbbf7.3Modern DevOpsMember(s) of the team have experience with modern development and operations (DevOps) techniques such as continuous integration and continuous deployment_6e3f1490-439d-11e4-a6a7-d9492e61dbbf7.4Service SecurityMember(s) of the team have experience securing digital services_6e3f1698-439d-11e4-a6a7-d9492e61dbbf7.5Contracting OfficerA Federal contracting officer is on the internal team if a third party will be used for development work_6e3f17ba-439d-11e4-a6a7-d9492e61dbbf7.6Contracting OfficerBudget OfficerA Federal budget officer is on the internal team or is a partner_6e3f18e6-439d-11e4-a6a7-d9492e61dbbf7.7Budget OfficerPrivacy, Civil Liberties & Legal AdvisorThe appropriate privacy, civil liberties, and/or legal advisor for the department or agency is a partner_6e3f1a30-439d-11e4-a6a7-d9492e61dbbf7.8Privacy AdvisorCivil Liberties AdvisorLegal AdvisorTechnology StackChoose a modern technology stack_6e3f1c2e-439d-11e4-a6a7-d9492e61dbbfPlay 8The technology decisions we make need to enable development teams to work efficiently and enable services to scale easily and cost-effectively. Our choices for hosting infrastructure, databases, software frameworks, programming languages and the rest of the technology stack should seek to avoid vendor lock-in and match what successful modern consumer and enterprise software companies would choose today. In particular, digital services teams should consider using open source, cloud based, and commodity solutions across the technology stack, as these solutions have seen widespread adoption and support by the most successful private-sector consumer and enterprise software technology companies... key questions: What is your development stack and why did you choose it? What database(s) are you using and why did you choose them? How long does it take for a new team member to set up a local development environment?Software FrameworksChoose software frameworks that are commonly used by private-sector companies creating similar services_6e3f1dbe-439d-11e4-a6a7-d9492e61dbbf8.1Software DeploymentTo the extent practical, ensure that software can be deployed on a variety of commodity hardware types_6e3f1f12-439d-11e4-a6a7-d9492e61dbbf8.2InstructionsEnsure that each project has easy to understand instructions for setting up a local development environment, and that team members can be quickly added or removed from projects_6e3f203e-439d-11e4-a6a7-d9492e61dbbf8.3Open Source SoftwareConsider open source software solutions at all layers of the stack_6e3f219c-439d-11e4-a6a7-d9492e61dbbf8.4Hosting EnvironmentDeploy in a flexible hosting environment_6e3f2318-439d-11e4-a6a7-d9492e61dbbfPlay 9Our services should be deployed on flexible infrastructure, where resources can be provisioned in real time to meet spikes in user demand. Our digital services are crippled when we host them in data centers which market themselves as “cloud hosting” but require us to manage and maintain hardware directly. This outdated practice wastes time, weakens our disaster recovery plans, and results in significantly higher costs... key questions Where is your service hosted? What hardware does your service use to run? What is the demand / usage pattern for your service? What happens to your service when it experiences a surge in traffic or load? How much capacity is available in your hosting environment? How long does it take you to provision a new resource such as an application server? How have you designed your service to scale based on demand? How are you paying for your hosting infrastructure — i.e., by the minute, hourly, daily, monthly, fixed? Is your service hosted in multiple regions / availability zones / data centers? In the event of a catastrophic disaster to a datacenter, how long will it take to have the service operational? What would be the impact of a prolonged downtime window? What data redundancy do you have built into the system, and what would be the impact of a catastrophic data loss? How often do you need to contact a person from your hosting provider to get resources or to fix an issue?ProvisioningResources are provisioned on demand_6e3f244e-439d-11e4-a6a7-d9492e61dbbf9.1ScalingResources scale based on real-time user demand_6e3f261a-439d-11e4-a6a7-d9492e61dbbf9.2APIsResources are provisioned through an API_6e3f2796-439d-11e4-a6a7-d9492e61dbbf9.3AvailabilityResources are available in multiple regions_6e3f28d6-439d-11e4-a6a7-d9492e61dbbf9.4UsageWe pay only for the resources we use_6e3f2a34-439d-11e4-a6a7-d9492e61dbbf9.5Static AssetsStatic assets are served through a content delivery network_6e3f2c50-439d-11e4-a6a7-d9492e61dbbf9.6HardwareApplication is hosted on commodity hardware_6e3f2e12-439d-11e4-a6a7-d9492e61dbbf9.7Testing & DeploymentAutomate testing and deployments_6e3f302e-439d-11e4-a6a7-d9492e61dbbfPlay 10Today, developers write automated scripts that can verify thousands of scenarios in minutes and then deploy updated code into production environments multiple times per day. They use automated performance tests which simulate surges in traffic to identify performance bottlenecks. While manual tests and quality assurance is still necessary, automated tests provide consistent and reliable protection against unintentional regressions, and make it possible for developers to confidently release frequent updates to the service... key questions: What percentage of the code base is covered by automated tests? How long does it take to build, test, and deploy a typical bug fix? How long does it take to build, test, and deploy a new feature into production? How frequently are builds created? What test tools are used? What deployment automation or continuous integration tools are used? What is the estimated maximum number of concurrent users who will want to use the system? How many simultaneous users could the system handle, according to the most recent capacity test? How does the service perform when you exceed the expected target usage volume? Does the service degrade gracefully or catastrophically? What is your scaling strategy when demand increases suddenly?User-Facing FunctionalityCreate automated tests that verify all user-facing functionality_6e3f31b4-439d-11e4-a6a7-d9492e61dbbf10.1Unit & Integration TestsCreate unit and integration tests to verify modules and components_6e3f338a-439d-11e4-a6a7-d9492e61dbbf10.2Test AutomationRun tests automatically as part of the build process_6e3f34d4-439d-11e4-a6a7-d9492e61dbbf10.3DeploymentsPerform deployments automatically with deployment scripts, continuous delivery services, or similar techniques_6e3f36a0-439d-11e4-a6a7-d9492e61dbbf10.4Load & Performance TestingConduct load and performance tests at regular intervals, including before public launch_6e3f37f4-439d-11e4-a6a7-d9492e61dbbf10.5Security & PrivacyManage security and privacy through reusable processes_6e3f393e-439d-11e4-a6a7-d9492e61dbbfPlay 11It is critical that our digital services protect sensitive information and keep systems secure. This is typically a process of continuous review and improvement which should be built into the development and maintenance of the service. At the start of designing a new service or feature, the team lead should engage the appropriate privacy, security, and legal officer(s) to discuss the type of information collected, how it should be secured, and how it may be used and shared. The sustained engagement of a privacy specialist helps ensure that personal data is properly managed. In addition, a key process to building a secure service is comprehensively testing and certifying the components in each layer of the technology stack for security vulnerabilities, and then to re-use these same pre-certified components for multiple services.The following checklist provides a starting point, but teams should work closely with their privacy specialist and security engineer to meet the needs of the specific service... PLAY 11 Manage security and privacy through reusable processesIt is critical that our digital services protect sensitive information and keep systems secure. This is typically a process of continuous review and improvement which should be built into the development and maintenance of the service. At the start of designing a new service or feature, the team lead should engage the appropriate privacy, security, and legal officer(s) to discuss the type of information collected, how it should be secured, and how it may be used and shared. The sustained engagement of a privacy specialist helps ensure that personal data is properly managed. In addition, a key process to building a secure service is comprehensively testing and certifying the components in each layer of the technology stack for security vulnerabilities, and then to re-use these same pre-certified components for multiple services.The following checklist provides a starting point, but teams should work closely with their privacy specialist and security engineer to meet the needs of the specific service... key questions: Does the service collect personal information from the user (whether government or public)? How is the user notified of this collection? Does it collect more information than is needed to perform the requested task? Are there uses of the data that would not be expected by the average user? How does a user contact a responsible person to seek access, correction, deletion, or removal of his or her personal information? Will information stored in the system be shared with others? How and how often is the service tested for security vulnerabilities? How can someone from the public report a security issue?SORN & PIAContact the appropriate privacy or legal officer of the department or agency to determine whether a System of Records Notice (SORN), Privacy Impact Assessment, or other review should be conducted_6e3f3ae2-439d-11e4-a6a7-d9492e61dbbf11.1Privacy OfficersLegal OfficersData Collection & PreservationDetermine, in consultation with a records officer, what data is collected and why, how it is used or shared, how it is stored and secured, and how long it is kept_6e3f3c40-439d-11e4-a6a7-d9492e61dbbf11.2Records OfficersPI NoticesDetermine, in consultation with a privacy specialist, whether and how users are notified about how personal information is collected and used, including whether a privacy policy is needed and where it should appear, and how users will be notified in the event of a security breach_6e3f3dbc-439d-11e4-a6a7-d9492e61dbbf11.3Privacy SpecialistsUser AccessConsider whether the user should be able to access, delete, or remove their information from the service_6e3f3f56-439d-11e4-a6a7-d9492e61dbbf11.4Hosting Infrastructure“Pre-certify” the hosting infrastructure used for the project using FedRAMP Use deployment scripts to ensure configuration of production environment remains consistent and controllable_6e3f40be-439d-11e4-a6a7-d9492e61dbbf11.5Data & DecisionsUse data to drive decisions_6e3f42c6-439d-11e4-a6a7-d9492e61dbbfPlay 12At all stages of a digital project, we should measure how well our service is working for our users. This includes measuring how well a system performs and how people are interacting with the system in real time. Our teams and agency leadership should carefully watch these metrics to proactively spot issues and identify which improvements should be prioritized. In addition to monitoring tools, a feedback mechanism should be in place for people to report issues directly... key questions: What are the key metrics for the service? How have these key metrics performed over the life of the service? What system monitoring tool(s) are in place? What is the targeted average response time for your service? What percent of requests take more than 1 second, 2 seconds, 4 seconds, and 8 seconds? What is the average response time and percentile breakdown (percent of requests taking more than 1s, 2s, 4s, and 8s) for your service’s top 10 transactions? What is your service’s monthly uptime target? What is your service’s monthly uptime percentage including scheduled maintenance? Excluding scheduled maintenance? How does your team receive automated alarms when incidents occur? What is the volume of each of your service’s top 10 transactions? What is the percentage of transactions started vs. completed? What tool(s) are in place to measure user behavior? What tool/technology is used for A/B testing? How do you measure customer satisfaction?UtilizationMonitor system-level resource utilization in real time_6e3f449c-439d-11e4-a6a7-d9492e61dbbf12.1System PerformanceMonitor system performance, measuring response time, latency, throughput, and error rates in real-time_6e3f462c-439d-11e4-a6a7-d9492e61dbbf12.2Performance MonitoringEnsure monitoring in place can measure median, 95th percentile and 98th percentile performance_6e3f47b2-439d-11e4-a6a7-d9492e61dbbf12.3AlertsCreate automated alerts based on this monitoring_6e3f4960-439d-11e4-a6a7-d9492e61dbbf12.4Concurrent Users & BehaviorsTrack concurrent users in real time, and monitor user behaviors (in the aggregate) to determine how well the service is meeting user needs_6e3f4ad2-439d-11e4-a6a7-d9492e61dbbf12.5Internal MetricsPublish metrics internally_6e3f4d16-439d-11e4-a6a7-d9492e61dbbf12.6External MetricsPublish metrics externally_6e3f4ec4-439d-11e4-a6a7-d9492e61dbbf12.7Multivariate TestingUse an experimentation tool that supports multivariate testing in production_6e3f5040-439d-11e4-a6a7-d9492e61dbbf12.8OpennessDefault to open_6e3f51bc-439d-11e4-a6a7-d9492e61dbbfPlay 13When we collaborate in the open and publish our data publicly we can improve Government together. By building services more openly and publishing open data, we simplify the public’s access to government services and information, allow the public to easily provide fixes and contributions, and enable reuse by entrepreneurs, nonprofits, other agencies, and the public... key questions: How are you collecting user feedback for bugs and issues? If there is an API, what capabilities does it provide? Who uses it? How is it documented? If the codebase has not been released under an open source license, explain why. What components are made available to the public as open source? What datasets are made available to the public?User FeedbackOffer users a mechanism to report bugs and issues, and be responsive to these reports_6e3f53f6-439d-11e4-a6a7-d9492e61dbbf13.1DatasetsProvide datasets to the public, in their entirety, through bulk downloads and APIs (application programming interfaces)_6e3f56c6-439d-11e4-a6a7-d9492e61dbbf13.2Public DomainEnsure that data from the service is explicitly in the public domain, and that rights are waived globally via an international public domain dedication, such as the “Creative Commons Zero” waiver_6e3f5838-439d-11e4-a6a7-d9492e61dbbf13.3Data CatalogCatalog data in the agency’s enterprise data inventory and add any public datasets to the agency’s public data listing_6e3f59f0-439d-11e4-a6a7-d9492e61dbbf13.4Data RightsEnsure that we maintain the rights to all data developed by third parties in such a manner that is releasable and reusable at no cost to the public_6e3f5b80-439d-11e4-a6a7-d9492e61dbbf13.5Software RightsEnsure that we maintain contractual rights to all custom software developed by third parties in such a manner that is publishable and reusable at no cost_6e3f5d1a-439d-11e4-a6a7-d9492e61dbbf13.6APIsWhen appropriate, create an API for third parties to interact with the service directly_6e3f5f22-439d-11e4-a6a7-d9492e61dbbf13.7Source CodeWhen appropriate, publish source code of projects or components online_6e3f61ca-439d-11e4-a6a7-d9492e61dbbf13.8PublicityWhen appropriate, share your development process and progress publicly_6e3f6364-439d-11e4-a6a7-d9492e61dbbf13.92014-09-23https://playbook.cio.gov/OwenAmburOwen.Ambur@verizon.net