---
# System prepended metadata

title: Innovation Week
tags: [innovationweek, '2020', refinitiv]

---

# Innovation Week
###### tags: `refinitiv`, `2020`, `innovationweek`

[toc]


## Goals  
1. To provide a space and a time for participants to make headway on problems they are interested in.
2. For us to come to a collective understanding of the challenges from conception to delivery of a product.


## What to Submit
Each team will need to produce content which we (read: Ayla) will pull together into a project page like this sample from the London team:

**Deck Content (by Thursday, 5pm)**
* Problem (including quantifiable negative impact) 
* Solution Features & Benefits (including quantifiable commercial or efficiency gain, screenshots of solution) 
* User Profile (internal or external)
* Tech Architecture (diagram)
* Techniques Used (what and why)

**Demo Video (by Friday, 3pm)**
* Recorded demo of your solution
* Walk us through one use case end to end

**B-Reel (by Friday, 3pm)**
* Fun photos of you eating pizza
* Snapshots of a Teams Call
* Making-of-not-ready-yet screenshots of the solution


## Schedule

| Day | Time | Activity | Notes    |
| ---- | -------- |  ----------- | --- |
| **Monday**   | 10-11:30am | Pitches  | 20 minute check-ins/warmups, 10 minute briefing, 1 hour for pitches (5 minute pitch, 10 minutes for questions)  |
|    | 11:30-11:45am     |  Team Formation    |  Sanjna and Ayla |
|    | 11:45-12:00pm     |  Team Finalisation    |   |
|    | At 1pm     |  Innovation Week begins    | (woo!)  |
|    |  At 6pm    |  Building Freeze  |  Relax, enjoy your evening! |
|  **Tuesday**  |  From 9am   |  Build  |   |
|    |  11-11:30am    |  Innovation Week Office Hours (optional)  | Opportunity for questions and concerns |
|    |  2-3:30pm    |  Teams Meet Ayla  |  Each team spends half an hour with Ayla |
|    |  At 6pm    |  Building Freeze  |  Relax, enjoy your evening! |
|  **Wednesday**  |  From 9am   |  Build  |   |
|    |  11-11:30am    |  Innovation Week Office Hours (optional)  | Opportunity for questions and concerns |
|    |  2-3:30pm    |  Teams Meet Ayla  |  Each team spends half an hour with Ayla |
|    |  At 5pm    |  Movie  |  Refer to the section on Movie Options |
|  **Thursday**  |  From 9am   |  Build  |   |
|    |  11-11:30am    |  Innovation Week Office Hours (optional)  | Opportunity for questions and concerns |
|    |  2pm    |  Soft Stop |  By this point, you should be wrapping the code for your build, and nearly done with your presentation |
|    |  **By 5pm**    |  **HARD STOP**  |  Send presentations and links to prototypes to Ayla |
|    |  5-5:30pm    |  Thirsty Thursdays  | Organised by Joshua |
|  **Friday**  |  9:30-11am   |  Presentations  | 10 minutes presentation, 10 minutes QnA. Teams will present in reverse order of completed materials received by Ayla (if you submitted last, you present first.)  |
|    |  11-12pm    |  Deliberation/Voting  | See section on *Prizes* |
|    |  1-3pm    |  Documentation |  Document your code, process, and work with Ayla to collate materials that are ready to go up on Connectiv |
|    |  3pm    | Wrap-up  |  Facilitated by Swarnima |
|    |  6pm    | Innovation Week officially ends  |   |




## Operations

1. **Presentations and code must be emailed to Ayla by 5pm on Thursday.** 
2. You are allowed to reuse code, as long as you cite it.
3. Using company resources is allowed! Just remember to turn them off when not in use and at the conclusion of Innovation Week.
4. Teams must stop hacking once the time is up. However, teams are allowed to debug and make small fixes to their programs after time is up. e.g. If during demoing your hack you find a bug that breaks your application and the fix is only a few lines of code, it's okay to fix that. Making large changes or adding new features is not allowed.

### Movie Options

The team chose 25 Million Pounds

Options close at the end of the day Tuesday, we'll vote on Wednesday.

* **AlphaGo** (7.8 on imdb) *On YouTube*
    * Google's DeepMind has developed a program for playing the 3000 y.o. Go using AI. They test AlphaGo on the European champion, then March 9-15, 2016, on the top player, Lee Sedol, in a best of 5 tournament in Seoul. 
* **25 Million Pounds** (7.8 on imdb) *On YouTube*
    * It details the collapse of Barings Bank in the mid 1990s primarily by a broker called Nick Leeson, who lost £827 million ($1.3 billion) by speculating on futures contracts.
* **Trading Places** (7.5 on imdb) 
    * A snobbish investor and a wily street con artist find their positions reversed as part of a bet by two callous millionaires. 
* **The Big Short** 
* **Parasite**

### Prizes (suggestions welcome!)
Potential voting mechanism: Voting for prizes will be done collectively, with Sanjna serving as a tie-breaker vote if needed.

Serious awards: 
Airbnb experiences (inspired by Nitish/Ayla)

Fun awards:
1. Most chaotic code/docs
2. Project most likely to give tech a heart attack



### Guidelines
What makes a good innovation week project?
 - **Solve a problem**. Projects might “solve” a problem that doesn’t exist, it's important that we are all rooted in problems that make sense for us to solve! Make sure that you can foresee and explain how someone might use what you build by the end of this week.
 - **Clearly articulated**. Projects should have a clear question or problem they are trying to solve plus a reasonably specific proposed solution.
 - **Attainable**. Most projects will accomplish about 25% of what they think they can accomplish, so it's important to manage your goals to feel accomplished at the end, rather than interrupted.

Being a great team member:
* It's everyone's responsibility to ensure that others in the team feel that they are valued members within it. How to do that:
    * Checking in with team members, having frequent group catchups. No one gets left behind, but no one also is left alone to do something.
    * Making sure that everyone is clear on what they are meant to be doing
    * Make sure that everyone feels comfortable doing the work they have been asked to do
* Challenge yourself! None of us are experts in everything. This could be your time to try something new, contributing code, or ideas.

*Inspired by hackathon.guide*



## Teams
It's important for the teams to be balanced, so here's our handicapping:
* Engineering can’t be a part of the same team.

Fill in a form indicating your interest in working on a project.
 - Sanjna and Ayla set up teams.

Teams are as follows (alphabetical order):
1. **Data Squad** - Alena, Ben, Kelvin
2. **Insider Insights** - Jason, Joe, Luke, Sherry
3. **Infinite Karma** - Kai Xin, Joshua, Nitish, Regan, Sharmaine, Swarnima




## Reflection
TBD

