4. INTRODUCTION
§ Initiative to create openness in Government to ensure public trust and establish a system of
transparency, public participation, and collaboration (President Obama, 2009).
WHAT IS OPEN GOVERNMENT AND OPEN DATA?
The Open Data Movement is here… just search
Open data have become an
important source of digital
innovation (www.data.gov)
5. ENGAGEMENT PROCEDURES
ABOUT PURDUE IRONHACKS
Here is a short video talking about IRONHACKS
https://www.purdue.edu/opendigital/resources/videos/
6. IronHacks: Not your ordinary hackathon
Traditional ‘Hackathons’ The Purdue IronHacks
36 hrs of high energy; less creativity 3 weeks: 5x high-energy hacking + time for creativity
Proprietary code: no sharing with others Open access: shared and can build on others’ code
Mentorship during the 36 hrs;
Feedback on final solution
5 iterations: hackers get valuable technical, market,
and user feedback from experts; constant guidance
Constant physical presence and interaction
Virtual presence and communication;
hackers can work on problems when they wish
GOAL:
Facilitate entrepreneurial individuals to turn open data into digital
innovations (mash-ups) that create value for citizens.
ABOUT PURDUE IRONHACKS
8. You have to develop an interactive mash-up: A map, data visualization, interaction
forms
Components and parameters in decision support system (Guo, J., & Tokuda, T., 2010).
Generic mashup
components
ABOUT PURDUE IRONHACKS
9. TECHNOLOGY
• Has a low number of
errors (relative to the
size of the app)
• Meets minimum
technical
requirements
INFORMATION
VISUALIZATION
• Affords recognizable
interactions
• Reduces cognitive work
load (option)
• Minimal reliance on
memory
• Meets minimum user
requirements
NOVELTY
• Combine different
datasets in a novel
ways
• Move beyond
standard
visualizations
We use a rigorous and objective evaluation methodology: We used automated tools
and trained experts to assess your app
ABOUT PURDUE IRONHACKS
10. There are numerous awards and incentives
Internship
Possibilities
IronHacks
Certificate
Amazon
Giftcards
Class Credit
Mobility
Opportunity
ABOUT PURDUE IRONHACKS
13. 1. Rule #1: Commit at least one new version of your app via our social coding platform in each of
the 5 phases
2. Rule #2: Do not work in teams as IronHacks is an individual competition
3. Rule #3: During the contest, we encourage reuse and ask you to give credits to other sources;
but keep in mind: blunt copying from other sources (inside and outside the contest) is not
allowed: minimum of 50% of your code needs be your own (Purdue honor’s code)
4. Rule #4: It’s a virtual civic community and general discussions should take place via our
discussion forum
5. Rule #5: To qualify for an award you have to fill in a short IronHack survey at the beginning
and after the hack as requested by NSF and Purdue (your data will remain anonymous)
6. Rule #6: IronHacks follows the concept of openness; we will not own your code; by
participating in IronHacks you acknowledge that your software can be used by others for non-
commercial purposes if they acknowledge it (creative commons)
In the contest you have to follow our community rules and guidelines
ABOUT PURDUE IRONHACKS
14. We use a social coding platform; it will make life easier for you
• No installation process involved.
• No Git involved.
• A one-click submitting process.
• No frustration about machine used.
• More – time devoted to coding.
15. Since 2015, WE HAVE BEEN GROWING
4
2015:
Open
Pilot
2016:
Open
Pilot
2016:
In-class
2016:
In-class
2017:
Purdue,
UNAL
22 26 68
200
FUTURE DEVELOPMENT
Numbers represent participants per hack
2017
Fall
2018
Spring
Bubble represents the number of participants at the
IronHacks competition, globally.
17. 4TH phase3RD phase à2ND phase à1ST phase à
GOLD IRONHACKS EXPERIENCE
In prior hacks solution evolved into functional prototypes
18. Degly, one of the winners from the UNAL Spring 2017 competition, shares why he is
such an avid supporter of IronHacks. Click here to listen to Degly:
AWARDS AND PRIZES
https://www.youtube.com/
watch?v=jzcfpPAtIIM
20. Today, its time to launch the Purdue-UNAL IronHacks competition 2017; two groups in
software engineering I will participate
IMPACT AND IRONHACKS FUTURE
Jairo Aponte PhD
Software
Engineering I & II
Alejandro Díaz
Vecchio, Student
Ambassador
Nicolas Munera
Lecturer
21. 1-2
Nov
Check
out
scores
Scores in
at 8 pm
29-31
Oct
Work
hard, be
creative
SUBMIT:
Oct 31
6-7
Nov
Check
out
scores
Scores in
at 8 pm
8-10
Nov
Work
hard, be
creative
SUBMIT:
Nov 10
11-12
Nov
Check
out
Scores
Scores in
at 8 pm
Final winners
and Awards
Ceremony!
The IRONHACKS
Phases:
Milestones/
Metrics:
13-15
Nov
Work
hard, be
creative
SUBMIT:
Nov 15
16-17
Nov
Check
out
scores
Scores in
at 8 pm
Developers: Hacking
Phase 1
October 29– November 30October 11-28 December 1
3-5
Nov
Work
hard, be
creative
SUBMIT:
Nov 5
18-20
Nov
Work
hard,
final
push!
SUBMIT:
Nov 20
21-30
Nov
Wait…
Hacking
Phase 2
Hacking
Phase 3
Hacking
Phase 4
Hacking
Phase 5
Evaluation
Phase 1
Evaluation
Phase 2
Evaluation
Phase 3
Evaluation
Phase 4
Evaluation
Phase 5Expert Panel:
RCODI Symposium
Oct 11
Virtual classes,
tutorials, exercises
& sample projects
Post-hack survey
Nov 26
Award Ceremony
Dec 1
The program starts this Wednesday; the hack starts on October 29th
22. PURDUE – UNAL GOLD IRONHACKS
You will compete against ~35 other students; this increases the changes of winning
ONE OF THE THREE AWARDS
Subgroup 1
Subgroup 2
Subgroup 3
….
Original
pool of
participants
• 3 winners in
each group
(~35
participants)
• All the same
challenge
question
(fairness)
• Random
assignment
Platform
23. PREPARATION, TUTORIALS, NEXT STEPS
Prior to the hack, we have training sessions; how you do in those ones has no effect on
your hacking performance
Start Oct 11,
Quizz due
Oct 17
Training
Session I
Start Oct 17,
Quizz due
Oct 24
Training
Session II
Start Oct 25,
Quizz Oct. 30
Training
Session
III
Start Nov 2,
Quizz due Nov
4
Training
Session
IV
Coding:
Oct 30-
Nov 1
Evaluation:
Nov 2-3
Phase
1 Coding:
Nov 4-6
Evaluation:
Nov 7-8
Phase
2 Coding:
Nov 9-11
Evaluation:
Nov 12-13
Phase
3 Coding:
Nov 14-16
Evaluation:
Nov 17-18
Phase
4 Coding: Nov
19-21
Evaluation:
Nov 22-Dec
1
Phase
5
Dec 1
Awards
Training Schedule
Hacking Timeline
24. We offer four tutorials in the technologies and skills needed.
GOLD IRONHACKS EXPERIENCE
Tutorial Start Date Content of class/Training
1st Wednesday October 11 • Intro to HTML
• Intro to CSS
2nd Wednesday October 18 • JavaScript and JQuery
3rd Wednesday October 25 • D3.js
• Google Maps
4th Wednesday November 1 • Usability basics
• How to make data useful
25. The training will be virtual (videos, online training material, and help sessions)
GOLD IRONHACKS EXPERIENCE
26. Our process is set-up to support in an iterative development; help session take place on
Wednesdays and Thursdays from 230pm-330pm, Bogota time
Hack
Phase
1
Eval.
phase
1
Hack
Phase
2
Eval.
phase
2
Hack
Phase
3
Eval.
phase
3
Developers
UX Experts
Winners
award
ceremony
Hack
Phase
4
Eval.
phase
4
2x week: mentoring and help sessions (virtual and physical)
Tech Experts
Training
sessions
3 day hacking sessions
1x week: mentoring and help sessions (virtual and physical)
GOLD IRONHACKS EXPERIENCE
Eval.
phase
5
Hack
Phase
5
27. PREPARATION, TUTORIALS, NEXT STEPS
Please complete the following steps before October 11th
1. Go to www.ironhacks.com (Read the website) and register to the Purdue-UNAL IronHacks with
your GitHub account.
2. Fill in the survey that will open after the registration (This survey is mandatory for winning
awards).
3. Watch the presentations of the kick-off event in Purdue online (live streaming October 11, 2 pm
EST)
REMOTE IRONHACKS KICK-OFF
Link to Webex: https://goo.gl/M7yiSG
Wednesday, October 11, 2017
2:00 pm | Eastern Daylight Time (New York, GMT-04:00) | 3 hours
Meeting number: 313 954 859
Meeting password: bR6mXMNy
4. Remember: We recommend you to complete the sessions in the recommended timeframe to
make sure you are ready for the HACKING!
This is what you should do before October 11th