Project Overview
The project accounts for 50 points, which is half of the contribution to the grade.
In the list below, the number in [] is the number of points for this part.

P0- Form Teams- 4/8

Teams should be formed by April 8th. Please email mse237@gmail.com:
  • Subject should be "P0- Form Teams."
  • Body should include your project team name, as well as the name and email of each team member.

P1- Initial Idea- 4/20

Initial idea [5]. Primarily completed by the team strategist, should be 1-2 pages in length. The primary reason for this document is so the teaching team can give you feedback about your team's idea. Remember to focus on () An important problem that hasn't been solved yet () something that leverages social data that users willingly contribute.

P2- Public Webpage- 4/27

Revise initial idea, create a public webpage for your project [5]. As you create this public webpage, please remember that your audience is a person not in the class who might be interested in the results of your project.

P3- Final Specs- 5/4

Final specs online [10]. Add a "specs" section/tab to your public webpage, which should include:
  • Concise description of project goals
  • Expected results
  • Timeline of milestones / work to be completed over the rest of the term
  • A list of key risk factors, and proposed strategies to mitigate
You should submit P3 by:
  • Create the above "specs" section on your webpage.
  • Add a link to the Project_Teams page pointing to the "specs" section of your webpage.
  • Send an email to mse237@gmail.com, cc your entire project team, use the subject "P3- Final Specs- YourTeamName", the body need only contain a link to the specs section of your webpage.
Please note- coding/development should have begun in earnest by this point.

P4- Progress Report- 5/11

Status report [5]. Coding/production should be well in progress at this point. Deliverable is to add a section to the top of your specs page including:
  • Heading of this section should read "P4- Progress Report".
  • What features/modeling/data gathering has been completed
  • What features/modeling/data gathering is on deck for the next week
  • A candid discussion on whether the project is in good shape- what's going well, what are critical risk factors, etc.
You should submit P4 by:
  • Adding an update to the top of the "specs" section in your public webpage with the heading "P4- Progress Report".
  • Send an email to mse237@gmail.com, cc your entire project team, use the subject "P4- Progress Report- YourTeamName", the body need only contain a link to the specs section of your webpage.

P5- Initial Results- 5/18

Initial Results [10]. No statistical significance is required, but definitely should have some amount of working code/progress on results. Deliverable is to add a section to the top of your specs page include (approximately 2-4 pages):
  • Heading of this section should read "P5- Initial Results".
  • The first section should focus on a list of results- each feature/analysis/task that's been completed. Include a description of the feature, and a link to the relevant section of your webpage if possible.
  • A second section focused around "lessons learned." This should include hypotheses you initially had, how you tested them, and what you learned for the next iteration. A table could be useful.
  • Please order the above list by how important you think each completed task is, and include a short description of your reasoning in each case.
  • A list of what remains to be done for P6.
You should submit P5 by:
  • Adding an update to the top of the "specs" section in your public webpage with the heading "P5- Initial Results".
  • Send an email to mse237@gmail.com, cc your entire project team, use the subject "P5- Initial Results- YourTeamName", the body need only contain a link to the specs section of your webpage.

P6- Final Results- extended to 5/27 (was 5/25)

Final Results [15]. Custom deliverables were created by the teaching team for each team.
For many teams: The landing page for your webpage should be a blog entry covering the following areas:
  • Blog entry. Use this entry as an example.
  • Audience is the outside world; goal is a thoughtful post to share insight in your chosen space.
  • Insightful takeaways about your topic you gained over the course of the project.
  • Why will social data revolutionize your project space?
  • Overall, your entry should focus on being entertaining and highlighting surprising results. Intuitive and/or obvious results need not be highlighted for this part of the assignment.

You should submit P6 by:
  • Adding this blog entry to your website landing page. Alternatively, it can be posted at yourWebsite.com/blog under the heading "MS&E 273- Final Results".
  • Send an email to mse237@gmail.com, cc your entire project team, use the subject "P6- Final Results- YourTeamName", the body need only contain a link to the proper section of your webpage, and any other relevant sections of your webpage you'd like to highlight.

Project Wrapup

Three selected groups will present to a panel of VCs on May 27th. The rest of the projects will present June 1st.