Release Management Process
CrowdComms has updated the design, development and change management process. The scope of this process is adding new features based on the requirements of clients and internal business objectives to improve the CrowdComms platform.
Releasing the product is the final stage and in summary
- All new features follow a design & development process that includes stakeholder feedback on the concept and execution of the UX design, rigorous testing, peer review of code and security review before being planned for release. Progress is managed throughout by the product delivery manager.
- During preparation for release, CrowdComms production staff will be trained to support our clients. All customer facing communications and internal training documents will be reviewed as part of the release testing.
- The release committee will conduct an impact assessment of the proposed changes and highlight any areas of concern or gaps in documentation.
- Once testing and documentation has been completed, the release committee will authorise the release. The new updates will be prepared for release, including scheduling release times to minimise any disruption.
The improvement to the process includes-
- We aim to communicate details of the release approx. two weeks in advance. An email detailing the changes will be sent to admins who have access to the CrowdComms dashboard (CMS).
- A final reminder email will then be sent two days before the scheduled release date.
- Between the two update emails, there will be the opportunity for clients to discuss the changes with account managers and support managers to ensure they understand the new functionality and any potential change to user experience.
Please note, critical updates to ensure smooth operation of the CrowdComms platform will not always follow the above steps.
The above process is followed for any new feature additions or any planned ‘breaking change’ where the user experience on the platform would be modified in any meaningful way.