I’ve been a local lead for the Space Apps community in Odesa since 2016. Each year we hosted a bootcamp for the first-timers who need help picking their challenge and planning their work and a hackathon with 100+ participants. This year I didn’t want to add another 48 hours to my already excessive screen time log, so I decided to concentrate on mentoring specific teams, and Olha’s was one of them. She did meet my (over)expectations and collected an all-female team of 6 people – designers, thinkers, data scientists, and project managers.
At first, we wanted to take on the Spot That Fire V3.0. This challenge was around for 3 years, but apparently, NASA wasn’t satisfied with the solutions provided: the teams were supposed to develop an application to detect, predict, and assess the economic impacts from wildfires by leveraging high-frequency data from a new generation of geostationary satellites, data from polar-orbiting environmental satellites, and other open-source datasets. After elaborating on the idea, the team (named Girls on Fire, no less) decided to go with the Invent Your Own Challenge category and emphasize our local issues with the wildfires. That way the girls were able to concentrate on Ukrainian specifics and create a project that would later have a chance to become a real startup.
To mentor the team, I invited the space data specialist and NASA Datanauts program alumni, Tamara Koliada – earlier I invited her to join one of my workshops for the Ukrainian State Space Agency (Космічний воркшоп: як працює data science). Tamara’s help was essential to the team’s data scientists who never dealt with NASA and ESA datasets before.
I also became a mentor myself, telling the girls everything I know about wildfire detection in Ukraine (one of my previous blog entries is dedicated to that: ).
It is an unspoken rule of the hackathons: to come unprepared. Of course, there are teams who bring an almost ready prototype to the final pitches, but I consider that unfair to those who really try and build something new in 48 hours. The Girls On Fire was unprepared in a good way. However, team composition and chemistry allowed them to work on their project in the most effective way possible. There are two keys to working remotely and under pressure:
- Realistic expectations and defining the project scope first
- Division of labour between the teammates
From her Space Apps experience, Olha was aware that the team has to simplify the solution as much as possible to get there in time. From the very beginning, each of her teammates received her task list: one was supposed to work with the mentors, one was supposed to prepare the pitch, and the others had their pieces of work planned meticulously. This approach allowed the girls to deliver everything they planned, and then some.
The Space Apps has several judging criteria. The teams get rated by creativity, innovativeness, relevance, pitch quality, and sustainability of the project. In my opinion, sustainability is the most important criteria: each team has to ask themselves, whether or not they want to work on their project in the future, and if they do, what kind of resources do they need to succeed.
With Girls On Fire, sustainability was there from the start. They knew exactly why, where, and when can their project be useful for fighting the wildfires in Ukraine. They knew who and how could implement the solution into their workflow. And most importantly, they came up with a monetization strategy, so the project would become self-sufficient. Later in December the girls will meet again and make a plan for the future of their startup.
If you would like to know more about the WTFire project by Girls On Fire team, please visit their page or click through the demo.
And if this example has inspired you to try and build something of your own, join the global Space Apps community, and participate in the next hackathon on October 2-3, 2021. Starting your first space tech project is definitely not rocket science, and if you need a mentor, I’m always there for you – just tell me about your ideas in an e-mail.