Hi all, I am a project manager working a healthcare organisation deploy QlikView. We have one consultant and a few staff members that have just attended the Designer and Developer courses but have no real-world QlikView experience.
As part of my duties, I am meeting our various services and capturing their requirements. However, I am struggling to find a satisfactory way to communicate the requirements to the team members. At the moment I am just letting them know where the data is coming from and what are the main axes that the clients are interested in.
My questions to the more experienced developers are: what do you want to hear when you are first asked to develop a QlikView app? What is essential to you? What mistakes have you seen done in the requirements capture phase?
I second Gysbert's suggestion of user stories as a way to state requirements. If your team has taken the Designer & Developer training, they will have seen the two business/project plans presented there. I think those are decent templates for generating specifications for development. Specifically, the identification of audience, Dimensions and KPIs.
As a developer the most important requirements to me are the dimensions and the metrics being utilized in the application.
Having the dimensions and metrics gives me a good starting point, but the requirement phase should be an ongoing communication between the business owner and the team. Very rarely, a business owner knows exactly everything they want by the first POC session.
Having the current reports the business owner is producing as a reference will also help tremendously. In the end it's up to us to take that existing report and turn it into a Qlikview application that blows the current report out of the water.
It's important to be agile throughout the development because the application will go through several different changes based on the business owners feedback. Involving the business owner in the QA phase will most certainly prompt changes from the original requirements.