Once you get used to QlikView's development style, it is easy to create new applications from the scratch disregarding its folder structure, the location of its data sources, or the overall portability of the environment. However, these elements are not to be ignored as building unstructured apps usually leads to inefficiencies and rework.
Having a robust yet simple folder structure available to start new dashboards will ensure that all your endeavors can be easily integrated with the current QlikView environment or moved around on different computers.
This structure will greatly vary from environment to environment, and it depends on the number of developers involved, the workload distribution, the complexity of the data sources, and even the personal/organizational styles. Nonetheless, it should be able to handle several applications (not only different modules, but also different versions of each one of them), a layered QVD structure (files and generators), general files...
