Specifics we want to see

Think UX

Use your user personas to craft a user journey and experience that stands out and solves the problem you set out to solve
We want to see a custom front-end experience, and hear the reasons why you've chosen to design it like this
The look, feel, and brand of the product/app should all align and we'd like to hear the reasons you've decided this was the right approach
Make sure you highlight anything you want people to see in your presentations - we can only know what you show us, so if you've got a cool little animation or feature, be sure to show it clearly rather than expect people to notice

The problem should be solved before you start coding. Use Day 1 to work out who you are solving the problem for, what the problem is, how best to align with your target user in terms of creating a brand/user journey and what the priorities are to deliver value to your users and then getting the whole team set up so that everyone is ready to code and on the same page with a well planned backlog of tasks to deliver.
Use the steps of Disney ideation to ensure you make space for all of the phases of the ideation process.
Plan out the structure of your app, including a component tree mapping out the states, behaviours, and information/functionality handed down via props before you start coding. Don't be afraid to come back to this plan if something changes further down the line in the project!

Keeping in sync with each other is vital, and stand-ups are a great way to do this. There is no limit on when stand-ups should be, that's down to you as a team... many teams do a couple a day to check-in quickly with each other. Remember, it can be rapid - the point of a stand-up is a quick glance at what's going on, and if there are any blockers anyone is facing
Being clear about who is doing what is helpful when working across a team
Performing code reviews is a great way of getting more eyes on the code, and keeping people up to date with what's happening
As you build and progress through your tickets, keep checking the plan and keeping it up to date so everyone stays on the same page throughout.

Days 2, 3, and 4 should all be spent pair programming
We want to see a different pairing each day
For a team with an odd number of members, that might mean one person may be on their own each day or in a three, but this should be a different person each day and only by neccessity

You should be using environment variables where you think it is appropriate, and be comfortable with why this is important to do in building applications
You should use the core technologies that we have covered on the course so far - think JavaScript, Node, SQL, and React

10 minute presentation slots, with some Q&A after. Try to stick to the timings!
Share the talking evenly around the team; everyone should contribute to the planning, building, and presenting
Practice beforehand and time yourselves

Introduce yourselves (10 second intros!)
Briefly explain the problem you are solving
Live demo your app, 3-4 mins to explain your solution, how your app works and how it solves the problem
Briefly talk through how you approached the project (git and github strategy, planning, team roles, etc)
Finish, and questions