The goal of this project is to create a cloud app to be used by both organisation members and organisations to note, specify and plan successful events.
GNU General Public License v3.0
0
stars
0
forks
source link
[US 2] As an Event planner, I need to get a list of all the events and the types they were listed as, to have examples for each event type and to know the specific events already organized from each event type. #2
This task is a continuation of the core function and it's concerning the Event planner who now not only needs the numbers of the specific event types planned through which they know about the event type's popularity, but also which events were considered as which event type. While for example "Watching a movie" as an example for the event type "Film/Series" won't help the Event planner, an event like "Golf" being mentioned ten out of fifteen times in the category "Sports" might be a good indicator for the popularity of this specific sport.
That means, that the original functionality from US 1 will be expanded to include this.
The scope is esteemated to be low in comparison, as most of the code written for US 1 could probably be reused.
Although this is just an extension of US 1, it is still categorized as priority two to make the by the application proposed unique selling point complete.
Based on this more "normal" functions can be added for The User.
This task is a continuation of the core function and it's concerning the Event planner who now not only needs the numbers of the specific event types planned through which they know about the event type's popularity, but also which events were considered as which event type. While for example "Watching a movie" as an example for the event type "Film/Series" won't help the Event planner, an event like "Golf" being mentioned ten out of fifteen times in the category "Sports" might be a good indicator for the popularity of this specific sport.
That means, that the original functionality from US 1 will be expanded to include this.
The scope is esteemated to be low in comparison, as most of the code written for US 1 could probably be reused.
Although this is just an extension of US 1, it is still categorized as priority two to make the by the application proposed unique selling point complete.
Based on this more "normal" functions can be added for The User.