Wearables E-Commerce Project

See the list of TEAMS

You will make use of everything that you have learned thus far in the bootcamp to build an e-commerce app that will showcase all of the provided wearables items.

The stack is React.Js, Redux, Node.Js, and styled-components.

Your node server should be RESTful and follow REST principles, at least to the extent we learned during the bootcamp.


✋ You CANNOT use any external UI libraries, including, but not limited to, Material UI, Bootstrap.


Getting Started

You have your assignment and your team. What should you do first? This will vary for every team, and even every team member.

The important thing is to NOT just jump in and start coding!

There probably shouldn't be any coding until very near the end of the first day.

Meet your Product Manager!

Each team has been assigned a product manager. This person is in charge of answering questions, guiding you and basically preventing everything from falling apart!

This person should be present for some of your team meetings, but not all. PMs are super busy people and have multiple projects, people to manage. 😉

Planning

  1. You will break into 3 groups (with your assigned PM.)
  2. Your PM will answer any initial questions, and give you more information, as required.
  3. Breakout into a separate meeting with just your team. Your PM will bounce from team to team to make sure you're on track.
  4. Time to use the Kickoff Meeting Agenda

First team meeting

It could also be a good/fun idea to give yourselves an original team name. :)

Your first team meeting should start with the Kickoff Meeting Agenda.

Successful Software Project Delivery in 10 Steps.

💡 How a project starts is indicative of how it will end.

Teamwork

The most important aspect of this project is the ability to work in a team. No matter your contribution to the project, you should understand the FULL codebase. This will require that you

  • review each other's code
  • ask questions when you don't understand
  • comment your code extensively. Always go for clarity over brevity.

GitHub

see the GITHUB Document