Assignment #4

Innovate 2Z03
Professor Glen Crossley
Winter 2023
Group 24
Adam Azarifi 400236258

Aman Datta 400167826

Aryaman Maheshwari 400230920

Marzouq Khan 400186210

Yuv Arora 400275953

Stage 1 Stage 2 Stage 3 Stage 4 Stage 5 Stage 6

User must The user is The next Next the user Assuming The final
click the ‘Sign brought to the screen will see their the user has screen allows
in’ button to search page, displays a route & started their the user to
enter the next where they list of different journey, the rate & review
page must input destinations journey screen will their
their (including times display the experience
Enter your destination to the input) live location with using
McMaster retrieve details related to the There is an with the peripheral for
email & your desired option to highlighted their journey
password in They’ll be location choose route
the appropriate able to see a between their
boxes surrounding All details method of As the user
map and must regarding the transport moves, the
Click Sign In click next to users live features
move on potential Click ‘Start’ will update
journey will to begin as it goes
be shown journey
here Upon
arrival, the
This is ‘Complete’
where the button will
user must highlight for
click their clicking
destination

1
2) An updated list of “How might we?” questions that address the new uncertainty (or
uncertainty you didn’t address in your first sprint) in your proposed solution sorted into
themes.

3) A solution sketch from each team member that shows their proposed solution illustrated
with enough detail that someone could understand what you are proposing to do.

2
Sketch #1

Sketch #2

3
Sketch #3

Sketch #4

4
 Sketch #5

4) A review of the solution sketches by the team that highlights which parts of each solution
the team thinks is worth further investigation.

After further reviewing all of the solution sketches, we found certain features and parts of
the sketches we want to further investigate and possible incorporate into our app for future use.
We’ll begin with Sketch #1 and #2 as they have similar features we believe would enhance the
experience of the user. This feature is selected from Sketch #1, #2 and #5, the sign-in feature
which would require you to us your educational email account and will enhance security and
safety by preventing people who do not attend universities from abusing this app. The sign in
feature will allow you to access universities other than yours as well. Furthermore, Sketch #1 and
#2 use a screen which displays the result of your chosen destination is essential. It provides basic
information regarding the destination such as the rating, hours of operation, list of similar
locations (recommendations) and traffic. Incorporating this information, along with the capacity

5
and vacancy of the location, will provide users with any additional information they would
otherwise require to use Google search for.
From Sketch #2 individually, the review and comments section on Peripheral would
provide us and other users relevant information while choosing their destination. If the reviews
and comments are viewable for users, they can read reviews and make decisions upon reading
the reviews. These reviews can be about the destination or the user’s experience with the app.
From Sketch #2 and #3, the option of viewing your travel methods to reach the destination is
essential as well. User’s (especially ones who are commuting) away from campus can use this to
plan their schedules that would either require them to walk, transit, take an Uber/Lyft or drive.
Sketch #3 provides you with an option to integrate your schedule and sync your lectures and
classes into the app. Through this the app can provide notifications and timely information to the
user, making it easier for these users to reach their respective destinations on time. We hope to
personalize and ease the users experience through this.
Sketch #4 has a favourite option when you are in the process of choosing your
destination. This favourite option allows users to save locations, that they visit often or want to
visit. This is aimed to enhance user experiences by making it convenient for them to select these
locations and to provide a more personalized experience. Sketch #5 brings two new ideas to the
table, namely the app tutorial for new users and the share button. The first idea allows us to
convey the easy interface of the app as well as many of it’s functions. Additionally, Without an
app tour, users might have trouble understanding how to use the programme and risk making
mistakes. Users may become frustrated as a result and perhaps stop using the app altogether. The
likelihood of errors is decreased by giving users a tutorial tour so they can use the app more
effectively and avoid making typical blunders. Secondly, the “share” option presents various
boons. Firstly, sttudents may quickly share the app with their classmates and peers by adding a
share button, which may promote app acceptance and usage. This can be particularly beneficial
in the early phases of the app's introduction because word-of-mouth can aid in generating interest
and spreading awareness. Secondly, users can quickly and simply inform other students who
might be considering visiting the same building about occupancy levels by using the share
button. More people reporting occupancy levels will result in a more complete picture of the
present situation of each building, which can assist to increase the accuracy of the data the app

6
collects. When there are campus activities or peak periods like test season, this might be
especially helpful.

5) A clear statement of what the team would plan to prototype moving forward and why.

In addition to the features we have already identified, we will be placing trackers around
the student center in order to test the viability of the tracker and gather data on store traffic and
wait times. Our next step is to release a beta version of the app to a selected focus group to
gather feedback and refine the product further.
We strongly believe that releasing a beta version to a focused group is critical for several
reasons. Firstly, it allows us to test the app in a controlled environment and address any bugs or
issues before launching it to a wider audience. Working closely with a specific group of users
enables us to receive detailed feedback that can be used to improve the product based on their
specific preferences and needs.
Secondly, releasing the app to a focused group can help us build buzz and excitement
around our product. By targeting early adopters and influencers, we can generate interest and get
valuable feedback to refine our marketing and messaging.
Lastly, a focused beta release can help us establish relationships with key stakeholders
and partners. By collaborating with a specific group of users, we can create strong relationships
and identify potential partnerships that can help us grow our business and expand our reach.
To release our beta version to a focused group, we plan to identify the appropriate users
to target. This could involve partnering with student organizations or reaching out to specific
departments or programs within the university. We will also need to create a comprehensive plan
for gathering feedback and incorporating it into our product development.