Project Mentor and Helper Guide
Everyone is expected to actively participate during the hackathon to support project teams. We assign Mentor and Helper roles for project ideation & work time so that everyone – planning team and participants – know what to expect and who to ask when help is needed.
The Roles page has an overview of the Mentor and Helper roles, and this guide is to give you more ideas to help you effectively support teams in their projects.
This guide is adapted from Ocean Hackweek and the University of Washington eScience Institute Hackweek Guide.
- Project Mentors will be very active in the project ideation, pitching, and organization phase, and can even propose project ideas. Once projects get underway the priority for both Mentors and Helpers should be on enabling leadership and collaborative work by participants themselves. The project mentor shouldn’t be the center of attention.
- Monitor participation by everyone, to mitigate situations where extroverts dominate discussions or introverts don’t feel comfortable to participate. Suggest ways to rebalance participation so that everyone feels they have something to contribute.
- Provide scientific advisory support. Serve as a resource. Ideally the project will be in your broader scientific domains, but it’s not really necessary.
- Provide technical advisory support. Serve as a resource for Python, R, git/GitHub, sources of relevant data, analytical or data processing methods, etc. Help the team arrive at solutions to specific challenges.
- When you can’t help directly, help them seek help elsewhere in the ESA EarthCODE community. Link to other helpers or participants who may have relevant expertise.
- Maintain regular communication with project team via a Slack channel, in person, and through GitHub issues and PR discussions.
- Be a resource for the preparation of project presentations. Make suggestions if the team is stuck because the different strands of a project are not coming together semi cleanly.
Powerful Questions
Powerful questions are a coaching technique to help people think through what they need. They are short, open ended. Here are some that could be helpful during the hackathon:
- Where do you feel like you’re stuck?
- What has been successful?
- What is unclear or fuzzy?
- What is your next step?
- What’s one thing you can let go?
- What do you need?
- What options do you have?
Daily Standups
Each morning teams will have a short (15 minute) “standup” meeting. During these meetings, each team member is given a minute or so to briefly share 1) progress they have made on their tasks, 2) anything preventing progress, and 3) what they plan on working on next.
The goal of these “standups” is to make sure everyone has the resources and support they need to achieve their hackathon goals - it can be hard to ask for help when you’re working with a new team!
As a helper, you can lead or help facilitate these meetings by asking the questions to each team member, and ensure each person has a chance to provide their update. Listen for things another teammate, you, or another helper can do to help people get unstuck. The goal of these is not to get into the details of a problem or “solutioneering”, but to identify things to work on during project time.