3 minute team film

A graphical view of the information presented in https://www.youtube.com/watch?v=K-GiOtHN4FY on how to, and what, your GovHack Team video should include.

Get Started. It's Free
or sign up with your email address
Rocket clouds
3 minute team film by Mind Map: 3 minute team film

1. Which cameras?

1.1. You know how to use it

1.1.1. Smart phones

1.1.2. Digital stills cameras

1.1.3. Digital video cameras

1.1.4. Web cameras

1.1.5. Digital audio recorders

1.1.6. Screen grabbing software

1.1.6.1. QuickTime Screen Recording

1.1.6.2. GovHack Website for more examples

1.2. You can work quickly

1.3. Avoid complicated or high end gear unless you know what you're doing!

1.3.1. No pressure to use high end gear

2. Why a film?

2.1. Efficient team presentations

2.2. International audience

2.2.1. Everyone can watch

2.2.2. Simple, consistent process for judges

2.3. A fun way to record your memories!

3. Why only 3 mins?

3.1. Present your GovHack

3.1.1. With brevity

3.1.2. With clarity

3.2. Judges will stop watching at 3 mins!

4. How to prepare

4.1. Simple outline

4.1.1. It must be easy to watch and hear

4.1.2. Use a storyboard style or template

4.1.2.1. "Once upon a time..."

4.1.2.2. Hero's Journey

4.1.2.3. News at 10

4.2. Practice

4.2.1. Notes for images

4.2.1.1. Features to click

4.2.1.2. Screens to show

4.2.1.3. What and why explanation

4.2.2. Notes for voice-over

4.2.2.1. Key phrases

4.2.2.2. 30 second pitch

4.3. You don't have Lots of time

4.4. No need to be a masterpiece

4.5. Don't include

4.5.1. Things you don't have rights for

4.5.1.1. Movie soundtracks

4.5.1.2. Pop music

4.5.1.3. Photographs or drawings

4.5.1.4. Creative Commons is good

4.6. No need for a detailed script

4.7. Other tips and support for producing your Team GovHack video

4.7.1. Over the weekend

4.7.1.1. Twitter

4.7.1.1.1. @gavintapp (Aus)

4.7.1.1.2. @telling_stories (NZ)

4.7.1.2. GovHack website

4.7.1.2.1. Forums

4.7.1.2.2. Q&As

4.7.1.2.3. Watching previous years

4.7.1.3. Use this mind map

5. How to film your video

5.1. Where?

5.1.1. Simple locations are great

5.1.1.1. Relevant is best

5.1.1.1.1. Your hack

5.1.1.1.2. Your team

5.1.1.1.3. Your location

5.1.1.2. Consider or control the light

5.1.1.2.1. Natural daylight works well

5.1.1.2.2. Tungsten lamps give a nice soft light

5.1.1.2.3. Fluorescent and other lights can flicker on some cameras

5.1.1.3. Avoid distractions

5.1.1.3.1. Flashing lights

5.1.1.3.2. Lots of movement

5.1.2. Keep the camera stable!

5.1.2.1. Tripod

5.1.2.2. Desk

5.1.2.2.1. Stack of books

5.1.2.3. Chair back

5.1.2.4. Beanbag

5.1.2.5. Camera rig

5.1.2.5.1. Shoulder

5.2. Who?

5.2.1. Single presenter

5.2.1.1. Talking?

5.2.1.1.1. Recording voice overs to go over other shots

5.2.1.1.2. Recording a person talking to camera

5.2.1.2. Demo'ing

5.2.1.2.1. Over the shoulder to show using screen

5.2.1.2.2. Make others aware you're recording to avoid interruptions or loud noises

5.2.2. Group presenting

5.2.2.1. Talking?

5.2.2.1.1. One at a time!

5.2.2.1.2. Medium wide shots from waist to head

5.2.2.2. Reactions?

5.2.2.2.1. Wide from behind computer to show reactions

5.2.2.2.2. Cut to computer screens

6. What should be in the video?

6.1. Introduction

6.1.1. Team name

6.1.2. Hack name

6.1.3. Each team member name

6.1.4. Team photo or brief film clip

6.2. Record your teams progress

6.2.1. Still images

6.2.1.1. Smart phone

6.2.1.2. Timelapse

6.2.1.3. DSLR

6.2.1.4. Screen grabs

6.2.2. Short clips

6.2.2.1. Key moments

6.2.2.1.1. Whiteboard planning

6.2.2.1.2. Notable 1st's

6.2.2.1.3. Brainstorm

6.2.2.1.4. Team build

6.3. Describe your hack

6.3.1. What does it do?

6.3.1.1. What did it aim to do?

6.3.2. What data sets did you use?

6.3.2.1. Did you combine disparate ones?

6.3.2.1.1. Judges find this particularly interesting

6.3.3. What technologies did you use?

6.3.3.1. Programming languages?

6.3.3.2. Hosting?

6.3.3.3. Intersting or unique technical features?

6.3.4. Expertise used?

6.3.4.1. Design

6.3.4.1.1. User Interface

6.3.4.1.2. Visuals

6.3.4.2. Research

6.4. Demo your hack

6.4.1. What to hear?

6.4.1.1. Voice over

6.4.1.1.1. Benefits of your hack

6.4.1.1.2. What next?

6.4.1.2. Computer

6.4.1.2.1. You hack sounds

6.4.2. What to see?

6.4.2.1. Video

6.4.2.1.1. You and your team

6.4.2.1.2. Someone using your hack

6.4.2.2. Computer

6.4.2.2.1. All key features

6.4.2.2.2. Screenshots

6.4.2.2.3. Screen recordings

7. How to edit your video

7.1. Editing software

7.1.1. Simple and quick is better

7.1.1.1. Free is even better!

7.1.1.1.1. Try iMovie

7.1.1.1.2. Try Movie Maker

7.1.1.1.3. Other free or low cost edit Apps

7.1.2. Editing Apps on smartphones or tablets are fine

7.1.3. Use your storyboard to guide your edit

7.1.4. Avoid complicated or slow Apps

7.1.4.1. Renders must be quick!

7.1.4.2. All editing takes time!

7.1.5. Avoid fancy fades and edits

7.1.5.1. Unless they are vital for the story of your hack!

7.2. Hosting your video

7.2.1. Upload to an online video site

7.2.1.1. YouTube

7.2.1.2. VIMEO

7.2.1.3. Other sites

7.2.2. Leave enough time to upload!

7.2.2.1. 3 min 720 videos take about 10 mins to render

7.2.2.2. Allow another 10 mins to upload

7.2.3. Include the URL on your GovHack website form

7.3. Render resoultion

7.3.1. Avoid higher resolutions for improved post production speed

7.3.1.1. 720

7.3.1.2. 1080

7.3.1.3. 2K

7.3.1.4. 4K

7.3.1.5. 8K?

8. More information in this short film: https://www.youtube.com/watch?v=K-GiOtHN4FY

8.1. This mind map is free for anyone to share, copy, print or whatever! Enjoy it, enjoy GovHack 2015! See you at Whanganui, NZ!