Please read the details of the link below completely and follow the steps specified there to submit proposals. Given the high number of requests, messages and requests submitted on Riipen will not be reviewed.

All details and questions are discussed in the document below.

Program Overview and Partnership Invitation Document

This program has been run for 19 cohorts over 7 years and with 200+ partners. We work with 30+ partners every term. We will not be able to respond to messages on Riipen. Almost all questions are answered in the document above.

Quick summary: students take this course to develop a software application (web, mobile, desktop, or AI related) for various use cases. Previous examples include:

• Specialized software for research
• Software for hospital teams, universities, non-profits
• Mobile apps for finding travelers in a specific community
• Web-based application for connecting a non-profit to volunteers

If the project information interests you, please go through the steps mentioned in the document and submit a proposal and mention "Riipen" as how you found about us.

After reviewing 300+ proposals, we have created a thorough process to streamline the process for all involved.

We will not be able to accept requests on Riipen as the proposals need to be chosen by the students when the term begins. (See timeline for details).

Students have built impressive software over the years working with partners like you.

We thank you for your partnership in advance.

Students will submit three main deliverables:

0- Project matching: Students will review the submitted proposals and choose the ones they want to be matched with. They will be introduced to the selected partners.

1- Project plan: The project plan will set the scope of the project and explain what the students aim to do and how they aim to work with the partners, and how they want to achieve it.

2- Deliverable one: Deliverable one will be the first working version of the software with minimal functionalities and limited capabilities. This is so the partner can provide feedback and guidance for the next steps.

3- Presentation to the teaching team and Partner (You): Students will present the almost final version of their software. You are welcome to attend and observe the presentations and ask any questions they may have at the end.

4- Final Deliverable: This is the final deliverable submitted to the teaching team and the partners. This deliverable may not have all the functionalities, but it supports key use cases.