Girls Can Code - 1/27/17

Girls Can CodeM e e t i n g 1 0 - 1 / 2 7 / 1 7

+   t e c h n o v a t i o n

voting, scheduling, and thingssplitting up meetings

alternative meeting times

time commitments

finding a problemWhat is the problem? In design terms, this alsotranslates to: what is the needWho does the problem affect and how? This isimportant because the people who are affected by theproblem will be the users of your app. They will beyour stakeholdersWhy is it important to solve? Why is this problemcompelling and do you have any evidence of theproblem to back up your argument?What is the solution? You may have an initial idea fora solution. You will be experimenting more with thesolution in this unit as you get to know your user andthrough paper prototyping!

Brainstorm and write down all the possiblestakeholders for your project

To find out what stakeholders want the appto do, you will need to interview them. Youcan ask questions to help you find somefunctional requirements of your app.

Interview to learn more about the problemand get their thoughts about the solution. Ifapps already exist to help solve the problemyour team is focusing on, you can ask usersabout the app and what they like or what

doesn’t work so well for them.

JUN IOR TEAMSEN IOR TEAM

first opening screenlogin screensign in screenmonitor / information screenhow-to-use screennormal screen v .s alert screensettings config screenemergency contact inputscreen

T H A N K Y O Uf o r b e i n g a p a r t o f o u r d a y

L o v e ,F r a n k & L i l y

https://www.youtube.com/watch?v=JMjozqJS44M