welcome to the club 😉 I'm in the same situation. My suggestions are seemingly simple, but it took me virtually until now to put them together:
- We decided in our organisation that only the superusers and developers should have the installed client_software, all others
should view the QlikView apps in their browser - that saves us the hazzle of updating on every single machine - but both
alternatives have their pro's and con's.
- Establish a process for the departments/ teams requesting anything from you so you will have something palpable to serve
as a base for documenting what needs to be done.
- Try to create templates for as much as you can to make the creation of new apps faster.
- Make a "checklist" for the "rollout" of newly created apps to the users to make it easier for you - but mainly for others who are not
as familiar with the whole thing as you.
- Try to make important parts of your apps kind of uniform (like the formatting of month_names and day_names,
the naming_conventions of variables etc.)
- Try to keep your apps simple and easy-to-use by using simple types of chart, not the most flashy ones - that,
however, is up to the "clients" you need to cater for.
- Store often-needed information (expressions or dimensions, file_paths and target_values) centrally, in a location where
others (those concerned) can access it.
- Document everything you do, both in the QMC and otherwise (what you are working on, have a plan that is accessible to your supervisors so they see what you're doing and planning to do)
- Document all your apps and generally all of your code - as a rule_of_thumb, insert roughly one line of comment for
every five lines of code (so that others, colleagues can reconstruct what your code is doing and why)
- Document who has what kind of licence and who can access which app(s) so you will have an answer if someone asks you what has become of the licenses they bought.
- Last, but not least: Try to convince your managers early on that (QlikView is not the cheapest solution, but) they will have to invest some money in order to get the most out of QlikView - it's no good starting too small and heaping one improvised solution onto another, you will have nothing but trouble with the often-praised "quick and dirty" fixes... Better do it right from the beginning and have a clean solution.
ah - no, we haven't. QlikView was, in fact, introduced one year before I started, but the one (only one) responsible for it had left a while ago, so nothing was moving in that respect ...
We have, in the meantime, presented our approach and QlikView a number of times, before the local management and Germany_management, but that was already quite a bit down the road from a POC.
I'm sure you will find lots of information about what QV is and what it can do here, however - judging from your nr. of points, you have been here a while, so you probably know anyway - just filter that for what is relevant to your company.
Basically the POC are different from application to domain wise you can also create sample POC with less data and represent the small data there and useful charts to represent the information.
