It is MVP (Minimum Viable Product)
Go-Live Time
It is a day everyone is yearning for (Anuyat’s team,
clients, stakeholders, and investors) - it is a day when
the MVP goes up and live. Finally, an idea is right there
on everyone’s screen, all alive & happening.
A 90-day commitment to providing a quality minimum viable product is in its finishing phase.
What does MVP go-live
mean?
It means different things for each group involved during the MVP development process. Different processes come to life when the MVP is moved from the test environment to the production environment.
It is time to prepare all the technical platforms for
hosting the MVP, compile all the relevant documents to be
handed over, and arrange meetings with customers to
provide the walkthrough of the system.
For the team at Anuyat
It is time to be ready to implement the post-live strategies, evaluate the system on their environment, reach out to the support team in case of any concerns, and take a hand over of the system resources.
For the customers
It is time to prepare all the technical platforms for
hosting the MVP, compile all the relevant documents to be
handed over, and arrange meetings with customers to
provide the walkthrough of the system.
It is time to be ready to implement the post-live strategies, evaluate the system on their environment, reach out to the support team in case of any concerns, and take a hand over of the system resources.
Begin with Cloud setup
Most of our MVPs are cloud native. They use different services over the cloud, such as cloud databases, APIs, management tools, etc. This requires an application-specific cloud setup by configuring hardware and software every time an MVP goes live on the production.
The go-live squad sets up user permissions, tightens security, billing information, and network configurations.
The go-live squad sets up user permissions, tightens security, billing information, and network configurations.
Containerization
– building a platform-independent package
Read these stats:
- 72% enhancement in application’s security.
- 61% more effective to reduce the cost of
production downtime - 56% increase in application’s quality
Three major concerns and one solution–
containerization
Anuyat is among the leading organizations that use containerization power to package the software codes with all the required components, such as libraries, frameworks, and other dependencies. The isolated "container" encapsulates the application like a bubble and keeps it independent to be used between different infrastructures and operating systems.
For developers, it provides “build here, use
anywhere” kind of applications.
The basic stage is set, and the MVP is accessible. From here on, all the activities are focused on ensuring continuous functional checks for a perfectly working system.
Continuous integration –
pacing up with the changes
- Our customers can now get busy exploring the MVP in a live environment.
- Meanwhile, our team keeps a busy eye on the continuous integration needs of the MVP. With the change in technologies and business strategies, there is a demand for a constant watch out for any change in the data models, API calls, and business logic. Consequently, the changes are integrated with the live MVP.
- The team takes integration issues on priority level 1 (critical issues) and provides the solution in a reasonable time. However, just fixing the problem is not enough here; the team follows the trail and reaches the root cause of the failure.
- This analysis also unveils other functions which might have been affected due to this integration failure. Identifying them and fixing them is also the job responsibility of our go-live expert.
Continuous delivery & monitoring –
a watch party
- Post go-live, the continuous monitoring of functional bugs and changes that affect the system’s integration becomes a looped process: more changes, more integration testing, and thus, continuous delivery cycles.
- Each delivery cycle has logs maintained for all the changes that may affect integration. For instance, the addition or subtraction of a single field within the application must be mentioned into the log files. Also, log-in the changes it would have stirred into the system and how the team has handled them.
Backup and archival –
the power of two
- Crisis management needs every data point to initiate the recovery of the damaged system. For this purpose, backup and archival are used in combination.
- On the abstract level, both the techniques aim to store the historical data used in the production environment, to be retrieved during data loss due to system breach, disaster, infrastructure breach, etc.
Although both differ at the micro-level, each has
its power to exhibit.
Backup
- Backup protects both active & inactive data on the production
- Backup aids with large-scale recoveries
Archival
- whereas archives have only inactive data.
- while the archive is known to quickly access specific historical data such as a particular email address from the past.
There are more service-level instances where we
can find differences between the two. But we make
use of both as they are complementing each
other.
Fair words of caution
It is good to be positive with the successful go-live of the MVP. But expecting the unexpected is what wise people have always suggested.
Delays might be the case while implementing the system in the production environment, for unknown reasons. We suggest our clients have a backup plan ready to adjust their commitments in such an event of delay.
In conclusion,
a quick checklist of go-live an MVP, for our team.
List down all the resources needed to initiate and successfully implement the go-live.
Check if there is an older system that this new MVP will replace. If yes, take a week’s bracket to understand how to replace or merge these two systems, without affecting the data and processes at the customer’s workplace.
Set a timeline of tasks such as training, data integration, merging, etc.
Keep a rollback plan ready if something goes against the successful launch of the MVP in the production environment.
Share the SLA and other support documents with the customer to guide them on reaching the support team.
Check the availability of dependencies regarding technical resources, professionals, experts, and customers.
Make sure that the logs and reporting systems are in place. This comes in handy in case of rollbacks or understanding the root cause of an issue.
Time for your marketing team to buckle up and execute their strategies for introducing the newly delivered MVP in the target market.
Help
Case Studies
Useful Links
Contact Us
Anuyat © 2024. Powered by www.anuyat.com