Coding4Integrity

Agenda (EGYPT)

Day 1 – Monday

11 October 2021
(English Session)

10:30 CET

Virtual Video Link Opened for Participants and Guests to join

11:00 CET

Opening and welcoming remarks

11:45 CET

Introduction to Coding4Integrity: the African Youth Anti-Corruption Hackathon

12:00 CET

Presentation of partner organisations, teams and rules

12:30 CET

Ask me anything session

13:00 CET

Team Formation Starts

15:00 CET

End of day report

Day 2 – Tuesday

12 October 2021

10:45 CET

Virtual Video Link Opened for Participants and Guests to join

11:00 CET

Session by Sabrine on how to use the Untap Compete Platform for Teams (Arabic session)

11:30 CET

Session by Joakim Von Scheele on how to use Cubimo Platform for Communication (English session)

12:00 CET

Ideation and Design Session by representative of Start Up Egypt (Arabic Session)

13:00 CET

Teams resume work on their ideas

16:00 CET

Debriefs by Mentors

Day 3 – Wednesday

13 October 2021

10:45 CET

Virtual Video Link Opened for Participants and Guests to join

11:00 CET

Business Development Session by Serdar Temiz, Chromaway (English session)

12:00 CET

Teams resume work on their ideas

16:00 CET

Debriefs by Mentors

Day 4 – Thursday

14 October 2021

10:45 CET

Virtual Video Link Opened for Participants and Guests to join

11:00 CET

Pitch Presentation Session by a representative of Start Up Egypt (Arabic session)

12:00 CET

Teams resume work on their ideas

16:00 CET

Debriefs by Mentors

Day 5 – Friday

15 October 2021

10:45 CET

Virtual Video Link Opened for Participants and Guests to join

11:00 CET

Introduction to Microsoft Azure by a representative of Microsoft Africa (English session)

12:00 CET

Teams resume work on their ideas

16:00 CET

Debriefs by Mentors

Day 6 – Monday

18 October 2021

10:45 CET

Virtual Video Link Opened for Participants and Guests to Join

12:00 CET

Teams resume work on their ideas

14:30 CET

Teams’ Idea Submission

15:00 CET

Introduction to Celo Development Kit by Josh Crites, Celo Labs (English session)

16:00 CET

Debriefs by Mentors

Day 7 – Tuesday

19 October 2021

11:00 CET

Submission Consideration

16:00 CET 

Submission Critique Compilation

17:00 CET 

Teams get confirmation of relevance of their ideas in their team channels

Day 8 – Wednesday

20 October 2021

11:00 CET

Coding officially commences

12:00 CET

Teams resume work on their ideas

16:00 CET

Debriefs by Mentors

Days 9 to 21

Thursday, 21 October

To

Tuesday, 2 November 2021

  • Teams continue coding and building their solutions
  • Mentors organize two sessions weekly to meet with teams
  • Mentors key in important notes on team progress in the progress report update document
  • Organizing committee gathers important data on teams progress and intervenes where necessary 

Important dates and sessions in the coding period

Technical sessions with Celo Technical Mentors

  • Every Tuesday 9:00am -10:00am San Fransisco Time
  • Every Thursday 9:00am -10:00am San Fransisco Time

(IMPORTANT) Wednesday 3 November 6:00 pm 

All teams make their final submissions on the submission platform. Teams submit their:
  • Project’s Github Repository Link
  • Pitch Deck Presentation of their Solution
  • 3-minute video demo of solution

Day 22 – Thursday

4 November 2021

10:45 CET

Virtual Video Link Opened for Participants and Guests to join

11:00 CET

Pitch Events Welcoming Session
  • Regional Focal Point welcomes team in specific region to the event
  • Shares statistics of hackathon and the various solutions developed
  • Welcomes Teams pitching to the pitching webinar stage

11:20 CET

Pitch Events Commence

  • Teams present their ideas to the awards committees in each country and various guests

16:00 CET

