UMSI Entrepreneurship Nancy A. Benovich Gilby Ehrenberg Director of Entrepreneurship Clinical Associate Professor  School of Information 650-539-8376 nabgilby@umich.edu 2016 Winter UMSI 363 Class #3

? Only innovations in for-profit, high tech or bio-tech are considered to be “entrepreneurial” innovations” A startup is a: human institution designed to create a new product or service under conditions of extreme uncertainty

Office Hours Prof Gilby (sign up for slots, bottom of my email or links below) Office Hours*: Prof Gilby: Tues 4-6 Engagement Center (UMSI EC) 777 North U, Above Panera Thurs 12-4:00 Engagement Center   Manav Gabhawala (W 11:30-12:30) EC manavg@umich.edu Shubham Rajora (M 12-1) EC shubhamr@umich.edu

Today Lab Work on issues with lab #2, My ToDoList Discussion Project Visionaries/Sponsor PitchOut How to describe and evaluate a business iteratively: Business Model Canvas Agile/ User Stories Quiz Team Project Progression

Terminology Classes – Objects? Methods – Functions? Variables – Instance Variables? Library – Protocol (Delegate) Application Framework – Model, View, Controller (MVC)

MVC – Model View Controller – Model? Task –Is Model Persistent? Name Desc MyToDo List

MVC – Model View Controller – Model? – Persistant MyToDo List Back end as a Service Parse

Assignment #2 (Repeat from last week) A) Plan the design, develop and test of a “To Do List” app Create a new board Trello board, set up with Backlog, Doing, Done lists. Add “User Stories” as cards to Trello in your backlog: start with these required MVP features: As a student, I want see all the work items I need to get done today. As a student, I want to add work items As a student, I want to delete work items What else in the backlog? Add at least 5 more to complete on later sprints. Move just the required features to the the Doing list, leave the rest as backlog At the end of completing Assignment 2, you will share your board with us As a <user type>, I want to <function> so that <benefit> .

Assignment #2 Plan, Build, Test The To Do app

Assignment #2 Plan, Build, Test The To Do app Step 1 Open Xcode Create a new project, call it something like MyToDo List App Choose a “Tabbed Application” = tab bar on the bottom to switch between “scenes”

Assignment #2 Build Your ToDo List App, Step 2 Run the app, so you can see what functionality Interface Builder/Cocoa Touch provides you.

Assignment #2 Build Your ToDo List App, Step 3 Open the Main.storyboard, note how the views are laid out

Assignment #2 Build Your ToDo List App, Step 4 We need to create a data structure to hold the task data (MODEL) Create a Cocoa Touch Class File, call it Task Manager as a subclass of NSObject, language is Swift

Assignment #2 Build Your ToDo List App, Step 5 The task data structure will be a simple struct. We’ll create a global variable to point to an instance of TaskManager

Assignment #2 Build Your ToDo List App, Step 6 In Main.storyboard, select the FirstViewController , go to the File Inspector Uncheck Use Auto Layout, press Disable Size Classes button

Assignment #2 Build Your ToDo List App, Step 7 Delete the junk (text) in the First View Controller and put in a Table View (NOT a TableViewController!!!) Resize the Table view to leave space for the battery bar at the top and the tab bar at the bottom.

Assignment #2 Build Your ToDo List App, Step 8 Select the First tab button, change tab button name/label/text to Tasks Change the second view tab button to Add New

Assignment #2 Build Your ToDo List App, Step 9 Need to set up a data source and a delegate for our TableView Right click the table view, the black dialog below will appear, Drag from the DataSource Outlets to FirstViewController (Tasks), the Yellow/Blue botton on the top/left Right click the table view, Drag Delegate to FirstViewController (Tasks)

Assignment #2 Build Your ToDo List App, Step 10 Need to finish setting up a data source and a delegate for our TableView by adding Delegate – usually a subview has it’s parent as a delegate to handle certain methods, and that parent view is opting in to handle those methods, if the methods are required, the parent view must override them. (add UITableViewDelegate and Open the code for FirstViewController and add UITableViewDelegate, UITableViewDataSource to the class (Do not type this, this is for reference of UITableViewDataSource, note func and optional func) Press CMD and click on UITableViewDataSource, you’ll see two methods that is not optional, we’ll need to implement it in FirstViewController .

Assignment #2 Build Your ToDo List App, Step 10 Copy the 2 methods that are func (not optional), paste them into FirstViewController(Tasks) and make them into functions. For the first function, return the number of tasks For the second function add the following:

Assignment #2 Build Your ToDo List App, Step 12 Create the Add Task View from Second View Controller Remove the junk, add a Label (Add Task), and two Text Fields and a button (Add Task). Change the place holder text to Task Name and Task Description

