You are on page 1of 2

https://www.youtube.com/watch?

v=LMIWMFSr-NY

1. Be confident! Everyone is in the same boat, feeling anxious and skeptical. Be


confident of your skills.
2. Make a google doc or similar space for collaboration
3. Get acquainted with github, that is where evaluation will take place
4. Start researching about the NPOs as soon as their names are released
a. Mission statement
b. Objectives of the organization
c. Where do they function(demographic, webpage/app)
d. go through their social media handles
5. In the morning(7 am), problem statements will be released and teams will be given
30-60min to go through them
a. crucial time
b. decide the project, tech stack, probable solution
c. Pain point at this point: conflicts amongst team members, resolve them, all
should be team players
d. Fill the form quickly, to receive the choices that you filles
6. A buffer time of 1hr will be given, after which team can interact with their NPOs to
gain insights
a. 30-40% efforts should be made on understanding the problem statement
b. Know the requirements well, for instance, they might not require a
website/app so think otherwise
7. Do not be domination, be a team player
8. Think of a team name before hand
9. It is not necessary that the winning team will get the internship, the team who
displays the best team collaboration will land up an internship role.
10. Have templates ready before hackathon due to time crunch and limited resources:
a. UI/UX template
b. ppt template
c. video template if any
d. github readme template
e. web/app templates
f. go through github projects for similar tasks to save time
11. observe space efficient ways in hackathon during video editing or any other
development
12. SMEs are people skilled in their domain(ML etc), seek their help whenever needed
13. 2 hrs before project submission, start with your deliverables
a. video
b. read me
c. ppt
14. Push your code side by side, do not wait till the end, since issues can crop up on
github and make a panic environment for the team
15. Make a user friendly demo, not something where u are opening cmd
16. If an NPO does not specify a web/app, select one where the requirements can be
integrated efficiently,
a. for instance, if requirements are of camera, live location, dynamic notification,
then go for app
b. if your user does not come on portal often, notifications are not to be updated
often, then opt for web

17.
18. search CFG-github to get project from past cohorts

You might also like