After last weeks meeting and having done the project requirements documentation, there was a distinct issue with the application that I was beginning to see. To me, the scope of the project was not specific enough. We were trying to tackle and application that was explicitly for tracking expensive wines with incredible detail and accuracy. At the same time we wanted an application that could be widely used by wineries to provide the majority of their customers with general wine information. These two project end-goals were at direct odds with each other in my thinking. So I went to our project partner and expressed this dilema.
The project partner was clear: general and wide use is more important than specificity that helps only a small group. So we restructured the project requirements based on this feedback and I think we finally nailed the project on the head. Overall, wineries will be able to add wines that they have created and generate individual QR-codes for each bottle. There will be some general fraud detection based on some location data that is given whenever a QR-code is scanned by a phone, but the fraud detection takes a backseat to the general use case of “a consumer scans a QR-code and gets the information on the wine”.
There was some minor disagreement among the team; nothing to be concerned about, but some clarification was still in order. The general consensus that the team came to was if a user had location data enabled, they would be able to mark that they had bought the wine bottle, if they input their own information. The application would then check to see if the wine bottle was being “purchased” at the same location as the last time it had been purchased. If this was the case, the new data would overwrite the old data, and that data would never be officially added to the bottle’s history. This allows for people who truly care about the wine bottle’s transaction history to continue to keep track, while also being user friendly enough for the general customers.