Assignment #2 Build Your ToDo List App, Step 13 Need to set both text fields delegate as their parent, Second View Controller as the delegate by right clicking, dragging to the top parent view.

Assignment #2 Build Your ToDo List App, Step 14 Need to finish setting up a delegate as SecondViewController Open the code for SecondViewController and add UITextFieldDelegate, Press CMD and click on UITextFieldDelegate, there are only optional methods but it gives us access to extra functions. Copy textFieldShouldReturn, make it a functions, add the follow code so the text field resigns the responder when a user presses return (and the keyboard goes away!!) Run and test

Assignment #2 Build Your ToDo List App, Step 15 Run and test, form the FirstViewController which is the task list, press the Add Task tab button. In the SecondViewController which is add task, type stuff into the text fields, hit return, the key board should go away. Note if you click outside the text views on the SecondViewController, the keyboard stays there (it should go away), button doesn’t do anything

Assignment #2 Build Your ToDo List App, Step 16 We need to get rid of the keyboards when we click in the SecondViewController. Override function touchesBegan as below , run and test. Keyboard goes away when you click outside the textfields.

Assignment #2 Build Your ToDo List App, Step 17 We now need to add the text to the task list when we press the button. That means we need to take text from the two text fields in code by making outlets for them. Call one txtTask, the other txtDesc, they will be of type UITextField

Assignment #2Build Your ToDo List App, Step 18 We now need an action for the button, control click drag, Call it buttonAddTask Add the code as below which adds the task into the task list, get rid of the keyboard with endEditing, clear out the text fields from the Add Task, then jump back to the first first to show that the task has been added.

Assignment #2 Build Your ToDo List App, Step 19 We will need to add an outlet for the tasks table view, call it tasksTable We now need to update the view when returning to to FirstViewController by overriding viewWillAppear

Assignment #2 Build Your ToDo List App, Step 20 Now run the app, add tasks, make sure the tasks list update

Assignment #2 Build Your ToDo List App, Step 20 Last feature, almost there! We need to delete an item of the task list when it is complete by swiping (click on right, drag to the left). Item should be removed from table, table updates itself. In UITableViewDelegate … commitEditingStyle (Delete), add to FirstViewController Run, add a few tasks, try to delete

Update Trello Test all the checklists on each of your user story cards. Move the all the cards to the Done list

To Get Credit for these Assignments Add Members to Trello……. nabgilby@gmail.com, manavg@umich.edu , shubhamr@umich.edu #4 Try uploading your code to github and sending me a link. If too cumbersome, zip the folder, upload to canvas, we will download, run your code using the tests on the back of each trello card

Project Visionaries/Sponsors Pitchouts

Team Project Overview Project Week: Project Week: Starts Feb 8 Through next Thurs: Submit your own ideas, reviews those that are there 2/1 Idea sponsors pitch ideas, you vote your top 3 Project Week: Project Week: Starts Feb 8 Form your team based on assignments, establish ground rules, Interviews round 1, build app scaffolding, Review Customer Development Round 1 and Potentially Pivot, Competition, sketch/wireframe Review Customer Development Round 2, Pivot, Competition 2, sketch/wireframe, Business Model Canvas Review Customer Development Round 3 Draft pitch, Dataset, backend, MVP prototype 1 KJ Affinity Diagram, final wireframe test with users All teams pitch and review, MVP prototype 2 Pitch and demo to VCs, Executives, Entrepreneurs

IMPORTANT Tradeoffs for Ideas!!!! Medical Apps have higher likely hood of getting used, can make a real difference, can have social impact! Medical Apps harder to find people to interview for customer discovery Medical Apps might have a higher likelihood for grant or seed funding Consumer apps are easier to find target users to interview, especially if they are students Consumer apps have a difficult time getting use and funding, usually need marketing ($$) and take awhile App Sponsors who can help market have a higher likelihood of getting use. FIND AN APP AREA YOU HAVE STRONG INTEREST IN LEARNING ABOUT THIS TERM, that is your responsibility!

Discussion

Business Model Canvas http://www.businessmodelcompetition.com/uploads/5/1/5/7/5157318/_5650743_orig.png

Business Model Canvas – Plain English

Value for Who?

IDEATION: Customer Development Customer Search Customer Validation Problems Solutions

Who is the FIRST target, specifically

First Target Customers, Value Hypothesis WHO For whom are we creating value? Who are our most important customers (those who have the most URGENT need!!!!) WHAT: value do we deliver to the customer? Which one of our customer’s problems are we helping to solve? Which customer needs are we satisfying? What bundles of products and services are we offering to each Customer Segment?

Gotta Luv Pyramids  Lean Startup PASSION

Design Thinking

