CAS 4EN3: Software Entrepreneurship - Fall-Winter 2018
Announcments will be made and questions answered on the discord server set up for this course. Contact the instructor if you are not a member.
This year, we will have two streams, one for intrapreneurship, in which teams will propose and implementations within the CS Outreach program, and a second, entrepreneurship stream, in which teams will prepare for and hopefully win external pitch competitions. Teams must be accepted into the entrepreneurship stream by the end of October, but we will accept teams as early as possible. Proposals for the intrapreneurship stream must also be accepted. Anyone not part of a green-lit team will be assigned to another team, taking into account their abilities and wishes, but also the fit with the existing teams, and the scope of their projects.
Many innovations are only possible in large corporations or governments, for various reasons, and innovations must take into account the brand, reputation, history and culture of the host organization. This puts a twist on entrepreneurship, which led to the neologism intrapreneurship.
We hope that students in both streams will benefit by critiquing and being critiqued by students in the other stream.
This is a full-year course, but you only have to pay for three credits! If you have a great idea in October, there will be time to see if it pans out by April.
Issues in starting up a new software enterprise, with the focus on independent start-ups. This course will cover the technical, financial, legal and operational issues encountered by software startups. Small groups of students will take an idea and turn it into a prototype, a business plan, and a sales pitch. Lectures will cover issues from team formation to appropriate software development processes to patent protection to venture capital.
This is not a course on entrepreneurship for a general audience. We will gloss over or omit issues which are not germane to software entrepreneurship, although they are very important to entrepreneurship in general. We will assume basic knowledge and experience with software technologies and software development methodologies.
In this course you will learn how to turn an idea into a new software business. You will learn about all aspects of starting a new software venture, and be evaluated according to your ability to relate this knowledge to a business idea chosen by your team. You will get to talk to experienced software entrepreneurs who will serve as both guest speakers, and as judges. We will adjust the order of presentation to take advantage of available guest speakers.
(1) Problem Identification
(a) Idea Generation - Where do good ideas come from?
(b) Market Validation/Monetization - Will anyone pay for a solution to this problem? Is it a general solution?
(c) Can I solve this problem with software? in what time? with how many people?
(d) Novelty - Is this solution or the presentation new? Can we solve it better than other people?
(2) Disruptive Technologies - Your foot in the door.
(3) Team Formation
(a) Identifying Required Skills
(a) Finding mentors and advisors
(b) Processing advice
(c) Giving peers advice
(4) Marketing and Sales
(a) Elevator Pitch
(c) Company Website
(d) Social Networks
(f) Local communities/organizations (e.g. IF, Communitech)
(g) Trade Shows, Events
(5) Monetization - How do we make money?
(a) Software as a product.
(i) Bespoke software.
(ii) Shrinkwrap software.
(iii) Agency model (e.g., iTunes).
(iv) Platform model (e.g., Facebook).
(b) Software as a service.
(c) Software as a vehicle for advertising.
(d) Service enhanced by software.
(6) Financing - How can we afford to get started?
(a) Self-financing / Bootstrapping -
(b) Angel Financing -
(c) Venture Capital -
(d) Bank Loan -
(e) Government loans/programs.
(7) Intellectual Property
(i) ours - Can we keep others from copying our idea?
(ii) theirs - Can others prevent us from running our business, or make us pay royalties?
(b) Trade Secrets - Can we protect our idea by not telling anyone?
(c) Trade Dress.
(d)Ownership of IP (corporate vs. personal, i.e. who has the rights to it if someone leaves the company/team?)
(a) What expertise do you need and how do you get it?
(b) Do you share - a vision, - a strategy, and
(a) Legal requirements.
(b) Handling financial data.
(10) Closed / Open Source
(a) Can you charge people for services related to software you open source?
(b) Licenses: Does using Open Source software force you to work for free?
(iii) Limited Licenses.
(iv)Dual or multiple license scenarios (e.g. game companies sometimes open source the engine, but retain IP to assets for a particulargame. Redhat has some closed-source code, and maintains open and closed source Linux distributions for example.)
(11) Software Development Practices in a Startup Environment
(i) Software Product Families
(ii) The Waterfall
(iii) Agile Software Development
(iv) Live Testing
(12) Network Effects
(13) Platform Effects
(a) When should you share an idea and when should you keep it secret?
(b) Is half a revenue stream better than no revenue stream?
(15) Other legal issues.
Christopher Anand. anandc (circled a) (name of university) (country).
Office: ETB 112. (drop by, call x 21397, or check on discord)
Ethan Do. doq4 (circled a) (name of university) (country).
Office hours: by appointment.
All marks are group marks except for (1) 0 to 20 percent bonus for leadership, and (2) a -20 to 0 percent subtraction for insufficient group contribution. What is leadership? We will know it when we see it. You cannot really game these parts of the marks. You will get at least one warning if we think you are not contributing sufficiently to your group. Group marks will be evaluated on November 23, February 8, and April 26. Your mark in each category can only go up. In this way, the mark is your current progress. However, to get a positive mark in each category, you must make a reasonable first attempt by November 23, or have an approved plan for submitting that deliverable later. The dates may be delayed due to illness or unforeseen circumstances. For the Entrepreneurship Track groups: 20 - technical innovation (beyond simple application of technology) 10 - pitch deck 10 - one pager 10 - business model 10 - business plan 20 - pitch to investors 20 - pitch to potential clients — 100 For the Intrapreneurship Track groups: 10 - plan for measuring impact (e.g., math tests or teacher surveys) 30 - if good efforts have been made on five one pagers, the top three marks will be added up, otherwise the bottom three 10 - value proposition for students 10 - value proposition for teachers 10 - value proposition for parents 10 - value proposition for administration 10 - value proposition for sponsor 10 - pitch deck for organization 10 - how does this project fit into the existing program (including brand analysis) 10 - stickiness (why does this make teachers want to stick with the program, and not lose the logins; consider switching costs, halo effect) 20 - execution: does it work 10 - execution: measured impact — 100
ETB 237, Wednesdays 7pm-10pm.
Links useful in preparting pitch: how to do presentations.
Different projects will interpret Prototype in different ways. Some groups may be able to develop a working prototype, other groups will only have a UI shell capable enough to do some usability testing.
Although entrepreneurs may be invited to act as judges, course evaluation is the responsibility of the instructor, who will answer questions about how each deliverable will be evaluated in advance, and who will ensure that marking is consistent across the course.
If in doubt, ask the instructor how this applies to your work.