Is there anything worse than finding out something isn’t going to arrive when you thought it would? Well, after the disappointment has faded you quickly realize that it costs a lot more than just your good mood. Seems sensible that we should all be aiming for fewer delays, but how do we achieve that?
Cutting the delays involved in deploying apps is an obvious goal that lead developers and app managers aim for. But often there is greater focus on just processes rather than the tools those processes run on. It’s all well and good clearly outlining responsibilities and SLAs, but if the tools that help achieve those things aren’t up to scratch, those goals will stay out of reach.
Let’s set the scene, you’re working in a business with hundreds or thousands of apps, a full team of in-house developers, and offshore development capacity that your team taps into as necessary. It’s fair to say that in this situation there are so many moving parts involved in your app portfolio they can’t possibly be managed by one person.
Well, we’ve worked with multinationals where a single FTE has actually been responsible for app deployment across the whole business. You might be in a similar position yourself, or you might have a team member to whom you’ve entrusted that responsibility. A word from us – this isn’t a good idea. Critical points of failure are not a good way to reduce deployment delays.
With that said, even if you have fewer apps across a smaller business, the typical steps involved in deploying an app are usually inflated beyond what makes reasonable sense – certainly when there’s a better way, but we’ll get to that in a bit. Even a quick overview of deployment steps is exhausting. You have to log in to the acceptance server, isolate the app you need, download it, copy the app, import it to Qlik or the production environment, and check the data sources, and only then can you be even slightly confident that it’s ready for publishing.
Imagine what that manual work looks like across hundreds or even thousands of apps. If your business wants to scale, and you’re already dealing with manual deployment delays, it’s only going to get worse.
Isolating the production server is a pretty key consideration from a security perspective. You want as few people as possible to touch it, because they might mistakenly break something, and as the number of people with access increases, so too does its vulnerability to hacks or ransomware.
Keeping production under lock and key as well as cutting down on the manual work of whoever is in charge of production is precisely what PlatformManager does. On top of its features that make the testing and development of Qlik apps a breeze, it’s built to take away the complexity and compromisation of deployment. You only have to give PlatformManager deployment server access, and within 2 or 3 clicks, deployment happens in the background. No more delays, no more headaches.
Want to make deployment better for every single one of your apps? Speak to PlatformManager today.