Once the requirement gathering is done with every group of people across departments and functions, you will have a long list of requirements from each of them. Among these requirements, not all the requirements will be important and urgent, but still everyone would like to get their requirement done at the earliest, probably because of their curiosity towards Qlik Sense or due to the pressure from senior management. In such situation, it becomes difficult to prioritize the requirements in such a way that every department gets some of their requirements implemented.

To handle this kind of situation, you need to be able to prioritize the requirements. There are various prioritization techniques available which can be used, but the one which I use and would like to talk about is the Must, Should, and Good to have strategy. The idea of this strategy is taken from the MoSCoW prioritization technique, which is used in agile methodology. This technique was developed by Dai Clegg.

The MoSCoW technique categorizes the requirements into four main buckets, which are Must have, Should have, Could have, and Wont Have. The MoSCoW methodology is more suited for software development projects, but to make an effective use of this methodology for BI projects like Qlik Sense, we can concentrate on the main three categories, which are Must Have, Should Have and Good to Have(could have).