What would you do with a free development team?
The next Uber or Facebook? Or do you have a non-profit that needs an MVP? Let us help you get started — Yesh. For Free!
Apply for our Real World Coding Program and show us your mockups, MVP, business plan, etc. Anything that would help us select your project over the other contestants, as we will only be able to take on a few projects.
If you get selected, we will ask you to work on a list of tickets (or issues) to define your project and guide our students through the tasks at hand. Tickets are clear, usually small, definitions regarding features of your project.
Writing tickets is something that needs a little bit of practice. They should have actionable titles, (not: The signup screen, but rather: Build the sign up screen, notice the verb in it). The description should be clear and written from the perspective of the User of your app. An example:
« Add a Like Button to Posts »
Below every Post, I see a little button that says “Like”. Next to it, there is a sentence that initially reads “0 likes”.
When I click the “Like” button, the text on it changes to “Unlike” to make sure I can’t “Like” that particular Post again.
Other Users and I see that I “Liked” it because the text of the sentence next to it changes to reflect the number of likes, e.g: “1 like” or “32 likes”.
When I click the “Like/Unlike” button, the page stays as it is. I am not leaving the page, not even to be redirected back. The changes in text on the button and the “X likes” sentence are instantly visible when I click the button.
Writing clear tickets will help to speed the process along. We will provide a short workshop/tutorial on writing tickets on an evening that you can attend to make sure that you will write great tickets.
One of our senior developers will sit down with you and the students to plan a Roadmap for the build phase. In this phase, we will decide the minimum to deliver, how to build it, and (also important!) what not to build.
The students will work on your project for one week during their course. This should give them the time to set up a basic version of your product. It might be that they will want to work on it more in a later stadium, but there is a chance that you end up with a half finished app. Especially if the Planning Phase did not go well. ;)
During the building phase, we ask you to be around as much as possible so the students can ask you questions and have their morning stand-up meetings with you. At the end of the week, there will be demos and drinks.
The week thereafter, one of our senior developers will sit down with each team to discuss how things went in a Retrospective meeting. Ideally, you will be available for that meeting too.
"Getting this team up and running was the easiest thing. So eager, enthusiastic and willing to learn. I couldn’t have imagined how much they had accomplished during this week. Delivering way above expectation. Making my vision come to life in collaboration with these students made my summer."
-Douwe Wester, LeanUp
"In the real world project; I had the pleasure to pitch an idea, which involved a slack integration with a CRM API and the guys were eager to start and started coding away. With the guidance of the teachers, they were quickly put on the right track and able to deliver a testable MVP within 5 days"
-Aik Deveneijns, LevelUp Ventures