Award Committee Begins Judging
Award committee uses set hackathon criteria to judge teams

Days 23-25

Friday, 5 November 2021

To
Sunday 7 November 2021
  • Judging continues
  • Final winners list compiled and submitted to Vienna 

Day 26 – Monday

8 November 2021
  • Winners announced
  • Certificates sent to participants, winners, judges and mentors

11:00 CET

Opening and welcoming remarks
  • Brigitte Strobel-Shaw, Chief of the Corruption and Economic Crime Branch, UNODC
  • Representative of the Ministry of Youth and Information and Communication Technologies of Kenya
  • Representative of the Economic and Financial Crimes Commission of Nigeria
  • Representative of the Special Investigative Unit of South Africa

11:45 CET

Introduction to Coding4Integrity: the African Youth Anti-Corruption Hackathon
  • Alex Petkov, Project Associate, UNODC
  • Leonardo Paradiso, Associate Programme Officer, UNODC

12:00 CET

Presentation of partner organisations, teams and rules
  • Felix Macharia, technical consultant, UNODC
  • Representative of Microsoft Africa
  • Anca Bogdana Rusu, Partnerships, Policy and Advocacy, Celo

12:30 CET

Ask me anything session
  • Participants are welcomed to ask questions in the chat or by raising their hands in relation to the hackathon objectives and program.

13:00 CET

Team Formation Starts
  • Teams begin team formation aided by mentors

15:00 CET

End of day report

  • Mentorship lead reports to the hackathon committee on team formation statistics

13:00 CET

Teams resume work on their ideas

  • Teams separate in breakout rooms and begin working on ideas based on guidelines provided during the ideation session

16:00 CET

Debriefs by Mentors
  • Mentors check on team progress with idea formation

12:00 CET

Teams resume work on their ideas

  • Teams separate in breakout rooms and begin working on ideas based on guidelines provided during the product development session

16:00 CET

Debriefs by Mentors
  • Mentors check on team progress with product development

16:00 CET

Debriefs by Mentors

  • Mentors check on team progress with product development

12:00 CET

Teams resume work on their ideas

  • Teams separate in breakout rooms and begin working on ideas based on guidelines provided during the product development session

16:00 CET

Debriefs by Mentors

  • Mentors check on team progress with product development

12:00 CET

Teams resume work on their ideas

  • Teams separate in breakout rooms and begin working on ideas based on guidelines provided during the product development session

14:30 CET

Teams’ Idea Submission
  • Teams make a submission of their first ideas via email to the hackathon committee by this time
  • Teams also submit their official GitHub repositories where they will be adding relevant code through-out the hackathon

16:00 CET

Debriefs by Mentors

  • Mentors check on team progress with product development

11:00 CET

Submission Consideration

  • Hackathon committee members assess submissions individually and make comments

16:00 CET

Submission Critique Compilation

  • Comments from Hackathon members compiled, to be shared with teams

11:00 CET

Coding officially commences

  • Teams officially start coding in their github repositories

12:00 CET

Teams resume work on their ideas

  • Teams separate in breakout rooms and begin working on ideas based on guidelines provided during the product development session

16:00 CET

Debriefs by Mentors

  • Mentors check on team progress with product development

12:00 PM

Team Formation Starts

  • Teams begin team formation aided by mentors on the team formation channel

  • Teams once formed create their own channel for communication and for communication with mentors

2:30 PM

Teams’ Idea Submission

  • Teams make a submission of their first ideas via email to the hackathon committee by this time

  • Teams also submit their official GitHub repositories where they will be adding relevant code through-out the hackathon

10:00 AM

Pitch Events Welcoming Session

  • Regional Focal Point welcomes team in specific region to the event

  • Shares statistics of hackathon and the various solutions developed

  • Welcomes Teams pitching to the pitching webinar stage

10:20 AM

Pitch Events Commence

  • Teams present their ideas to the awards committees in each country and various guests

4:00 PM

Award Committee Begins Judging

  • Award committee uses set hackathon criteria to judge teams