accesscode-2-2 · NataliaEstrella · Nov 4, 2015 · Nov 4, 2015 · Nov 6, 2015 · Nov 6, 2015
diff --git a/README.md b/README.md
@@ -1,54 +1,8 @@
-### Unit 3: Final Project
-
-All apps:
-  *  Will solve a relevant problem that serves an existing market
-  *  Are technically complex and ambitious enough to highlight the skills you have gained
-  *  Are fully functional and polished for presentation at Demo Day  
-
-With that in mind, things to think about when ideating projects are the **technical complexity**, **design**, and **product**.  
-
-###[Final Project Schedule](/final_project_schedule.md)
-
-###[Final Project Rubric](/final_project_rubric.md)
-
-###[Groups](/final_project_groups.md)
-
-
-###App requirements:
-*  Overall product requirements
-  - Technically complex
-  - Compelling use case
-  - Polished implementation (UI/UX)
-  - Original product 
-  - An engaging pitch that connects with the audience
-*  Basic technical requirements 
-  - Does not crash
-  - Does not hang (little or no delay visible to the user)
-  - Does not fail when internet connection is slow/unavaialable
-  - Have a consistent look and feel visually across the app
-  - Consistent with [iOS Human Interface Guidelines](https://developer.apple.com/library/ios/documentation/UserExperience/Conceptual/MobileHIG/#//apple_ref/doc/uid/TP40006556-CH66-SW1)
-  - Look great in both landscape and portrait
-  - Have well-organized, high-quality code
-
-
-### Tips & Ideas
-*  Things that would impress:
-  - Super cool library that other devs could use
-  - Integration of complex APIs (e.g video, web services, etc...)
-  - Awesome UI
-  - Work with the OS in a more intimate way 
-  - Advanced Separation of Concerns
-*  Things to Avoid:
-  -  Unusable: Good technical implementation, but does not consider the end user's interaction
-  -  Non-function: Good UI, but does not actually incorporate the tools needed to be feature complete.
-  -  Obvious: Solution can easily be found in tutorials or examples, copies an existing system tool, or simply strings together APIs.
-  -  Not Useful: This app doesn’t have a clear purpose or solve a problem. 
-*  Some sample project ideas:
-  -  Weather + Calendar
-  -  Poll app / trivia app 
-  -  Really good photo journal app
-  -  Really good note taking app
-
-
-
-
+## Team: Poseidon Project
+### Project: Zetron
+
+###Members:
+* Natalia
+* Dan
+* Kaira
+* Jamaal
diff --git a/final_project_groups.md b/final_project_groups.md
diff --git a/final_project_rubric.md b/final_project_rubric.md
diff --git a/final_project_schedule.md b/final_project_schedule.md
diff --git a/presentation_guidelines.md b/presentation_guidelines.md
diff --git a/project_proposals.md b/project_proposals.md
@@ -1,45 +1,32 @@
-# Final Project Proposal Submission  
-
-### The following is due Tuesday, 11/03 at 10:00pm:  
-
-
-Please create a repository for your final project, with the following contents:  
-  *  README with your group members  
-  *  project_proposal.md (template below. Feel free to use the markdown from this file and fill in your responses.) 
-  *  Your app
-  *  Folder that contains [Weekly Retros](weekly_retrospective.md). (Empty for now)  
-
-
----
-
 # Access Code 2.2 Final Project Proposal
 
-#### For each group, please submit the final project proposal by 10:00 pm on Tuesday 11/03/2015. You will receive feedback on the proposal on Thursday 11/5. 
-
----
 **Project Name:**
+The Poseidon Project
 
 **Team Name:**
+Poseidon Team
 
 **Team Members:**  
+* Kaira Villanueva
+* Jamaal Sedayao
+* Natalia Estrella
+* Daniel Distant
 
 
 ## The Problem 
-Describe the problem that your app will address. This does not need to be a novel idea or product, but your app should not directly recreate an existing product. If you are basing the app on an existing product, there should be some edge to your design or feature that solves a problem with that existing product.   
-
-In this section, please frame the issue with supporting statistics about the need (market size, competitors, use cases). You should fully think through your user - who is your user? Why do they need this app? How are they using it?   
+People are bored.
 
 ## The Solution 
-Please provide a detailed description of the app here. Map out how the app solves the problem described in section I. You should also include:
-  *  Baseline features you plan to implement by Demo 1 (what + why).
-  *  Bonus features you plan to implement if baseline features are completed in time (what + why).
+We combat the crippling effects of boredom with our games.
 
-## Execution
-Please describe how you will build this app. Include: 
+## The Minimum Viable Product - Due Thursday, 11/17/15
+  * Users can connect multiple devices connect via MultiPeer Connectivity 
+  * Users can tell where other users are via MPC/Geolocation/Bluetooth
+  * Users can TAG other users by getting close to them with their device
+  * Users can tell they have been TAGGED because their device registers the TAG and responds
+
+## Execution [SOON]
   *  A detailed timeline for building the product, broken out by weekly sprints. Think about the user stories you would frame your weeks around. *Your polished MVP (baseline features) should be ready to demo by Demo 1 on Thursday 11/17/2015.*  
   *  A breakdown of team member responsibilities. Team members should take ownership over a specific feature or aspect of the app.  
 
 
-[Example of a project proposal (from Mozi)](https://github.com/jaellysbales/access-robot/blob/master/ProjectProposal.md)
-
-[Example of a project plan (from Espy)](https://docs.google.com/spreadsheets/d/1n4XtthaWqkg7YvaTfJZwC9Fc10RKd4JLr4HaUtYAh1c/edit#gid=0)
diff --git a/week1-summary.md b/week1-summary.md
@@ -0,0 +1,50 @@
+## Weekly Retro  
+### Due: November 17, 2015 
+
+**Goals for last week**:
+  *  Create a unified theme.
+  *  Thoroughly research and become familiarized with necessary technology. 
+  *  Connect users via Multipeer Connectivity.
+  *  Detect proximity via Core Bluetooth while users are connected to Multipeer Connectivity.
+
+
+**Goals for this week**:
+  *  Fine tune bluetooth proximity response.
+  *  Research wifi incorporation for proximity detection.
+  *  Implement shake gesture.
+  *  Add sound effects. 
+  *  Refine UI/UX.
+
+
+**Guiding Questions** (consider before the meeting):
+
+  *  What went well?
+    *  Tracking down the necessary technology was difficult, but with the whole team eager to implement it, the task was done quickly. 
+  *  What should we do differently next time?
+    *  Restructure demo process.
+  *  What did we learn?
+    *  Refining the connection between users is essential. 
+    *  Users are receptive to the product.
+    *  We must restucture the demo presentation. 
+  *  What still puzzles us?
+    *  Exactly how to get the BEST proximity reading. 
+
+**Team Member Analysis**:
+If you did not meet your goals, how will this affect the progression of the product? What will you do differently to meet your goals this week?
+
+We met all of our goals. As a result, this gives our team time to refine the product and enhance functionality. 
+
+**Additional Discussion Topics**:
+
+  *  Compare your work planned with what your work completed. 
+    *  We accomplished everything we sought out to complete by this demo. 
+  *  Is the divison of roles within your team working?
+    *  The division of roles works, but we often overlap for the sake of speed and efficiency: One person might be more familiar with a certain task.  
+  *  How is communication and collaboration between team members?
+    *  Communication and collaboration happens frequently. We try to work outside of class as often as possible, and keep each other abreast of any changes and potential ideas. 
+  *  Are you getting adequate support? How are you reviewing code?
+    * Michael Vilabrera, our mentor, regularly checks in with our team and gives us guidance on how to move forward with the project.  
+  *  How can you improve productivity and get the most work done within the next week?
+    *  To improve productivity we could continue having a defined list of goals to accomplish, but having more defined deadlines. 
+
+**Mentor Comments**:
diff --git a/week2-summary.md b/week2-summary.md
@@ -0,0 +1,51 @@
+## Weekly Retro
+### Due: November 24, 2015 
+
+
+**Goals for last week**:
+  *  Create a unified theme.
+  *  Thoroughly research and become familiarized with necessary technology. 
+  *  Connect users via Multipeer Connectivity.
+  *  Detect proximity via Core Bluetooth while users are connected to Multipeer Connectivity.
+
+
+**Goals for this week**:
+  *  Fine tune bluetooth proximity response.
+  *  Research wifi incorporation for proximity detection.
+  *  Implement shake gesture.
+  *  Add sound effects. 
+  *  Refine UI/UX.
+
+
+**Guiding Questions** (consider before the meeting):
+
+  *  What went well?
+    *  Tracking down the necessary technology was difficult, but with the whole team eager to implement it, the task was done quickly. 
+  *  What should we do differently next time?
+    *  Restructure demo process.
+  *  What did we learn?
+    *  Refining the connection between users is essential. 
+    *  Users are receptive to the product.
+    *  We must restucture the demo presentation. 
+  *  What still puzzles us?
+    *  Exactly how to get the BEST proximity reading. 
+
+**Team Member Analysis**:
+If you did not meet your goals, how will this affect the progression of the product? What will you do differently to meet your goals this week?
+
+We met all of our goals. As a result, this gives our team time to refine the product and enhance functionality. 
+
+**Additional Discussion Topics**:
+
+  *  Compare your work planned with what your work completed. 
+    *  We accomplished everything we sought out to complete by this demo. 
+  *  Is the divison of roles within your team working?
+    *  The division of roles works, but we often overlap for the sake of speed and efficiency: One person might be more familiar with a certain task.  
+  *  How is communication and collaboration between team members?
+    *  Communication and collaboration happens frequently. We try to work outside of class as often as possible, and keep each other abreast of any changes and potential ideas. 
+  *  Are you getting adequate support? How are you reviewing code?
+    * Michael Vilabrera, our mentor, regularly checks in with our team and gives us guidance on how to move forward with the project.  
+  *  How can you improve productivity and get the most work done within the next week?
+    *  To improve productivity we could continue having a defined list of goals to accomplish, but having more defined deadlines. 
+
+**Mentor Comments**:
diff --git a/weekly_retrospective.md b/weekly_retrospective.md