<aside> ๐Ÿ’ก This template is designed as a standalone document for individual projects. It is a living document, and new ideas and old ideas here should be evaluated iteratively.

</aside>

Table of Contents

1. Preface and Goals

Preface

<aside> ๐Ÿš‚ The release train doesnโ€™t wait for anyone. On a biweekly schedule, there will be new features, tests, and deployments that will work together in unison. If you are not able to catch this deployment train, you better catch the next one!

</aside>

Goals

<aside> ๐Ÿ›— The purpose and goals of this document are to write down how DxGov handles its releases going forward. This document will provide a coordinated effort between the development team, QA team, product manager, and our stakeholders.

</aside>

<aside> โœ… โ€œA successful release cycle means a fast build-to-deployment time with no unexpected bugsโ€

</aside>

The following cycle represents an agile release management cycle, and we are going to proceed from the eight stages presented below:

  1. Bugs and Features

  2. Planning and Design

  3. Software Build

  4. Review

  5. Test

  6. Deployment

  7. Support

  8. Issue Reporting and collections

https://s3-us-west-2.amazonaws.com/secure.notion-static.com/1878d504-6fff-4e20-b450-8ad96ddcfa01/Untitled.png

Team

<aside> ๐Ÿ‘ฅ The DxGov Team

</aside>

Name Role
Kenny Developer
Madusha Developer
Milton Developer
Dino Developer
Augusto Developer/Developer Manager
Ross Product Manager
Tomas Developer
Philip QA

Release Cycle Overview