Build for the Future Hackathon

Building Apps that make a difference

  • 81 Participants
  • 150,000 Invested
  • 0 Uninvested

Industries

  • Social Good

📖  RULES


1. Who can participate? 


Participation is limited to 15 teams, five teams for each of the three nonprofit organizations. Teams should be composed by members of the same OutSystems partner or customer organization. We recommend building a diverse team that covers a wide spectrum of skills - developer, tech lead, UX/UI designer, and product owner. However, teams are free to choose any other combination. We encourage participants to build diverse teams that take into account gender, region, skill levels, seniority, and more. In our experience, team diversity has many benefits, especially in a hackathon.


Teams will also have the option to add a sixth member to the group. This team member will be a recent graduate of the OutSystems Developer School, will have just completed their certification, and have at least two years of experience as a professional developer. This opportunity will give them real-life experience developing with OutSystems.


If you would like to include a new OutSystems developer let us know via [email protected]



2. Registration Rules


Each team member must use the TAIKAI platform to register as an innovator, and the team lead selected by the team will then create a Project and add their team “innovators” to the project. 

Team names should include the company name and another identifying noun. For example, an OutSystems team might use “OutSystems Geeks” or “OutSystems Warriors.” 


Each team should send the following information to [email protected] with the following information:

  1. Team information:
    • Organization or company
    • Team name
  2. Team members information:
    • Full name
    • Email address (emails should be the ones used in the OutSystems Community profile)
    • Home address (to send swag)
    • T-shirt size
  3. Let us know if you would like to include a new OutSystems developer into the team


Important: By registering for the event you agree to adhere to the code of conduct.



3. Team Selection


Once registration is closed, teams will be informed whether they are selected. Only valid registrations will be considered. For registration to be considered valid, the team must follow the instructions listed in the “Who can participate” section. Selection will be based upon two factors: 

  1. Capacity:  When we reach the goal of 15 teams, all the other registrations will be on a waiting list. 
  2. In case of excess enrollment, more than 15 teams, (in case one organization has more than one team registered) we will distribute a maximum number of teams per partner/customer and the teams will be selected upon the speed of registration (first come first served).


4. Challenge Selection 


Teams will be able to choose one of three different challenges. Each challenge is connected with a nonprofit and their specific use case. Nonprofits are from different regions; therefore, teams can choose their challenge according to their preferred nonprofit cause, challenge specifics, or geographical proximity. For more information on nonprofits and challenges they are facing, check the Nonprofits section.



5. Challenge Process


Registration for the hackathon will be open from December 3, 2020, until January 10, 2021. 


Live Hackathon Kick-off is scheduled for January 18, 2021, and all participants are invited to join. Apart from the introductions, this will be an opportunity for the nonprofits to present their challenges and requirements for the solution. Make sure at least one of your team members attends. 


Hackathon Mechanics


The hackathon will consist of 5 sprints (0-4) of approximately 1 week each:

Sprint 0 is reserved for an ideation phase.

During this week the teams will be able to connect with the nonprofit institutions and discuss the problems and possible solutions.


At the end of Sprints 1, 2, and 3, the teams will present a demo of their progress.

There will be a live final presentation at the end of Sprint 4.


After the demo of sprint 2, a pre-selection takes place, eliminating 2 of the 5 teams for each institution.


Timeline

  • Registration Ends: Jan/10
  • Official Kickoff session: Jan/18
  • Sprint 0 Ends: Jan/22
  • Sprint 1 Demo: Feb/01
  • Sprint 2 Demo: Feb/08
  • Pre-Selection Announcement: Feb/09
  • Sprint 3 Demo: Feb/15
  • Sprint 4 Live Presentation: Feb/22

Winners announcement will happen on February 25 2021. 



6. Other Events


During the hackathon Q&A sessions will be available on the following topics:

  • Architecture: Jan/27
  • UX/UI: Jan/28
  • How to make a pitch: Feb/15


7. Selection process and criteria


The final assessment of the proposed solutions will be done based on these 4 criteria (each having a weight of 25% of the final score):

  1. Applicability of the solution
    • The fit of the app developed will be assessed by the nonprofit organization’s members. This is why it is important to dedicate time at the beginning of the process to get to know them and present a demo after each sprint. 
  2. Tech quality 
    • The quality of the solution based on its technical aspects will be assessed by the OutSystems advocates and members of the product team. 
  3. UX/UI quality 
    • User experience/user interface is an important aspect of each app. OutSystems experts on UX/UI design will assess this feature of the proposed solution. 
  4. Demo quality 
    • The final day of the hackathon will be dedicated to the demo presentations where each team will be able to pitch their solution. The final presentation will be assessed by the journalist from recognised tech publications. 


8. Intellectual Property, Compliance and Solution implementation


In consideration of your participation in the Hackathon, you agree to license and contribute any and all intellectual property and other proprietary rights in and to the software, code, designs, inventions, ideas, materials, documentation, concepts, workflows and any other items you write, create, develop, provide, contribute or make available in respect of your participation in and to the Hackathon and related activities (“Works”) to the public (including OutSystems) pursuant to a permissive open source license, such as an MIT- or BSD-style license. You hereby warrant, represent and undertake that (i) the Works are entirely your own work and not the work of any third party, or if the work of any third party or if including the work of a third party, that you have a license or other sufficient rights or permission from the owner to satisfy your obligations hereunder (and have provided any permissions or acknowledgements as required) and (ii) you have the necessary rights (including from any employer or academic institution with which you are associated) to grant the rights and licenses you are granting hereunder and to otherwise comply with these Rules. You further agree that you will keep confidential all information of a confidential nature or which is proprietary to OutSystems, which is disclosed to you under or pursuant to the Hackathon, and not disclose it to any third party.