In QlikView, the implementation phase was predominantly developer- and IT-focused. Agile development processes introduced a way to maintain a close feedback loop with the business. While the same is also possible in Qlik Sense, the question resides on whether the business will become part of the implementation as well.

If the user becomes heavily involved in the development process, the implementation of Qlik Sense projects becomes interestingly interactive. Instead of having close iterations with the business on their app, you can start actively involving the user in the development themselves. Give them the data, show them how to create a couple of basic charts, and let them do it on their own. Once they're happy with the general design and context of the app, you as a consultant/developer can take it away and beautify it and make it more robust and production-ready. Your involvement in such a scenario will revolve around building extensions for the users and be writing the data model, as well as planning the architecture of the Qlik Sense environment.