MIS 4397

Instructor

mobile application development

H. Panahi <hpanahi@uh.edu> office: MH 330C office hours: T 2:30 PM - 3:30 PM in MH 322

Grading Scale

When the decimal is greater than or equal to 0.5, the grade is rounded up to the next letter (89.49 = B, 89.5 = A). There are no exceptions. A 90-100% B 80-89% C 70-79% D 60-69%

Class

room: MH 322 meets: T 11:30 PM - 2:30 PM

Objective

You are part of a small 4 member startup and will create a mobile application for iOS or Android. Your application must be developed with a sound business model, compelling digital creative assets, and crossplatform technologies. Success in this course requires three critical components: the business model, customer validation, and execution.

Academic Dishonesty

Course Website
http://www.bauer.uh.edu/hpanahi/mobile/

Required Reading

Plagiarism and cheating are serious offenses and may be punished by failure on exam, homework or project, failure in course, and/or expulsion from the University. For more information, refer to the Academic Dishonesty policy in the Universitys Catalog. The University of Houston Academic Honesty Policy is strictly enforced by the C. T. Bauer College of Business. No violations of this policy will be tolerated in this course. A discussion of the policy is included in the University of Houston Student Handbook, http://www. uh.edu/dos/pdf/student_handbook.pdf. Students are expected to be familiar with this policy.

Running Lean, by Ash Maurya

Need for Assistance

Course Evaluation
Attendance - 15% Group - 20% 10% MVP 10% Final Product Business Team Member: 15% Lean Canvas 10% MVP and Final Presentations 10% Blog Entries 10% Problem Interviews 10% Solution Interviews 10% MVP Interviews Creative Team Member: 5% Branding 10% Landing Page 10% Wireframes 20% MVP Design 20% Final Product Design Developer Team Member: 5% Initial Features Presentation 15% Weekly Code Review 20% MVP Code 25% Final Product Code

If you have any condition, such as a physical or learning disability, which will make it difficult for you to carry out the work as outlined in this document, or which will require academic accommodations, please notify me as soon as possible. Students must register with the Center for Students with Disabilities (CSD) (telephone 713-743-5400), and present approved accommodation documentation to the instructor in a timely manner.

Announcements

Course announcements will be made at the beginning of class and on the course website. Students are expected to check the course website on a daily basis.

Group Contract

Each team member must sign a group contract which will be provided by the instructor. Failure to comply with expectations in the group contract can adversely affect a students grade.

Tentative Course Schedule

Date 8/27 Objective Course Introduction Form Teams T - Draft Initial Lean Canvas After class, read Meta-Principles, Running Lean Illustrated, and Create Your Lean Canvas T - Introduction to Titanium, Bert Grantges, Appcelerator Guest Speaker T - Continue Drafting Lean Canvas After class, read Prioritize Where to Start, Get Ready to Experiment, Get Ready to Interview Customers, and The Problem Interview B - Begin Blog Entries T - Running Lean, Ash Maurya Guest Speaker via Skype B - Begin Problem Interviews D - Begin GitHub Commits T - User Experience, Kelsey Ruger Guest Speaker B - Continue Problem Interviews D - Begin Code Review After class, read The Solution Interview, Get to Release 1.0 B - Problem Interviews Due B - Begin Solution Interviews B - Continue Solution Interviews C - Wireframes Due D - Initial Features Presentation B - Continue Solution Interviews B - Solution Interviews Due T - Prepare for MVP Presentations T - MVP Presentations B - Begin MVP Interviews C - Logos and Landing Page Due After class, read Get Ready to Measure, The MVP Interview, Validate Customer Lifecycle B - Continue MVP Interviews B - Continue MVP Interviews After class, read Dont Be a Feature Pusher, Measure Product/Market Fit, and Conclusion B - Continue MVP Interviews B - MVP Interviews Due T - Final Presentations T - Prepare for Demo Day T - Demo Day

Weekly Code Review

Each team is responsible for committing code changes to GitHub no later than Monday at 11:59 PM, Central Time. The code will be reviewed in class every Tuesday. It is expected that regular progress is made on coding every week.

Blog Entries

9/3

9/9 9/10

Written by the business team member, blog entries are due Monday evening at 11:59 PM Central Time beginning on September 9th. Each entry must be at least 300 words, and discuss the business model and its evolution throughout the semester. Team developments, pivots, feature changes, and other updates on the groups activities should be included. Blogs must be setup on WordPress.com, and URL needs to be submitted by the intiial blog entry due date (9/9 11:59PM).

Tentative MVP Requirements

9/16 9/17

Technical Sufficient technical complexity Multiple screens Pull data either locally or remotely Support iOS or Android (preferably both) Proper coding style and structure (including appropriate variable/function names) Creative Good visual design and user experience that is in accordance with Human Interface Guidelines Logo and startup screen Color scheme reflects product branding Optimized for screen Images and/or video Business Does the product solve the customers problem? Does the MVP reflect information gained through customer interviews? Does the MVP reflect the different components of the current iteration of the business model?

9/24 10/1

10/8 10/15 10/22

10/29 11/05

Demo Day

11/12 11/19 11/26 12/3

An opportunity to showcase your application to other students on the last day of class. NOTE: You should expect to budget up to $20 for a shirt for Demo Day.

B - Business Team Member C - Creative Team Member D - Developer Team Members T - Team