Improvements to the Enable software are made to address both the immediate and longer-term needs of our customers. We have a product roadmap that outlines large initiatives with timelines measured in years, but we also work continually in response to customer input. For example, information from the Feedback backlog in Cello is compiled and categorized to help identify product improvements that have potential to benefit a large number of customers or to meet the most pressing needs.
Generally speaking, changes to the product are prioritized and planned by our Product Management team. They investigate possible changes and write detailed specification documents that the Engineering team then uses to estimate the amount of time that would be required to make particular changes to the software. Work is prioritized, estimated and planned in six-week-long cycles called build slots, and each calendar year is comprised of eight build slots and a four-week interim period from mid-December to mid-January.
The development work chosen by Product Management for each build slot is divided by Engineering into batches according to what part of the system will be affected, and each batch will be handled by one of the Engineering sub-teams. As the work is being done, the Customer Success team will use information from the Product Management and Engineering teams to assemble a product update newsletter for the customers.
At the end of each build slot, meetings are held at which representatives from the Engineering sub-teams discuss with Product Management and Customer Success the work that was completed. The updates are deployed to the User Acceptance Testing channels, and customers on the mailing list receive a notice that the newsletter article is available to review and that the updates are ready for testing. The specific release dates related to upcoming build slots are kept current in a separate article.
After approximately five weeks of testing in UAT, the batch of updates will deploy to the live channels. Customers are alerted of the deployment via email both to warn them of possible disruption to the system during the deployment and to remind them to anticipate the changes. By this time, the Customer Success team will usually have already produced new articles and videos for the Help Center and will be reaching out to customers to plan demos and training about the new features and functionality.
If you have questions about new features or product updates, or if you have email addresses to add to the updates mailing list, please reach out to one of your Customer Success representatives or raise a ticket on Cello.