StrawberryPick / Strawberry

0 stars 0 forks source link

Data interpretation/usage #115

Open veponen opened 2 years ago

veponen commented 2 years ago

In this phase especially with this subject matter, rough dashboards are outlined for the user. Dashboards are aimed to serve needs of user.

Epic C, Scrum 1

Dashboard is going to be used when someone reserves picking day. User needs to be able to tell if strawberries are with current understanding available when customer wants them and thusly can take the reservations or suggest later or earlier date. (future development: batch runs checking current reservation status with updated harvest prediction. This is to see if we have oversold strawberries)

model to be checked with real data later so that some treshold value can be changed to predict relation

Epic A, Scrum 2

Dashboard is going to be used for reservation changes if heavy rain is predicted for close future. Keyword dashboard is being used to determine when marketing campaign should be started: since we know already we can tak e future reservations, it is about when customers get active and we can get them calling to us for reservations in the future.

Report of customer review data is going to be used for developing marketing and pic-your-own operation towards known customer preferences instead of only guessing what they might be happy with.