MONDAY |  TUESDAY |  WEDNESDAY |  THURSDAY |  FRIDAY

Please note:  All times shown are in Washington DC or Eastern Time (ET)

---

Monday, September 8

11:00 am – 12:00 pm | Technology Set-up Help Session
An optional session for individuals who are having trouble accessing Slack, GitHub, and GCP. Please only attend if you need support with codeathon platforms.

12:30 – 1:30 pm | Welcome & Introduction Session

• Logistical information (including MS Teams, Slack, GitHub, Cloud Access, HelpDesk Support)
• Discussion of team roles
• Overview on accessing NDARO and Pathogen Resource Data
• Event photo: Codeathon photo-mosaic 

1:30 – 5:00 pm | Team Breakout Sessions: Initial planning & work time 

• Introduce team members 
• Assign team roles:
  • Team Lead - conveys scientific objectives to team, coordinates work. 
  • Tech Lead - coordinates software installation and data acquisition, manages version control and the team’s GitHub repository, troubleshoots technical issues with tech support. 
  • Writer - ensures that all work is documented, manages GitHub README and Team Report 
  • Flex position(s) - fill(s) various roles and assume(s) responsibilities for tasks as needed. 
• Decide on initial project and work approach; Outline readme introduction; Create workflow diagram 

4:30 – 5:00 pm | Team Lead Check-in meeting
All Team Leads and the event organizers meet to discuss team management issues, opportunities for inter-team collaboration, and questions about the codeathon, in addition to a reminder (and assistance as needed) for each team to push their day's work to their Team's GitHub repo.

• We encourage you to continuously commit your progress to git and push to the team GitHub repository often. To ensure that every participant’s work is committed and shared at least once a day, we have designated the last part of each working day for committing, merging and pushing any unfinished work.  

Tuesday, September 9

11:00 am – 12:00 pm |  Engagement Session I

12:30 – 1:30 pm | Stand-ups: Teams present proposed workflows (3 minutes per team)
Share your team's plans and receive feedback from other teams.
Ideally, the team will show your GitHub ReadMe or 1 presentation slide displaying an outline of the proposed work.
Suggested topics to cover: 

• What is the overarching goal of the project?
• What data will you use?
• What is your planned workflow for the codeathon? 
• What software, app or existing code do you plan to use in your project? 
• What metrics will you use for assessing your results?

1:30 – 5:00 pm | Team Breakout Sessions: Work time 

4:30 – 5:00 pm | Writers’ meeting
Designated Team Writers and the event organizers meet to discuss best practices in documentation, including content and layout for GitHub READMEs, as well as content and materials for Stand-up & Final Presentations. 

4:50 – 5:00 pm | Reminder: Push work to GitHub! 

Wednesday, September 10   

11:00 am – 12:00 pm | Engagement Session II

12:30 – 1:30 pm | Stand-ups: Teams present progress report and gather feedback (3 minutes per team)
Report on your team's progress and describe any roadblocks you've encountered. This is an opportunity gather feedback, brainstorm solutions and share expertise across teams. 

1:00 – 5:00 pm | Team Breakout Sessions: Work time 

4:50 – 5:00 pm | Reminder: Push work to GitHub! 

Thursday, September 11  

11:00 am – 12:00 pm  | Engagement Session III

12:30 – 1:30 pm | Stand-ups: Teams present progress report and gather feedback (3 minutes per team)
Report on your team's progress and describe any roadblocks you've encountered. This is an opportunity gather feedback, brainstorm solutions and share expertise across teams. 

1:30 – 5:00 pm | Team Breakout Sessions: Work time, begin to prepare final presentation material and make sure GitHub material is in good shape

4:50 – 5:00 pm | Reminder: Push work to GitHub! 

Friday, September 12  

11:00 am – 12:00 pm | Team Breakout Sessions: Work time to finish up documentation and final presentation prep

12:30 – 3:30 pm | Final team presentations (7 minutes per team, plus Q&A)
Each team presents their codeathon project's work with suggested ideas for follow-up. Time permitting, the codeathon team will respond to 1 or 2 questions from the audience. Note, additional questions or discussions can continue to occur in chat or for codeathon participants - can be moved and continued on Slack, as appropriate.