Customer Meeting #1

Meeting Details

Part 1:

• Platform: Zoom
• Date: 06.04.2021
• Time: 16.00-17.00

Part 2:

• Platform: Zoom
• Date: 07.04.2021
• Time: 16.00-17.30

First part of the meeting was carried out during the PS hours where we couldn't ask all of our questions. Therefore, we also arranged a meeting during the weekend to ask our remaining questions. We decided to combine the notes of these events in the same page because in the second meeting we only asked few questions, we talked about our work, requirements and got some feedback during the rest of the meeting.

Q&A

• Q: What are the types of users? Are spectators, event creators and sport field owners separate types of users with different rights?
  A: There will be only one type of users. Therefore, they will have the same permissions. All the events will be created and maintained through posts. Also, sport field owners will be able to post about their sport fields.
• Q: What happens if enough people do not register for an event? Is the event automatically cancelled? Or can it be delayed?
  A: Events may be delayed until sufficient number of players register. Also, once the event is delayed, users who have already registered will be notified and will be able to quit the event.
• Q: What are the items to be tagged with semantic tags? Are they badges or equipment?
  A: This topic will be explained later.
• Q: What are the responsibilities of admins?
  A: There might be a reporting system which will be maintained by admins.
• Q: What are the limitations to badges? How many types can exist? How many badges can be rewarded by the event creators?
  A: There will be three types of badges: badges that are rewarded by the system after participating in some number of events, that are rewarded between users (MVP, Fair player) and that are rewarded by the event creator. We might start with some basic badges and add some badges that are requested by the users. There will be also some badges that indicates some bad behavior, so earning a badge is not necessarily a good thing.
• Q: To what extent can event creators and users communicate? Can they communicate through a messaging system?
  A: Users will communicate through posts and the comments of these posts only. There will not be a messaging system for now.
• Q: Can users follow each other?
  A: Users may follow each other. This following mechanism will only allow users to be notified about the events that are created by the people they follow.
• Q: What happens if a user doesn't participate in an event they have registered? Do they get a penalty after they don't show up multiple times?
  A: There will be a blocking mechanism. Users will be able to block such irresponsible users.
• Q: What types of analytics are kept about users?
  A: Analytics will cover the details about the level of players, age group. These analytics will not be specific sport related analytics such number of goals and assists.
• Q: Do spectators notify the event creator that they are coming to watch? Can they come without notifying?
  A: Spectators will also notify the event creator, there will be a quota for spectators in addition to the registered players.
• Q: Which browsers should the software be compatible with?
  A: For now, only one or two browsers will be enough. Chrome might be a good choice.
• Q: What personal information will be shared with the event creators?
  A: Event creators might check the profiles of the users. Users may write some comments about their level and interest instead of just selecting from some categories. Personal data will not be visible to other users unless the user makes their info public. Therefore, event creator will only see the information the user decided to make visible.
• Q: Will the event creators be able to notify the users they have been recommended?
  A: This will not be implemented like a recommender system. Event creators will visit the profile pages of the applicants to decide who to choose.
• Q: Must users share their location? Or is it optional?
  A: It is optional. If the user decides to share it, they will be notified about the events near them.
• Q: How are the equipment shared?
  A: They are shared through posts. Sellers can link their websites or share the address of their stores. People who post equipment don't even need to be sellers, they might just share some equipment they like.

Conclusions

• Functionality of the application will be provided by posts only.
• We should not shape our requirements around the implementation too much.

Actions to be Taken

• We have to update our requirements according to the feedback we got. Especially, the requirements about equipment and sports fields should be reviewed.
• It is also a good idea to gather multiple requirements with similar functionalities to a single requirement. For example, requirements "Events shall be sorted according to.." should be merged into a single requirement.