More and more projects now rely on data in decision-making. Separating the wheat from the chaff, aka useful information from noise, is not always easy and obvious. When initiating a new product, it can be difficult to determine the appropriate order of actions to get reliable insights. How to effectively set up the process of collecting and implementing requirements on a data-oriented project while maintaining focus on the business features of the client's product? And where is the line between "too many words" and "too much technology"?
In our talk, we will talk about the quirks and challenges of the business analysis initiative on projects focusing on large amounts of data.