Sprout’s Automated Release Process

by | Mar 4, 2019 | 0 comments

Our customers are important to us, so we believe offering them a way to actively participate in the production of their software project is essential. Whether we’re building a web app or a mobile app, replacing an existing app or building something brand new—we want our customers to remain involved from beginning to end. We have a passion for collaborating and building positive relationships with each customer that promise to form strong foundations for each of their individual projects. Every customer comes to us with a vision, and we want to make sure we’re always delivering on that vision.

Sprout offers an avenue that allows our customers to be involved in the production process every step of the way. Each time our developers make changes or improvements on a project at the close of a sprint, customers receive an alert notifying them that they have updates in need of review. Customers can then sign in to Sprout, where they have the option to test these updates in a beta testing environment. During the testing process, several tools are available for customers to utilize.



The first option Sprout offers to customers is the option to “Start a Discussion.” We encourage customers to utilize this feature anytime they have new ideas for their project that they are eager to bounce around with our team, or questions to which they are seeking prompt answers. Our team responds quickly to all customer inquiries. No matter the situation, we are dedicated to maintaining an open dialogue with our customers to support their every need.  



Another option Sprout offers to customers, and perhaps one of the most critical during the development stage, is the option to “Report a Problem.” This is also referred to as submitting tickets via Sprout. Customers should submit tickets anytime they detect a bug or defect during the testing process in beta. Our developers receive a notification to review and fix the issues each time a customer submits a ticket. Once the issues are resolved during the next sprint, customers are again alerted to review and test the updates. This cycle continues until customers feel satisfied with the work our developers have done, and they are ready to approve it for release to the production site.



The third option Sprout offers to customers is the option to “Approve for Release.” This option should be selected only after the work product has been tested in beta and the customer determines that it is ready to launch in a production environment. During the final testing phase, customers have the option to assign additional parties to test the work product. Each party listed must test the work product and approve it for release. Once all of the required parties have given their approval, the work product is published to the production environment.


Publishing can create downtime for applications, lasting anywhere from five to thirty minutes, so the product is typically published between 8:00pm-10:00pm on Sunday through Thursday. However, Sprout gives customers the option to publish the product immediately following approval from each required party, if they so choose. Due to the potential downtime that publishing may cause, however, customers may find it beneficial to wait for Sprout to automatically publish the release itself, within the set time frame. Once the work product has been approved and released it becomes available to users.



Our customers come to us because they have a vision, and they trust that we have the tools and expertise to develop the software to meet their needs. Sprout’s automated release process is one of the tools in which we take the most pride. It’s purpose is to provide our customers with a sense of ease and security in knowing that, when their project launches, it promises to be a seamless experience for everyone involved. If you have a vision that you’re ready to make a reality, we’re here to help. Let’s create something together!


Submit a Comment

News Categories