Skip to content

Latest commit

 

History

History

class-14-project-week-day-1

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 

Class 14 - Project Week: Milestone 1

Final Project Rules and Process

For your final project, your task is to work with a team to build a web site that simulates a real-world product, service, or game.

Rules:

Your team must adhere to the following requirements.

  • There can be no more than 4 people per team.
  • Each person must make meaningful contributions in HTML, CSS, and JavaScript.
  • Your web site must have at least 3 interlinked pages and clear navigation.
  • Your web site must have at least 2 pages that accept and process user input.
  • Your web site's state must persist between page reloads.
  • Your web site must be deployed live on the Internet.

Process:

Here's the process that we'll be using for project week.

  1. On the first day of project week, your team must submit a proposal to an instructor.
  2. During project week, your team must work on-campus so we can help whenever your team is stuck.
  3. On the last day of project week, your team must present your project in front of the class.

Project proposals

  1. On the first day of project week, your team must submit a proposal to an instructor with the following information:
  • Your team's name
  • Your team's members
  • Your project's pitch. (What is the problem statement and what are the benefits of your solution? Read more about these here.)
  • A diagram of relevant details from your project's domain model
  • A few wireframe sketches of your project's pages

TIP: Use pencil and paper to diagram and sketch.

Proposals, written or electronic, as per the project description, are due for review with the instruction team. First come, first served!

Due at 9:00pm.

Here are some tips on how to organize your team during the launch phase.

  • Elect a Launch Driver who will be responsible for the following:
    • Driving the coding of the initial scaffolding phase.
    • Hosting the code under their GitHub account (or create a new GitHub organization for your team and an organizational repo for the project)
  • The rest of the team will be Launch Navigators and responsible for the following:
    • Navigating the coding of the initial scaffolding phase.
    • Staying one-step ahead of the Launch Driver by researching unfamiliar technology.
  • Once everyone is in agreement, here's how to launch a new project.

Make a plan, and get to work!