|Class Times||Tuesday and Thursday, 3:30 to 4:50pm|
|On-demand office Hours||http://www.calendly.com/pitosalas/ftf|
|Prerequisites||None, but Sophomore standing required|
|Homework||Daily homework assignments; major term project; team assignments. Success in this 4 credit hour course is based on the expectation that students will spend a minimum of 9 hours of study time per week in preparation for class (readings, papers, discussion sections, preparation for exams, etc.)|
The most common trap that we all fall into when we become enamored with a new product or business idea is to assume that our own personal experience and intuition is a valid measure of the likelyhood of success. At the highest level then, this course is about thinking, measuring and experimenting, before taking the leap to start implementation.
Over the semester, students will be exposed to key ideas, theories, and techniques that can be brought to bear in the earliest phase of a startup project, before funding and before implementation. The course is organized around extensive, hands-on application of these tools, where students will work in teams to drive towards a fully realized product concept, prototype, market validation and business plan.
The course takes the perspective of the ‘technical co-founder’ of a computing startup. Being a technical co-founder requires, beyond computer science and programming chops, a diverse set of other skills and perspectives.
The instructor reserves the right to make changes to this syllabus and the associated curriculum web site if he deems it necessary. Any changes will either be announced in class or through e-mail. All students are responsible for finding out about such changes. Each student must be aware that not all assignments are listed in the syllabus. Students must use their common sense and not look for loopholes in the syllabus because, ultimately, the instructor has the final say in all matters. If you are confused on any assignment, ask the instructor for clarification.
By deciding to stay in this course, you are agreeing to all parts of this syllabus. In fairness to everyone, the syllabus must apply equally to all students without exception.
The final grade in this course will reflect my assessment of your performance in the course. This includes your participation; your mastery of the key learning objectives; your demonstration this both in written form and in code (if applicable); your application of what you’ve learned to working on a team; building an interesting product; and communicating what you achieved at the end of the semester.
Individual assignments are scored and weighted (see below), and used to determine class rank which in turn is used to determnine your grade. Note that you will not get a numeric “final score”, just a final grade. I will follow the guidelines from the University Bulletin:
Throughout the semester, there will be homeworks, assigments, presentations, quizes etc., small and large. Many of them are given a mark in Latte. When something is marked, we will use a 1-100 scale, which you can interpret as follows.