Program-level artifacts, workflow and status for delivery of products within the cloud.gov umbrella

cloud.gov is a set of tools designed and supported by US government workers, for US government work. cloud.gov's mission is to reduce the barriers to rapid, incremental, compliant, secure, and scalable delivery of government services for all government agencies by leveraging best-of-breed modern practices in an opinionated way.

cloud.gov consists of:

• the cloud.gov Platform-as-a-Service (PaaS)
• "cloud.gov" commonly refers to the cloud.gov PaaS, which was cloud.gov's first product. The PaaS provides a comfortable abstraction which handles cloud-based operations and greatly reduces the complications of infrastructure management for delivery teams. Our PaaS builds on the widely-used and open source Cloud Foundry, deployed with practices geared toward meeting strict government compliance requirements.
• the Compliance Toolkit continuous assurance service
• Compliance Toolkit provides a heads-up view of code quality and security suitable for integration into a delivery team's CI/CD system. Compliance Toolkit helps teams develop to a high standard, enter the compliance process with confidence, and demonstrate continued high quality/compliance long after they have Authority to Operate, as new requirements and vulnerabilities emerge. Compliance Toolkit includes Compliance Masonry, which transforms compliance documentation from static text to composable, testable code. Compliance Toolkit can be used with or without the cloud.gov PaaS, but is easier to take advantage of for apps being deployed there.

For now, this is in another tool only accessible by 18F personnel. Soon we will embed the information directly here.

We are using ZenHub to provide a top-level kanban board and burndown charts showing the status of related work happening across many repositories in GitHub. Install it, then click "Boards" above to see it.

We document the processes that govern the delivery of our work, which is shared (and potentially embellished) by various teams/sub-projects in other repositories. Our process is revised periodically when we reflect on common patterns observed across retrospectives.

To include artifacts from another repository in our program-level view, use ZenHub to set up a board that resembles the program board. Then merge that board into the program board, mapping similar columns appropriately.