1. 
   Three vetted ideas presented to Priya on Zoom meeting - Sep 29, 11:59PM: Each person in the team comes up with a novel app idea (based on above criteria). Email Priya CCing all members in your team with your availabilities for a zoom meeting with Priya. You needed to have met with Priya to discuss your ideas by the deadline.

1. Finalize Idea: Finalize one of the three ideas based on instructor input. Come up with a name for your App. This is the AppName.

1. Readme file is created in the repo. It outlines the course, section number, group number, app name, student names, student ids and email ids for the project. This must be created at the time the GitHub Repo is created, and must be updated periodically as needed.
   

1. Must be submitted on blackboard by the team lead. The proposal must also be checked in to the GitHub Repo under ReportsAndDocuments. See Proposal Template for details. 

1. Must be submitted by EACH STUDENT INDIVIDUALLY IN A TEAM. See progress report template document for details. Progress report must reflect nature of work done, dates and hours of work put in each day. Individual Progress Report must be submitted via blackboard and checked into the GitHub Repo under ReportsAndDocuments. 

1. Must be submitted by the team lead on blackboard. The Requirements document must also be checked into the GitHub repo under ReportsAndDocuments. Requirements Document template will have more details.


2. Requirements Gathering – USER STUDY 1 (at least 10 participants for survey, fewer if doing an interview with script)


3. Requirements Generation

1.  Must be submitted by EACH STUDENT INDIVIDUALLY IN A TEAM. See progress report template document for details. Progress report must reflect nature of work done, dates and hours of work put in each day. Individual Progress Report must be submitted via blackboard and checked into the GitHub Repo under ReportsAndDocuments. 

1. 
   Prototype (Nov 2, 11:59 PM): In Figma, create main workflow of the prototype with a name F25_3375_S#_G#_AppName. Add the instructor (kandhadaip@douglascollege.ca) as a collaborator to the project. It is optional to create a team. If you create a team, the team must be named with the same name F25_S#_G#_AppName, and add instructor as a team member. All other work flows within your project can be named misc or anything else but the main workflow must be named with the correct naming convention. 

The prototype you will design in FIGMA a full-fledged prototype in FIGMA for a novel app with high utility providing a transformative experience to the user. THIS IS NOT A CODING PROJECT. You are creating a hard coded prototype in Figma prototype with screens and user gestures/interactions in the prototype. Each screen has full color, with appropriate sample text, images. Where there are multiple items on a screen, you will show 3 to 5 items on the screen as a sample. And you will hard code the end to end interactions for 1 to 2 items so that you get a good idea of what the prototype will look like. Complete the PROTOTYPE by Nov 19.

1. While you complete the prototype, create the user study survey for prototype. After the prototype is complete, you will conduct USER STUDY 2 with a new set of users (at least 5 participants) who experience your protoype, and answer a specific survey regarding user experience with your prototype. Note that this USER STUDY is different than the earlier one with a new set of users, new survey. Complete this and obtain results by Nov 24.

1.  Must be submitted on blackboard by the team lead. The final report must also be checked in to the GitHub Repo under ReportsAndDocuments. See Final Report Template for details. 

1. To Come: FINAL DEFENSE and DEMO IN-CLASS – Last Lecture Day: As a team, you will be doing a final defense and demo of the prototype. More details on duration and format will be released.