Skip to content

Commit

Permalink
Update 5-mvp.md
Browse files Browse the repository at this point in the history
  • Loading branch information
ntissieres authored and unglazedstamp committed Jun 7, 2024
1 parent 5478380 commit 30b6405
Showing 1 changed file with 52 additions and 15 deletions.
67 changes: 52 additions & 15 deletions template/5-mvp.md
Original file line number Diff line number Diff line change
@@ -1,34 +1,71 @@
# The MVP

## Personas and Scenarios
## Personas & Scenarios

*Who are the target personas for this product?*
Echo is intended for EPFL students, with first-year students as the key persona. It is these students
who would benefit most from the application, as many of them don't know anyone yet. Although our school
organises groups to meet in BA1 (Coaching), it doesn't provide as personalised an experience as Echo.
If successful, we aim to replace/improve this service. In addition, our application offers events for
all levels, which is beneficial for our second and third personas: exchange students and repeaters.
Our fourth persona is students from all other years who want to meet new people or do an activity with
other enthusiasts. Our last persona is the associations. They are the first to organise events on campus
and struggle to promote their activities. Our application would give them extra visibility.

*Which is the key persona?*
## User Stories

*High-level scenarios to adopt, use and share the product.*
### User Story First-Year Student

## User Stories and Key Features
1. As a first-year student, I want to be able to take part in events with my class to meet people I can work with.

*User stories about how various personas will use the product in context.*
### User Story Exchange Student

*Identify and prioritise the key features required.*
1. As an exchange student, I want to be able to take part in EPFL public events so that I can integrate more easily into my new environment.

*Justify the importance of each feature.*
### User Story Repeater Student

1. As a repeater student, I want to be able to get to know my new classmates so that I have people to take classes with.

### User Story All EPFL Students

1. As an EPFL student, I want to be able to join events to pursue my passions.
2. As an EPFL student, I want to be able to meet new people who share the same passion as me so that I can make new friends

### User Story Association

1. As an association, I want to be able to promote my events in order to have more participants.

## Key Features

The main aim of Echo is to bring EPFL students together. That's why our application allows them to organise events around their passions, bringing together students from the same class or section. The key to our success lies in the number of events actually organised. Key features of our app include:
* Event participation - This is the most obvious feature, offering our users the chance to discover personalised events based on their passions and curiosity. They can easily find them thanks to a powerful search tool and profile customisation.
* Getting to know people from the same background - Coming to EPFL can be difficult, especially if you don't know anyone. Echo is keen to encourage people from the same class or section to get to know each other, so students can organise events restricted to a certain milieu.
* Associations - At present, the associations are by far the most active in creating events on campus. However, they all have the same problem: a lack of participants. Echo enables associations to promote their events to users and reach their target audience more easily.

## Success Criteria

*How will you evaluate the success of the MVP?*
### Event Creation

*Metrics include user penetration, quality / satisfaction.*
To assess the success of Echo, we will be looking at the number of events officially held. We estimate that an event brings together an average of 10 people. Our application will be a success if we manage to organise at least 1 event per week for every 100 students. So, for a first-year computer science class of 600 students, at least 6 events should be organised within this class using our application.

*If applicable, progress in discussions with ecosystem partners / investors / customers.*
### User Adoption & Engagement

## Features Outside the Scope
* In its first month at the start of the academic year, our application plans to reach at least 30% of new EPFL students (first-year, exchange and repeat students ~ 1,000 users), and at least 10% of the rest of the student body (~ 1,000 users).
* Since our events are generally organised on a weekly basis, we're mainly expecting weekly rather than daily users. Our aim is to achieve a DAU of 5% (100 users) and a MAU of 80% (1,600) in the first month of its launch.
* We expect the application to be used a lot at the beginning of the semesters and then to be put to one side slightly at the end of the semester/exam periods. However, we still expect to be able to achieve a retention rate of at least 50%.

### Feedback & Satisfaction

*The MVP must be viable and minimal.*
* We hope to achieve a score of 4 stars out of 5 in the Play Store ratings. We will be regularly monitoring feedback to identify recurring comments about our application, and adapting our approach accordingly.
* A survey will be carried out at the end of each month to respond to requests from users who would like to add new categories, and to ensure that each of them has at least one event available per week. This will enable us to assess demand and, why not, try to improve the visibility of certain activities that are struggling to develop (special events organised by the application).

*Which features don’t belong in it.*
### Association Implication

* Contacting all the associations to offer them the use of our application
* Success would mean serving 70% of EPFL's associations

## Features Outside the Scope

*How should these be eventually integrated and in what sequence.*
* Exclusion of AI to recommend events - One of the things we wanted to do for our application was to introduce users to new activities using a recommendation algorithm. Based on our users' habits, we could train an AI to come up with a viable model. This feature is out of scope because we don't currently have any users, and we haven't found any data accessible online of sufficiently good quality to have a good model. But it's still worth keeping aside in case we have the necessary resources.
* Exclusion of a multi-tenant Saas - What we're doing with EPFL could very well be replicated for every other school, company or region. Creating a more universal application, while remaining customisable for each environment, is a step we haven't yet explored. To begin with, it was simpler to focus on a structure that we knew well, the EPFL. The advantage of making it a multi-tenant SaaS is that it allows users to get used to using a single application regardless of the environment in which they find themselves. In this way, Echo could become for events what What's app is for communication.
* Exclusion of a degree of trust - Currently, all users can create and join events as they see fit. We're still not happy with this solution because it gives too many opportunities for malicious people to carry out activities that go against the ethical line of our application. We had envisaged assigning a level of trust to each user, not allowing them to organise events until 3 months after downloading the application. This right could be withdrawn in the case of abuse. However, our application cannot afford at the outset to refuse to organise events as a precaution, given that we do not yet have any users. We'll be moderating the application manually to start with.

0 comments on commit 30b6405

Please sign in to comment.