Based on our experience, we realize the energy metrics needs to be considered earlier in the development, and also the team should not wait till the end to use the green tools and check for energy inefficiencies. Rather it should be done earlier so the team has time to iterate based on the assessment results and make necessary changes to reduce inefficiencies.

And based on these reflections, we revised the plan we provided for hackathon earlier.

• 09 am to 10 am: Welcome & Introduction
• 10 am to 12 pm: Overview of the Hackathon Structure and Objectives
• 12 pm to 01 pm: Lunch
• 01 pm to 02 pm: Sustainability & Software Sustainability [Workshop] 🌱🌿
• 02 pm to 04 pm: Impact Assessment using SUSAF [Workshop] 🌱🌿
• 04 pm to 05 pm: Q/A Session

• 09 am to 10 am: Challenge 1 Presentation
• 10 am to 11 am: Challenge 2 Presentation
• 11 am to 12 pm: Challenge 3 Presentation
• 12 pm to 01 pm: Lunch
• 01 pm to 02 pm: Team Formation based on challenge interests and skills
• 02 pm to 04 pm: Thinking of Rough Ideas to Solve the Challenge and how the solution would contribute to SDG
• 04 pm to 05 pm: Feedback and Mentorship based on rough ideas

• 09 am to 10 pm: How to keep Sustainability in consideration while doing Solution/ Architecture Design [Workshop]
• 10 am to 12 pm: Prototype Development (Using SUSAF as a guiding tool)
• 12 pm to 01 pm: Lunch
• 01 pm to 04 pm: Define what modules are going to be developed and define measurements metrics for them, and how that metrics can be measured
• 04 pm to 05 pm: Presentation on prototype, metrics & Feedback

• 09 am to 12 pm: Refinement based on Feedback
• 12 pm to 01 pm: Lunch
• 01 pm to 02 pm: Sustainable Practices in Software Development [Workshop] 🌱🌿
• 02 pm to 05 pm: Technologies Selection & Project Setup

• 09 am to 12 pm: Development Work
• 12 pm to 01 pm: Lunch
• 01 pm to 02 pm: One to One Team Feedback & Mentorship
• 02 pm to 05 pm: Development Work

• 09 am to 12 pm: Development Work
• 12 pm to 01 pm: Lunch
• 01 pm to 04 pm: Development
• 04 pm to 05 pm: One to One Team Feedback & Mentorship

• 09 am to 10 am: How to assess using Green tools [Workshop] 🌱🌿
• 10 am to 12 pm: Measure the modules that has been developed using green tools for energy efficiency
• 12 pm to 01 pm: Lunch
• 01 pm to 02 pm: Figure out using green tools what is causing inefficiencies (if any) and how to reduce them
• 02 pm to 4pm: Development (Make improvements to reduce the discovered inefficiencies )
• 04 pm to 05 pm: One to One Team Feedback & Mentorship

• 9 am to 12 pm: Development Work & Assessment
• 12 pm to 01 pm: Lunch
• 01 pm to 04 pm: Development Work & Assessment
• 04 pm to 05 pm: One to One Team Feedback & Mentorship

• 09 am to 12 pm: Finalizing Code Repository submissions & Demo Videos
• 12 pm to 01 pm: Lunch
• 01 pm to 05 pm: Pitching & Presentation Preparation
  • Idea to solve sustainability challenge
  • Other solutions (if available for other countries), their deficiencies and how their team solution is tackling those deficiencies
  • How the solution is contributing to SDG
  • How the team tried to stay green (e.g. following green coding practices etc.) and usage of Green Tools
  • Impact Assessment of the proposed solution in 5 dimensions & how they contributed to them
  • Future Improvements

• 09 am to 02 pm: Pitching & Presentation
• 02 pm to 03 pm: Lunch
• 03 pm to 04 pm: Result Announcement
• 04 pm to 05 pm: Closing Remarks

• 09 am to 10 am: Welcome & Introduction
• 10 am to 12 pm: Overview of the Hackathon Structure and Objectives
• 12 pm to 01 pm: Lunch
• 01 pm to 02 pm: Sustainability & Software Sustainability [Workshop] 🌱🌿
• 02 pm to 04 pm: Impact Assessment using SUSAF [Workshop] 🌱🌿
• 04 pm to 05 pm: Q/A Session

• 09 am to 10 am: Challenge 1 Presentation
• 10 am to 11 am: Challenge 2 Presentation
• 11 am to 12 pm: Challenge 3 Presentation
• 12 pm to 01 pm: Lunch
• 01 pm to 02 pm: Team Formation based on challenge interests and skills
• 02 pm to 04 pm: Thinking of Rough Ideas to Solve the Challenge and how the solution would contribute to SDG
• 04 pm to 05 pm: Feedback and Mentorship based on rough ideas

• 09 am to 10 pm: How to keep Sustainability in consideration while doing Solution/ Architecture Design [Workshop]
• 10 am to 12 pm: Prototype Development (Using SUSAF as a guiding tool)
• 12 pm to 01 pm: Lunch
• 01 pm to 04 pm: Prototype Development
• 04 pm to 05 pm: Prototype Presentation & Feedback

• 09 am to 12 pm: Prototype Refinement based on Feedback
• 12 pm to 01 pm: Lunch
• 01 pm to 02 pm: Sustainable Practices in Software Development [Workshop] 🌱🌿
• 02 pm to 05 pm: Technologies Selection & Project Setup

• 09 am to 12 pm: Development Work
• 12 pm to 01 pm: Lunch
• 01 pm to 02 pm: One to One Team Feedback & Mentorship
• 02 pm to 05 pm: Development Work

• 09 am to 12 pm: Development Work
• 12 pm to 01 pm: Lunch
• 01 pm to 04 pm: Development
• 04 pm to 05 pm: One to One Team Feedback & Mentorship

• 09 am to 12 pm: Development Work
• 12 pm to 01 pm: Lunch
• 01 pm to 04 pm: Development Work
• 04 pm to 05 pm: One to One Team Feedback & Mentorship

• 09 am to 10 am: How to assess using Green tools [Workshop] 🌱🌿
• 10 am to 12 pm: Development Work
• 12 pm to 01 pm: Lunch
• 01 pm to 04 pm: Teams do the solution assessment using Green tools
• 04 pm to 05 pm: One to One Team Feedback & Mentorship

• 09 am to 12 pm: Finalizing Code Repository submissions & Demo Videos
• 12 pm to 01 pm: Lunch
• 01 pm to 05 pm: Pitching & Presentation Preparation
  • Idea to solve sustainability challenge
  • Other solutions (if available for other countries), their deficiencies and how their team solution is tackling those deficiencies
  • How the solution is contributing to SDG
  • How the team tried to stay green (e.g. following green coding practices etc.) and usage of Green Tools
  • Impact Assessment of the proposed solution in 5 dimensions & how they contributed to them
  • Future Improvements

• 09 am to 02 pm: Pitching & Presentation
• 02 pm to 03 pm: Lunch
• 03 pm to 04 pm: Result Announcement
• 04 pm to 05 pm: Closing Remarks