Lean Startup General management vs. “Just Do It” Validated Learning Because startups often accidentally build something nobody wants Emphasize fast iteration and customer insight BUILD-MEASURE-LEARN Feedback loop Engine of Growth = Flywheel Strategy = Target User & Customer, Business Model, Product Roadmap, Partners, Competition Entrepreneurship IS Management Built in “failure” on the way to greatness = risk taking, adaptation

Network Effect Metcalf’s Law VALUE = (# of participants) 2

More Lean Startup NOBODY EVEN TRIED OUR PRODUCT…. Quantitative targets created motivation to engage in qualitative inquiry and guided us in the questions we asked Out of desperation we decided to talk to some potential customers…brought into the office….try this…… GUINEA PIG FARMING ZAPPOS MVP = Design thinking, get something going with the least amount of work to test the value hypothesis (tests whether a product or service really delivers value to customers once they are using it)

4 Questions of the Value Hypothesis Do target users recognize that they have the problem you are trying to solve (and is that problem urgent: in the top 3) If there was a solution, would they use it (buy it) Would they buy it from you Can you build a solution for that problem Success is learning how to solve the customer’s problem

Team Project Overview Project Week: Project Week: Starts Feb 8 Through next Thurs: Submit your own ideas, reviews those that are there 2/1 Idea sponsors pitch ideas, you vote your top 3 Project Week: Project Week: Starts Feb 8 Form your team based on assignments, establish ground rules, Interviews round 1, build app scaffolding, Review Customer Development Round 1 and Potentially Pivot, Competition, sketch/wireframe Review Customer Development Round 2, Pivot, Competition 2, sketch/wireframe, Business Model Canvas Review Customer Development Round 3 Draft pitch, Dataset, backend, MVP prototype 1 KJ Affinity Diagram, final wireframe test with users All teams pitch and review, MVP prototype 2 Pitch and demo to VCs, Executives, Entrepreneurs

Learning Outcomes Mastery: None Competency: Apply the core principles of innovation methods from Lean Startup, Customer Development, Crossing the Chasm and Agile Development in one of the following sectors: a for-profit business, non-profit, or cultural institution. Identify and develop innovation skills in Design Thinking, defining and testing a target market along with SCRUM Development from which to form and grow teams in order to achieve innovation success. Create a prototype service, product or process using the technologies or tools of their choice for a demo Create a simple prototype in Swift Adaptively apply specific methods of innovation ideation, business/product/service development, and identifying steps for preparation for for-profit or non-profit incorporation. Take a leadership role in an agile software development process as the Scrum Master or Product Owner. Literacy: User test their prototype app. Awareness: Identify pathways supported by the University of Michigan to continue developing their innovation.

Grading, Workload

Grading Getting an A+ You may earn an A+ by exceeding requirements throughout the semester. To earn this, you must have received at least 95% on the exam and have a 98% overall. You must come to class. In addition your project must be ranked in the top 3 of the class. A 94% and above B- 80% and above A- 90% and above C+ 77% and above B+ 87% and above C 70% and above B 84% and above D 60% and above

Why Bother with Agile?

Agile YOU!! Product Owner

Scrum Process

What is an Agile User Story? A user story represents a small piece of business value that a team can deliver in an iteration (Sprint). While traditional requirements (like use cases) try to be as detailed as possible, a user story is defined incrementally, in three stages: The brief description of the need The conversations that happen during backlog grooming and iteration planning to solidify the details The tests that confirm the story's satisfactory completion

User Stories INVEST Checklist Well formed user stories meet the criteria

FYI: INVEST Checklist INVEST checklist: for quickly evaluating user stories originates in an article by Bill Wake repurposed the acronym SMART (Specific, Measurable, Achievable, Relevant, Time-boxed) for tasks resulting from the technical decomposition of user stories.

Why Bother? Keep your team expressing value to the end user Avoid introducing detail too early that would prevent design options and inappropriately lock developers into one solution Avoid the appearance of false completeness and clarity Get to small enough chunks that invite negotiation and movement in the backlog Leave the technical functions (how to accomplish the user story) to developers, testers, and so on

How Do I Writer User Stories? As a <user type>, I want to <function> so that <benefit> . Examples: As a consumer, I want shopping cart functionality to easily purchase items online. As an executive, I want to generate a report to understand which departments need to improve their productivity.

User Stories BEWARE Avoid generic “user” Not all roles are end users Specify roles of who interact with the system or realize value, “consumer”, “executive”, external systems “billing system” Not all roles are end users May be useful to create aggregate roles or specialized roles Consumer = all types of roles who purchase in any time frame vs Browser = searching for information purchase not likely in this session Frequent Shopper = repeat consumer, expert user of features

User Stories, Size Matters! KISS redux = KEEP IT SMALL STUPID Small enough to be coded, test and checked for completeness to the user story within an iteration/sprint