Project Cycle: Launch
Development is complete and it's time to launch your software and let the first users try it out.
The MVP development is over. What now?
Now we’re going to launch the product from the development environment to the live server. Typically, this means that we will publish the website, app or system and make it available on the internet or app stores (Google Play or App Store).
What can you can expect
‘Launch to live’ is short, a few days long, but intensive and crucial period when several things happen gradually.
1. In-depth testing
The development environment has been running at our side so far. Now we will start a live server on your side. We’ll do in-depth testing in the test environment. At the same time, you test the application from a user perspective. Ideally, you will pass the application on to your prospective users.
2. Migration to live server
If testing doesn’t reveal any major problems, we will release the software to production. Of course, your project manager will walk you through everything and show you which server option your software needs. Depending on the expected traffic, the cost of a live server can range from tens to hundreds of dollars per year. When it comes to mobile apps, you don’t have to pay anything to publish them on Google Play or the App Store.
3. Retesting
After starting the project on the live server, we test again. It may happen that what worked on the development environment behaves differently in the live environment.
4. Backlog review
The next step is to review the product backlog. At this point, we should all know if you want to slow down further development for now or continue intensively. But it’s no later than this moment that we open the product backlog together, review which functionalities, UI adjustments or backend optimizations are left in the backlog, and prioritize them. And then we plan forward together.
5. Support&Maintenance
We sign contract on the following support&maintenance of your software. In IT known as an SLA (service level agreement). Clients enter into SLAs with developers because no software is ever finished. It acts a bit like an organism. It becomes outdated, sometimes breaks or even collapses. Or it just stops doing what you expect it to do. And who better to take care of it than the person who made it?
In SLA, the deal is that for an agreed amount, we’re on the phone and whenever something needs to be fixed, we’ll take care of it. We have time booked for you and will resolve issues as quickly as possible so that your business continues to make a profit. We keep an eye on when you need to update to new versions ourselves to keep everything running smoothly.