dfmorse23 / term-2-partner-project

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Term 2 Partner Project

Objectives

By the end of this term, participants will...

  1. Develop familiarity with product design and development.
  2. Begin to master working on teams by working together in pairs.
  3. Build an impressive project to add to their portfolio and present at the Winter Open House.
  4. Develop greater resourcefulness in generating code, problem solving, and squashing bugs.

Timeline

  1. Week 1 - Pick teams & Ideate
  2. Week 2 - Project Planning Docs - User Narratives, Wireframes, ERD.
  3. Week 3 - Sprint 1
  4. Week 4 - Sprint 2
  5. Week 5 - Sprint 3
  6. Week 6 - Presentations

Requirements

All projects must have the following:

  1. Two partners working together.
  2. An advisor.
  3. A public github repo with a README.md file
  4. A backlog (in todo.txt file) and planned sprints.
  5. Follow a versioned release process (v1, v2, v3, v4).
  6. Be mobile responsive or be a mobile app.
  7. Must be live on the web and in the app store (if app)
  8. At least weekly meetings (on the calendar with a time and location).
  9. Projects must be written in Make School technologies: Python, JavaScript, Swift, Express.js, Flask, React.js, MongoDB, PostgreSQL, etc.
  10. A presentation (5min pitch, demo, and Q&A)

How to Turn Your Project In

Turn in the following links in the Core 2 Project Tracker

  1. Staging URL Link
  2. Github URL Link

The Project Will Be Judged On

  1. Beauty and Usability (UI/UX)
  2. Code Craftsmanship
  3. Teamwork
  4. Project Planning
  5. Creativity
  6. Technical Sophistication

Project Planning Docs

User Narratives

User narratives are stories where you get inside the heads of your users. They are NOT A LIST OF FEATURES.

Here's an example for a user narrative for a "Yelp for Landlords"

[info] Hi, I'm Randy the Renter and I'm looking for housing in San Francisco. I found 5 or 6 places on craiglist to live, but I want to see if the landlord is good because I've had trouble in the past with bad landlords. I go to "yelpforlandlords.com" and search by the address of the unit. The landlord comes up. It looks like they are a good landlord, 5 stars and based on the underlying property value, she doesn't gauge the renters. Awesome!

By fully getting inside the head of a user you can build an app that people actually want to use. This techinque can be used for hardware, software, even when you are building esoteric software development libraries, you always have a user that you want to make happy.

Another example:

[info] Hi, I'm Larry the Landlord and I'm a great landlord and want to read my reviews on yelpforlandlords.com. I visit the page and I look up my name. I find that I have many good reviews and I leave responses like "Thanks! You were a great tenant". On one negative review I try to give context to the problem they had.

  1. Write 3 user narratives for one of your favorite apps.

Wireframes

Wireframes are fast, rough sketches for your major views of your project.

  1. Read this article "How to Create Your First Wireframe" (8 min)
  2. Pick an app and draw a wireframe of the app
  3. pick an website and draw a wireframe of one page. (Don't forget to draw a second wireframe for how the screen looks on mobile)

ERD - Entity Relationship Diagram

  1. Read "Everything you need to Know about ERD".
  2. Now make 3 ERD's - one for each of your favorite apps or websites. (Just guess what their entities are named!)

About