Activate Teen Power in 24 Hours
Teams of Code/Interactive students will design and build a cool tech product that features an original solution for a teen problem.
The problem can be one that....
1. The team experiences personally.
2. Will affect teens in the future.
3. Affects teens in other places.
See a map of the space, LMHQ: http://bit.ly/lmhqmap
Schedule- Saturday, January 30th
12:00pm - 12:30pm Check-in + Lunch
12:30pm - 1:00pm Volunteer Meeting + Student Scavenger Hunt
1:00pm - 1:30pm Event Kickoff + Devpost and Slack Setup
1:30pm - 1:45pm Project Management Presentation
2:00pm - 6:00pm Work Time + Workshops (Main Space)
2:30pm - 3:30pm Workshop: How to Use APIs
(Charlie Swanson, MongoDB)
3:30pm - 4:30pm Workshop: How to Use the Foundation Framework
(Amélie Lamont, VenueBook)
4:30pm - 5:30pm Workshop: Storytelling to Motivate Action
(Carl Harris, Change.org)
5:30pm - 5:45pm Workshop: User Testing with the Javelin Board
(Cris Mercado, The Knowledge House)
5:45pm - 6:15pm Workshop: Intro to UX
(Yangbo Du, Global Resolutions Inc)
6:15pm - 7:30pm Dinner + Keynote (Main Space)
6:15pm - 7:30pm Dinner
6:30pm - 7:00pm Keynote (Ramona Ortega, Mi Dinero Mi Futuro)
7:00pm - 7:15pm Game Development Student Presentations
7:15pm - 7:30pm Demo Student Games
7:30pm - 7:45pm Fun Break Activity (Main Space)
8:00pm - 12:00am Work Time
12:00am - 12:30am Midnight Snack + Fun Break Activity (Main Space)
Schedule- Sunday, January 31st
8:30am - 9:30am Breakfast + Work Time
9:30am - 9:45am Clean uo Time Yall!
10:00am - 11:00 Work Time + Workshops (Main Space)
9:00am - 9:45am Workhop: Using GitHub & Mastering the Command Line
(Daniel Fenjves, Upperline School of Code)
10:00am - 10:30am Workshop: How to Pitch your Product
(David Yakobovitch, David & Co.)
10:30am - 10:45 Workshop: Submitting Projects on Devpost
(Jen Noborikawa, Code/Interactive)
11:30am DEADLINE TO SUBMIT FINAL PROJECTS ON DEVPOST
11:00am - 12:00pm Lunch + Pitch Practice
12:30pm - 1:30pm Student Product Pitches to Judges (Main Space)
1:30pm - 2:00pm Judges Deliberate + Clean Up
2:00pm - 2:30pm Award Ceremony + Thank You Cards + Surveys
$18,925 in prizes
hackBCA Entry + Free Laptops (15)
Udacity Nanodegree Year Memberships (5)
Code School Year Memberships (5)
Course Horse Gift Cards (5)
Entrepreneurship Books (5)
Submitting to this hackathon could earn you:
Your group must have between 3 and 5 participants from your school.
All students must be a part of C/I's in-school or after school programs.
All students must complete an initial brainstorming activity before they arrive at the hackathon.
All students must have their permission slips upon arrival or have their teacher e-mail permission slips to Programs@weare.ci before arrival.
EACH TEAM HAS 3 DELIVERABLES
1. Something coded
- Choice #1: Your tech product (e.g. web app or mobile app). Try to make it as functonal as possible. However at a minimum, it can be a static website.
- Choice #2: A website that showcases your problem and solution and shows what your tech product would look like if you created it.
- Tools: Neocities or Mozilla Thimble for browser text editing and hosting.
2. A Complete project submission on Devpost
- Must include the url for your app / website.
- Make sure to give your team time to write your answers!
3. A 2-minute pitch presentation
4. *Bonus* 1-minute video
- Theme: "Learn. Build. Collaborate"
- Create a short (fun / creative) video about your team's experience at C/I Code Camp. What did you learn? What did you build? How did you collaborate?
- Submit the url in your Devpost submission as the "Video Demo"
YOU MUST INCLUDE YOUR PROBLEM + SOLUTION + VALIDATION IN YOUR FINAL SUBMISSIONS
(Can be included in your tech product / website, pitch, or Devpost submission)
Problem + Validation:
- Describe the problem that your team is trying to solve
- Explain why it is a problem.
- Explain the validation process that you used and the results of your validation process. (i.e. "The Syrian Crisis has harmed the lives of 5.5 million children, but only 19/20 students surveyed said they knew about it," "Eating beef is bad for the planet, but only 17/20 students surveyed said they consider this when deciding what to eat.")
Solution + Validation:
- Describe your tech solution that helps to solve your problem
- Explain why it is a good solution.
- Be very detailed while describing the features.
- Explain the results of the validation process for your solution. (i.e. "We surveyed __ people and __ people said that our website increased their interest in the problem and that they would use our tech solution to help solve it.)
- Try to make your solutions as functional as possible (The more it works, the better!). However at minimum, if your team is only able to show what the solution looks like on your website without it actually working, that is acceptable.
How to enter
All student participants will work with mentors and attend workshops in order to build a tech products that solve important teen problems.
Step 0: Attend Workshops: Learn new tools that you can implement in your product. Workshop resources:
- Team Role Cards (CPO, COO, CEO): http://bit.ly/citeamrolecards
- Slack Signup: Check your email. Join cicodecamp.slack.com
- SCRUM Board for Project Management: http://bit.ly/scrumexample
- API Suggestions: http://bit.ly/apisuggestions
- Foundation Framework Resources: http://bit.ly/introfoundation
- Javelin Board for User Testing: http://bit.ly/cijavelinboard
- Command Line + GitHub: http://bit.ly/codecampcommandline
Step 1: Identify the Problem: The problem that you choose to solve can be any problem that affects teens.
- Does the team experience the problem personally?
- Will the problem affect teens in the future?
- Is this a problem for teens in other places?
Step 2: Brainstorm Solutions: Think of tech solutions that you can implement for the problem that you identify.
- Is your solution a new web or mobile app?
- Is your solution a new website?
- Is your solution a modification or addition to an existing tech product?
- How can you add technology to any factor surrounding your problem that is NOT currently using technology?
Step 3: Research: Make sure that your solution is original and feasible by researching other technologies and apps that already exist.
- Is your solution original?
- Is your solution possible?
- If your idea already exists, how can you can make it better or add an extra feature?
Step 4: Validation:
Validate your problem by either:
- Surveying students at the hackathon if they experience that problem. If no one experiences that problem, perhaps you're not solving the right thing!
- Researching for data from reliable sources that show many people experience your problem.
- Use our C/I Validation Form (http://bit.ly/civalidationform).
Validate your solution by:
- Surveying students at the event if they would use that product. (Be prepared to present this information in your final pitch -- for example "We surveyed 40 students and over 60% said that this was a problem they experienced. Over 70% said that they would use our solution.")
- Use our C/I Validation Form (http://bit.ly/civalidationform).
Step 5: Details and Features: What special features will your product have? How will your users interact with your product? Answer all of the questions provided in your product submission and do research as you go. While thinking about your product, evaluate your idea and answer the following questions:
- Will people use your app?
- Would you use your app?
- Is there a better solution?
- Is there a better way to phrase your solution?
- Is your solution too simple (or complex)?
Step 6: Wireframes: Plan your product's layout.
Step 7: Code your Product
Step 8: Refine and Improve: Keep improving your product until final submission at 11:30am on Sunday 1/31!
Step 8: Pitch Practice: Practice what you are going to say in front of the judges! You only get 2 minutes to present, so you have to make a good impression and stand out!
Brand Developer- Touchlab & Droidcon NYC Organizer
Senior Manager- Accenture
Program Associate- HIVE Digital Media Learning Fund
Vice President- Blackrock
Potential to Create Change
Did you choose to focus on a major teen problem? Does your tech product have the potential to solve it? Is your tech product a vitamin or is it a painkiller?
How much of your coding knowledge did you implement? Did your team challenge yourselves by learning something new from your mentor or at a workshop to use in your project? Did you implement an API to make your app functional?
Is the idea original and unique, or just a copy of something that already exists? Creative solutions show a students' imagination regarding the problem and solution as well as the product features that are presented.
How well did the team present their project? Was the idea well communicated? Were the visuals engaging and appropriate? Did the team share presentation responsibilities? Was there a hook to build audience interest?