Difference between revisions of "IU:TestPage"

From IU
Jump to navigation Jump to search
Tag: Manual revert
Tag: Manual revert
Line 1: Line 1:
   
  +
= Founder Project =
−
= IT Product Development =
  
−
* '''Course name''': IT Product Development
 +
* '''Course name''': Founder Project
−
* '''Code discipline''': CSE807
 +
* '''Code discipline''': Subject area: Technical Entrepreneurship
−
* '''Subject area''': S; o; f; t; w; a; r; e; ; E; n; g; i; n; e; e; r; i; n; g
 +
* '''Subject area''': T; e; c; h; n; i; c; a; l; ; E; n; t; r; e; p; r; e; n; e; u; r; s; h; i; p
   
 
== Short Description ==
  
== Short Description ==
  +
and prerequisites
−
This course has two parts: 1) building and launching a user-facing software product with the special emphasis on understanding user needs and 2) the application of data-driven product development techniques to iteratively improve the product. Students will learn how to transform an idea into software requirements through user research, prototyping and usability tests, then they will proceed to launch the MVP version of the product. In the second part of the course, the students will apply an iterative data-driven approach to developing a product, integrate event analytics, and run controlled experiments.
  
   
 
== Prerequisites ==
  
== Prerequisites ==
   
 
=== Prerequisite subjects ===
  
=== Prerequisite subjects ===
  +
* N/A
−
* CSE101: Introduction to Programming
  
−
* CSE112: Software Systems Analysis and Design
  
−
* CSE122 OR CSE804 OR CSE809 OR CSE812
  
   
 
=== Prerequisite topics ===
  
=== Prerequisite topics ===
  +
* Progress check-up, Q&A session, Critical incidents (CI) analysis, Reflection and feedback
−
* Basic programming skills.
  
  +
* Management of a startup: key issues
−
* OOP, and software design.
  
  +
* Soft and hard skills of a founder
−
* Familiarity with some development framework or technology (web or mobile)
  
   
 
== Course Topics ==
  
== Course Topics ==
Line 26: Line 24:
 
! Section !! Topics within the section
  
! Section !! Topics within the section
 
|-
  
|-
  +
| Section 1:
−
| From idea to MVP ||
 
  +
Basic ||
−
# Introduction to Product Development
  
  +
# Basic for all topics:
−
# Exploring the domain: User Research and Customer Conversations
  
  +
# Progress check-up
−
# Documenting Requirements: MVP and App Features
  
  +
# Q&A session
−
# Prototyping and usability testing
  
  +
# Critical incidents (CI) analysis
  +
# Reflection and feedback
  +
#
  +
# Main topics for the workshops:
  +
# Being an entrepreneur: challenges and advantages
  +
# How to work with a mentor
  +
# Science and entrepreneurship: synergy effect
  +
# Step by step to success: how to measure your business progress
  +
# Developing entrepreneurial thinking
  +
# Self presentation and pitching
  +
# Techniques of self-effectiveness for an entrepreneur
  +
# Business mission: creating value on the market
  +
# Planning and strategic projecting
  +
# Teambuilding
  +
# Problem-solving and flexibility in entrepreneurship
  +
# Customer relationships
  +
# “Rise and fall”: how to learn from your mistakes
  +
# Work/life balance for an entrepreneur
  +
# Where to find inspiration and to inspire others in business
 
|-
  
|-
  +
| Section 2:
−
| Development and Launch ||
 
  +
Advanced ||
−
# Product backlog and iterative development
  
  +
# Basic for all topics:
−
# Estimation Techniques, Acceptance Criteria, and Definition of Done
  
  +
# Progress check-up
−
# UX/UI Design
  
  +
# Q&A session
−
# Software Engineering vs Product Management
  
  +
# Critical incidents (CI) analysis
−
|-
  
  +
# Reflection and feedback
−
| Hypothesis-driven development ||
 
  +
#
−
# Hypothesis-driven product development
  
  +
# Main topics for the workshops:
−
# Measuring a product
  
  +
# Forming entrepreneurial identity: how to face CI effectively
−
# Controlled Experiments and A/B testing
  
  +
# Entrepreneurial strategies
  +
# Competitiveness and high professional value of a startup founder
  +
# Mentorship and advisory for a startup
  +
# Investor relationship
  +
# Community management of IT-entrepreneur
  +
# Implementation of a business model: flexibility and adaptation
  +
# Team building and human potential development
  +
# Networking: how to add and create value
  +
# Finance and money attitude of a startup founder
  +
# Client orientation
  +
# Pitch-deck design and pitching to various audiences
  +
# Startup founder as a seller
  +
# Risk-management for an IT-startup
  +
# Creating brand that matters: how to make a valuable impact
 
|}
 
|}
 
== Intended Learning Outcomes (ILOs) ==
  
== Intended Learning Outcomes (ILOs) ==
   
 
=== What is the main purpose of this course? ===
  
=== What is the main purpose of this course? ===
−
The main purpose of this course is to enable a student to go from an idea to an MVP with the focus on delivering value to the customer and building the product in a data-driven evidence-based manner.
 +
The main purpose of this course is to enable a student to progress with the development of the business project effectively dealing with a mentor and participating in workshops on main topics needed for a startup founder.
   
 
=== ILOs defined at three levels ===
  
=== ILOs defined at three levels ===
Line 52: Line 83:
 
==== Level 1: What concepts should a student know/remember/explain? ====
  
==== Level 1: What concepts should a student know/remember/explain? ====
 
By the end of the course, the students should be able to ...
  
By the end of the course, the students should be able to ...
  +
* know what is a progress check up, Critical incident, reflection in entrepreneurship,
−
* Describe the formula for stating a product idea and the importance of delivering value
  
  +
* explain main management concepts for a startup
−
* Remember the definition and main attributes of MVP
  
  +
* explain all basic elements needed for a project realization
−
* Explain what are the main principles for building an effective customer conversation
  
  +
* explain challenges and advantages of being a startup founder
−
* Describe various classification of prototypes and where each one is applied
  
  +
* know what is entrepreneurial thinking and how to develop it,
−
* State the characteristics of a DEEP product backlog
  
  +
* basic concepts of working with mentor
−
* Elaborate on the main principles of an effective UI/UX product design (hierarchy, navigation, color, discoverability, understandability)
  
−
* List the key commonalities and differences between the mentality of a software engineer and a product manager
  
−
* Explain what is hypothesis-driven development
  
−
* Describe the important aspects and elements of a controlled experiment
  
   
 
==== Level 2: What basic practical skills should a student be able to perform? ====
  
==== Level 2: What basic practical skills should a student be able to perform? ====
 
By the end of the course, the students should be able to ...
  
By the end of the course, the students should be able to ...
  +
* deal with a mentor and advisors,
−
* Formulate and assess the product ideas
  
−
* Perform market research for existing products
 +
* use scientific research in business,
  +
* measure business progress,
−
* Design effective customer conversations
  
  +
* do self presentation and pitching,
−
* Prototype UI, design and conduct usability tests
  
  +
* create a business mission,
−
* Prototype user interface
  
−
* Design and conduct usability testing
 +
* plan and do strategic projecting
  +
* team building,
−
* Populate and groom a product backlog
  
  +
* perform problem-solving and flexibility,
−
* Conduct Sprint Planning and Review
  
  +
* manage customer relationships,
−
* Choose product metrics and apply GQM
  
  +
* get right conclusions from the mistakes,
−
* Integrate a third-party Analytics tools
  
  +
* organize work/life balance,
−
* Design, run and conclude Controlled experiments
  
  +
* to inspire others in business,
  +
* face CI effectively using various entrepreneurial strategies,
  +
* provide startup and self-competitiveness,
  +
* manage with investors,
  +
* do networking and community management
  +
* pitch to different audiences,
  +
* implement client orientation to their company,
  +
* risk-management,
  +
* branding.
   
 
==== Level 3: What complex comprehensive skills should a student be able to apply in real-life scenarios? ====
  
==== Level 3: What complex comprehensive skills should a student be able to apply in real-life scenarios? ====
 
By the end of the course, the students should be able to ...
  
By the end of the course, the students should be able to ...
  +
* Check the progress of a startup, make a reflection, face with the main critical incidents for a founder
−
* Conduct user and domain research to identify user needs and possible solutions
  
  +
* Effectively deal with a mentor, participate in the student business community providing a value,
−
* Elicit and document software requirements
  
  +
* Develop a founder project systematizing all concepts and using all basic elements of startup management.
−
* Organize a software process to swiftly launch an MVP and keep improving it in an iterative manner.
  
−
* Build a data pipeline to monitor metrics based on business goals and assess product progress in regards to design changes.
  
−
* Evolve and improve a product in a data-driven evidence-based iterative manner
 
 
== Grading ==
  
== Grading ==
   
Line 121: Line 156:
   
 
=== Open access resources ===
  
=== Open access resources ===
  +
* Five insightful TED talks every startup founder should watch
−
* Jackson, Michael. "The world and the machine." ICSE '95: Proceedings of the 17th international conference on Software engineeringApril 1995 Pages 283–292,
  
−
* The Guide to Product Metrics:
 +
* How to find a mentor
  +
* How to succeed with a statup
  +
* How to build a future https://www.ycombinator.com/library/6G-how-to-build-the-future
   
 
=== Closed access resources ===
  
=== Closed access resources ===
  +
* The 23 Best Books for Startup Founders at Any Stage https://visible.vc/blog/books-for-founders/
−
* Fitzpatrick, R. (2013). The Mom Test: How to talk to customers & learn if your business is a good idea when everyone is lying to you. Robfitz Ltd.
  
−
* Reis, E. (2011). The lean startup. New York: Crown Business, 27.
  
−
* Rubin, K. S. (2012). Essential Scrum: A practical guide to the most popular Agile process. Addison-Wesley.
  
   
 
=== Software and tools used within the course ===
  
=== Software and tools used within the course ===
  +
−
* Firebase Analytics and A/B Testing, https://firebase.google.com/
  
−
* Amplitude Product Analytics, https://www.amplitude.com/
  
−
* MixPanel Product Analytics, https://mixpanel.com/
 
 
= Teaching Methodology: Methods, techniques, & activities =
  
= Teaching Methodology: Methods, techniques, & activities =
   
Line 139: Line 172:
 
|+ Teaching and Learning Methods within each section
  
|+ Teaching and Learning Methods within each section
 
|-
  
|-
−
! Teaching Techniques !! Section 1 !! Section 2 !! Section 3
 +
! Teaching Techniques !! Section 1 !! Section 2
 
|-
  
|-
−
| Problem-based learning (students learn by solving open-ended problems without a strictly-defined solution) || 1 || 1 || 1
 +
| Problem-based learning (students learn by solving open-ended problems without a strictly-defined solution) || 1 || 1
 
|-
  
|-
−
| Project-based learning (students work on a project) || 1 || 1 || 1
 +
| Project-based learning (students work on a project) || 1 || 1
 
|-
  
|-
−
| Differentiated learning (provide tasks and activities at several levels of difficulty to fit students needs and level) || 1 || 1 || 1
 +
| Contextual learning (activities and tasks are connected to the real world to make it easier for students to relate to them); || 1 || 1
 
|-
  
|-
  +
| Business game (learn by playing a game that incorporates the principles of the material covered within the course). || 1 || 1
−
| развивающего обучения (задания и материал "прокачивают" ещё нераскрытые возможности студентов); || 1 || 1 || 1
  
 
|-
  
|-
  +
| развивающего обучения (задания и материал "прокачивают" ещё нераскрытые возможности студентов); || 1 || 1
−
| концентрированного обучения (занятия по одной большой теме логически объединяются); || 1 || 1 || 1
  
 
|-
  
|-
  +
| концентрированного обучения (занятия по одной большой теме логически объединяются); || 1 || 1
−
| inquiry-based learning || 1 || 1 || 1
  
  +
|-
  +
| inquiry-based learning || 1 || 1
  +
|-
  +
| Just-in-time teaching || 1 || 1
 
|}
  
|}
 
{| class="wikitable"
  
{| class="wikitable"
 
|+ Activities within each section
  
|+ Activities within each section
 
|-
  
|-
−
! Learning Activities !! Section 1 !! Section 2 !! Section 3
 +
! Learning Activities !! Section 1 !! Section 2
 
|-
  
|-
−
| Lectures || 1 || 1 || 1
 +
| Lab exercises || 1 || 1
 
|-
  
|-
−
| Interactive Lectures || 1 || 1 || 1
 +
| Cases studies || 1 || 1
 
|-
  
|-
−
| Lab exercises || 1 || 1 || 1
 +
| Individual Projects || 1 || 1
 
|-
  
|-
  +
| Group projects || 1 || 1
−
| Development of individual parts of software product code || 1 || 1 || 1
  
 
|-
  
|-
−
| Group projects || 1 || 1 || 1
 +
| Discussions || 1 || 1
 
|-
  
|-
−
| Quizzes (written or computer based) || 1 || 1 || 1
 +
| Presentations by students || 1 || 1
 
|-
  
|-
−
| Peer Review || 1 || 1 || 1
 +
| Simulations and role-plays || 1 || 1
 
|-
  
|-
−
| Discussions || 1 || 1 || 1
 +
| Oral Reports || 1 || 1
−
|-
  
−
| Presentations by students || 1 || 1 || 1
  
−
|-
  
−
| Written reports || 1 || 1 || 1
  
−
|-
  
−
| Experiments || 0 || 0 || 1
  
 
|}
 
|}
 
== Formative Assessment and Course Activities ==
  
== Formative Assessment and Course Activities ==
Line 190: Line 221:
 
! Activity Type !! Content !! Is Graded?
  
! Activity Type !! Content !! Is Graded?
 
|-
  
|-
  +
| Individual and group reflection || Progress check-up<br>Q&A session<br>Critical incidents (CI) analysis<br>Reflection and feedback<br> || 1
−
| Quiz || 1. What is a product? What are the techniques for describing a product idea in a clear concise manner?<br>2. What user research techniques do you know? In what situations are they applied?<br>3. What are the key customer conversation principles according to the Mom Test technique? Bring an example of bad and good questions to ask.<br>4. What are the 4 phases of the requirements engineering process? <br>5. How do we document requirements? What techniques do you know? || 1
  
 
|-
  
|-
  +
| Training || Business training on the topic of the workshop with the aim to concept understanding, the skills development, knowledge systematization and practical implementation. || 0
−
| Presentation || Prepare a short 2-minutes pitch for your project idea (2-5 slides). <br><br>Suggested structure:<br>What problem you are solving:<br>- State the problem clearly in 2-3 short sentences.<br><br>Who are you solving it for:<br>- Who is your user/customer?<br>- Why will they be attracted to it?<br><br>What is your proposed solution to solve that problem:<br>- One sentence description<br>- What main feature(s) will it have? || 0
  
 
|-
  
|-
  +
| Group project || 5-minutes group pitches on the topic of the current class. <br><br><br>Suggested structure:<br>- What is the main problem a Founder can face here?<br>- What are the main techniques/instruments he can use?<br>- What are the main strategies of implementation?<br>- What is a practical value? <br>- What else can we propose?<br> || 1
−
| Individual Assignments || A1: Product Ideation and Market Research<br>Formulate 3 project ideas in the following format:<br>X helps Y to do Z – where X is your product’s name, Y is the target user, and Z is what user activity product help with.<br><br>Submit Link to Screenshot board and Feature Analysis Table:<br>- Pick and explore 5 apps similar to your idea<br>- Take screenshots along the way and collect them on a board.<br>- Make a qualitative analysis table for app features.<br><br>Prepare a short 2-minutes pitch for your project idea (2-5 slides). <br><br>Suggested structure:<br>What problem you are solving:<br>- State the problem clearly in 2-3 short sentences.<br><br>Who are you solving it for:<br>- Who is your user/customer?<br>- Why will they be attracted to it?<br><br>What is your proposed solution to solve that problem:<br>- One sentence description<br>- What main feature(s) will it have? || 1
  
 
|-
  
|-
  +
| Individual presentation || Students make presentations showing the ways of practical implementation of the business aspect that was discussed in current class into their startup. || 1
−
| Group Project Work || A2: Forming Teams and Identifying Stakeholders<br>Students are distributed into teams. <br>Meet your team <br>Discuss the idea<br>Agree on the roles<br>Setup task tracker (Trello or similar)<br>Identify 3-5 stakeholders and how to approach them<br>Compose a set of 5 most important questions you would ask from each stakeholder when interviewing them<br><br>Submit<br>A pdf with the idea description, roles distribution among the team, identified stakeholders, ways to approach them, a set of questions for each stakeholder.<br>An invite link to join your task tracker<br><br>A3: Domain Exploration and Requirements<br>User Research Process:<br>Compose the questionnaire for each stakeholder type. <br>Talk to 5-7 stakeholders.<br>Keep updating the questionnaire throughout the process<br>Compose an interview results table<br>Produce personas<br>Summarize most important learning points<br>Describe features your MVP will have (use case diagram + user story mapping)<br><br>Submit a pdf report with:<br>Personas + corresponding questionnaires<br>Interview results table (can provide a link to spreadsheet, make sure to open access)<br>Learning points summary<br>MVP features.<br><br>Optional: <br>Start implementation of the functionality you are certain about.<br><br>Assignment 4. UI design, Prototyping, MVP, and Usability Testing<br>Break down MVP features into phases and cut down the specification to implement MVP V1<br>Produce low and high fidelity designs for your product.<br>Review the phases breakdown.<br>Follow either the Prototyping or MVP path to complete the assignment.<br><br>Prototyping path:<br>Make a clickable prototype with Figma or a similar tool<br>Make 5-10 offline stakeholders use your prototype, observe them and gather feedback<br>Embed your prototype into an online usability testing tool (e.g. Maze).<br>Run an online usability test with 5-10 online stakeholders.<br>Summarize key learning points<br><br>MVP path:<br>Review your MVP phases.<br>Build MVP V1 <br>Make 5-10 offline stakeholders use your MVP, observe them and gather feedback<br>Integrate an online usability testing tool to observe user sessions (e.g. Smartlook).<br>Distribute the MVP to 5-10 online stakeholders and run an online usability test.<br>Summarize key learning points<br><br><br>Submit all of the below in one PDF:<br>Link to sketches and designs.<br>Link to your MVP/Clickable prototype.<br>Link to online usability test.<br>Names of people you conducted the tests with and which stakeholder type are they.<br>Key learning points summary.<br><br>Make sure all links are accessible/viewable. || 1
  
 
|}
 
|}
 
==== Section 2 ====
  
==== Section 2 ====
Line 204: Line 235:
 
! Activity Type !! Content !! Is Graded?
  
! Activity Type !! Content !! Is Graded?
 
|-
  
|-
  +
| Individual and group reflection || Progress check-up<br>Q&A session<br>Critical incidents (CI) analysis<br>Reflection and feedback<br> || 1
−
| Quiz || 1. What does the acronym MVP stand for? What types of MVP do you know of?<br>2. Define roles, activities, and artefacts of Scrum. What differentiates Scrum from other Agile frameworks, e.g. Kanban?<br>3. What does DEEP criteria stand for when discussing Product Backlog? Explain each of the aspects with examples.<br>4. Describe how Scrum activities are performed. Which of them are essential and which of them can vary depending on the product. || 1
  
 
|-
  
|-
  +
| Training || Business training on the topic of the workshop with the aim to concept understanding, the skills development, knowledge systematization and practical implementation. || 0
−
| Presentation || Prepare a 5-mins presentation describing your: <br>product backlog<br>sprint results<br>MVP-launch plan<br>Each team will present at the class. The assessment will be based on the presentation delivery, reasoning for decision making and asking questions and providing suggestions for other teams. || 0
  
 
|-
  
|-
  +
| Group project || 5-minutes group pitches on the topic of the current class. <br><br><br>Suggested structure:<br>- What is the main problem a Founder can face here?<br>- What are the main techniques/instruments he can use?<br>- What are the main strategies of implementation?<br>- What is a practical value? <br>- What else can we propose?<br> || 1
−
| Group Project Work || Assignment 5. Developing an MVP<br>1. Populate and groom product backlog: <br>Comply with the DEEP criteria. <br>2. Run two one-week sprints:<br>Conduct two Sprint plannings, i.e. pick the tasks for Sprint Backlog.<br>Conduct two Sprint reviews<br>Run one Sprint Retrospective<br>3. Make a launch plan and release:<br>You need to launch in the following two weeks.<br>Decide what functionality will go into the release.<br>Release your first version in Google Play.<br>Hint: Focus on a small set of features solving a specific problem for a specific user, i.e. MVP.<br>4. Prepare a 5-mins presentation describing your: <br>product backlog<br>sprint results<br>MVP-launch plan.<br>Demo for your launched MVP.<br>Each team will present at the class. The assessment will be based on the presentation delivery, reasoning for decision making and asking questions and providing suggestions for other teams.<br>5. Submit a PDF with:<br>Backlogs and Launch plan<br>Link to the launched product<br>Assignment 6. Launch your product, AC and DoD.<br>1. Improve the UX: Getting Started with the App.<br>2. Release in Google Play: Work on packaging it nicely<br>3. Design and deploy a landing page<br><br>4. Produce acceptance criteria for 3-5 most important user stories in your product.<br>5. Produce definition of done checklist<br>6. Estimate the items in your product backlog<br><br> || 1
  
 
|-
  
|-
  +
| Individual presentation || Students make presentations showing the ways of practical implementation of the business aspect that was discussed in current class into their startup. || 1
−
| Group presentation || Midterm Presentation<br>1. Prepare a midterm presentation for 10-mins in which you cover:<br>The problem you are trying to solve<br>Your users and customers (personas)<br>Your solution and it's core value proposition<br>Current state of your product<br>Clear plan for the upcoming weeks<br>Your team and distribution of responsibilities<br>Demo<br>Retrospective and learning points<br>Link to your app<br><br>Submit a pdf with:<br>Items 1, 2, 3<br>link to the presentation<br> || 0
  
−
|}
 
−
==== Section 3 ====
  
−
{| class="wikitable"
  
−
|+
 
−
|-
  
−
! Activity Type !! Content !! Is Graded?
  
−
|-
  
−
| Quiz || 1. What are common product hypotheses present? How can we formulate them as questions about our UX?<br>2. Explain what is hypothesis-driven development<br>3. Describe the important aspects and elements of a controlled experiment || 1
  
−
|-
  
−
| Presentation || Prepare a short 2-minutes pitch for your project idea (2-5 slides). <br><br>Suggested structure:<br>What problem you are solving:<br>- State the problem clearly in 2-3 short sentences.<br><br>Who are you solving it for:<br>- Who is your user/customer?<br>- Why will they be attracted to it?<br><br>What is your proposed solution to solve that problem:<br>- One sentence description<br>- What main feature(s) will it have? || 0
  
−
|-
  
−
| Group project work || Assignment 7: Development, Observation, and Product Events.<br>1. Continue with your development process:<br>- Hold sprint planning and reviews.<br>- Revisit estimations and keep track for velocity calculation.<br>- Host demos and release new versions to your users<br><br>2. Observing users:<br>- Integrate a user sessions recording tool into your product<br>- As a team: watch 100 user sessions and outline common user behavior patterns.<br>- Each team member: give product to 3 new people and observe them use it.<br><br>3. Product events:<br>Create a product events table.<br>Integrate a free analytics tool that supports events reporting (e.g. Amplitude, MixPanel).<br><br>Write and submit a report:<br>- describe user behavior patterns (main ways how people use your product).<br>- learning points from the observations<br>- add the events table.<br>- describe which analytics tool you chose and why<br><br>Assignment 8: GQM, Metrics, and Hypothesis-testing.<br>1. GQM and Metrics Dashboard<br>- Compose a GQM for your product.<br>- Identify your focus and L1 metrics<br>- Setup an Analytics Dashboard with the metrics you chose.<br>- Add the instructors to your Analytics Dashboard.<br><br>Hypothesis-testing:<br>- answer clarity and hypotheses: do users understand your product, is it easy for them to get started, and do they return?<br>- suggest product improvements to increase clarity, ease of starting and retention.<br>- based on the suggestions formulate 3 falsifiable hypotheses<br>- design a simple test to check each of them<br>- pick one test that could be conducted by observing your users<br>- conduct the test<br><br>Submit:<br>- GQM, Focus and L1 Metrics breakdown.<br>- Report on the hypothesis-testing activities<br>- Access link to the dashboard.<br>Assignment 9: Running an A/B test<br>Compose an A/B test:<br>- Design a change in your product<br>- Hypothesis: Clearly state what you expect to improve as the result of the change.<br>- Parameter and Variants: Describe both A and B variants (and other if you have more).<br>- Intended sample size.<br>- OEC: Determine the target metric to run the experiment against.<br><br>Then do one of the two options:<br>Option 1: Conduct the A/B test using a remote control and A/B testing tool (Firebase, Optimizely or like)<br><br>Option 2: Do the statistical math yourself<br>Conduct an A/B test and collect data.<br>Do the math manually using the standard Student T-test.<br><br>Submit a PDF with:<br>- the A/B test description <br>- report on how the experiment went.<br>- either screenshots from the tool or math calculations. || 1
  
 
|}
 
|}
 
=== Final assessment ===
  
=== Final assessment ===
 
'''Section 1'''
  
'''Section 1'''
 
# Grading criteria for the final project presentation:
  
# Grading criteria for the final project presentation:
  +
# The student shows his ability to measure business progress, reflect and make conclusions,
−
# Problem: short clear statement on what you are solving, and why it’s important.
  
  +
# The student can show that he can face main business critical incidents effectively using various strategies,
−
# User: should be a specific user, can start from generic and then show how you narrowed it.
  
  +
# Students show that his dealing with a mentor is productive,
−
# Solution: how do you target the problem, what were the initial assumptions/hypotheses
  
  +
# Demonstrates effective practical implementation of the following concepts/issues: implementation of scientific work into business practice, business mission, strategical projecting, team building, problem-solving and flexibility, customer relationship, work/life balance.
−
# Elicitation process: interviews, how many people, what questions you asked, what you learnt.
  
  +
# Performs good communication, pitching and presentation skills, inspired by the project, eager to develop it.
 
'''Section 2'''
  
'''Section 2'''
  +
# Grading criteria for the final project presentation:
−
# Arriving at MVP: how you chose features, describe prototyping and learning from it, when did you launch, and how it went.
  
  +
# The student shows his ability to measure business progress, reflect and make conclusions,
−
# Team and development process: how it evolved, what were the challenges, what fixes you made to keep progressing.
  
  +
# The student can show that he can face main business critical incidents effectively using various strategies,
−
# Product demo: make it clear what your current product progress is.
  
  +
# Students show that his dealing with a mentor is productive,
−
'''Section 3'''
  
  +
# Demonstrates effective practical implementation of the following concepts/issues: founder’s competitiveness and professional value, investor relationship, community management, business modeling, finance management, networking, team building and human potential management, client orientations, sales, risk-management and branding.
−
# Hypothesis-driven development: how did you verify value and understandability of your product, what were the main hypotheses you had to check through MVP.
  
  +
# Performs good communication, pitching and presentation skills, inspired by the project, eager to develop it.
−
# Measuring product: what metrics you chose, why, what funnels did you set for yourself, and what was the baseline for your MVP.
  
−
# Experimentation: What usability tests and experiments you conducted, what did you learn, how did it affect your funnels and metrics.
  
   
 
=== The retake exam ===
  
=== The retake exam ===
 
'''Section 1'''
  
'''Section 1'''
  +
−
# Grading criteria for the final project presentation:
  
−
# Problem: short clear statement on what you are solving, and why it’s important.
  
−
# User: should be a specific user, can start from generic and then show how you narrowed it.
  
−
# Solution: how do you target the problem, what were the initial assumptions/hypotheses
  
−
# Elicitation process: interviews, how many people, what questions you asked, what you learnt.
  
 
'''Section 2'''
  
'''Section 2'''
−
# Arriving at MVP: how you chose features, describe prototyping and learning from it, when did you launch, and how it went.
  
−
# Team and development process: how it evolved, what were the challenges, what fixes you made to keep progressing.
  
−
# Product demo: make it clear what your current product progress is.
  
−
'''Section 3'''
  
−
# Hypothesis-driven development: how did you verify value and understandability of your product, what were the main hypotheses you had to check through MVP.
  
−
# Measuring product: what metrics you chose, why, what funnels did you set for yourself, and what was the baseline for your MVP.
  

Revision as of 09:39, 6 July 2022

Founder Project

  • Course name: Founder Project
  • Code discipline: Subject area: Technical Entrepreneurship
  • Subject area: T; e; c; h; n; i; c; a; l;  ; E; n; t; r; e; p; r; e; n; e; u; r; s; h; i; p

Short Description

and prerequisites

Prerequisites

Prerequisite subjects

  • N/A

Prerequisite topics

  • Progress check-up, Q&A session, Critical incidents (CI) analysis, Reflection and feedback
  • Management of a startup: key issues
  • Soft and hard skills of a founder

Course Topics

Course Sections and Topics
Section Topics within the section
Section 1:

Basic ||

  1. Basic for all topics:
  2. Progress check-up
  3. Q&A session
  4. Critical incidents (CI) analysis
  5. Reflection and feedback
  7. Main topics for the workshops:
  8. Being an entrepreneur: challenges and advantages
  9. How to work with a mentor
  10. Science and entrepreneurship: synergy effect
  11. Step by step to success: how to measure your business progress
  12. Developing entrepreneurial thinking
  13. Self presentation and pitching
  14. Techniques of self-effectiveness for an entrepreneur
  15. Business mission: creating value on the market
  16. Planning and strategic projecting
  17. Teambuilding
  18. Problem-solving and flexibility in entrepreneurship
  19. Customer relationships
  20. “Rise and fall”: how to learn from your mistakes
  21. Work/life balance for an entrepreneur
  22. Where to find inspiration and to inspire others in business
Section 2: 
     Advanced ||
  1. Basic for all topics:
  2. Progress check-up
  3. Q&A session
  4. Critical incidents (CI) analysis
  5. Reflection and feedback
  7. Main topics for the workshops:
  8. Forming entrepreneurial identity: how to face CI effectively
  9. Entrepreneurial strategies
  10. Competitiveness and high professional value of a startup founder
  11. Mentorship and advisory for a startup
  12. Investor relationship
  13. Community management of IT-entrepreneur
  14. Implementation of a business model: flexibility and adaptation
  15. Team building and human potential development
  16. Networking: how to add and create value
  17. Finance and money attitude of a startup founder
  18. Client orientation
  19. Pitch-deck design and pitching to various audiences
  20. Startup founder as a seller
  21. Risk-management for an IT-startup
  22. Creating brand that matters: how to make a valuable impact

Intended Learning Outcomes (ILOs)

What is the main purpose of this course?

The main purpose of this course is to enable a student to progress with the development of the business project effectively dealing with a mentor and participating in workshops on main topics needed for a startup founder.

ILOs defined at three levels

Level 1: What concepts should a student know/remember/explain?

By the end of the course, the students should be able to ...

  • know what is a progress check up, Critical incident, reflection in entrepreneurship,
  • explain main management concepts for a startup
  • explain all basic elements needed for a project realization
  • explain challenges and advantages of being a startup founder
  • know what is entrepreneurial thinking and how to develop it,
  • basic concepts of working with mentor

Level 2: What basic practical skills should a student be able to perform?

By the end of the course, the students should be able to ...

  • deal with a mentor and advisors,
  • use scientific research in business,
  • measure business progress,
  • do self presentation and pitching,
  • create a business mission,
  • plan and do strategic projecting
  • team building,
  • perform problem-solving and flexibility,
  • manage customer relationships,
  • get right conclusions from the mistakes,
  • organize work/life balance,
  • to inspire others in business,
  • face CI effectively using various entrepreneurial strategies,
  • provide startup and self-competitiveness,
  • manage with investors,
  • do networking and community management
  • pitch to different audiences,
  • implement client orientation to their company,
  • risk-management,
  • branding.

Level 3: What complex comprehensive skills should a student be able to apply in real-life scenarios?

By the end of the course, the students should be able to ...

  • Check the progress of a startup, make a reflection, face with the main critical incidents for a founder
  • Effectively deal with a mentor, participate in the student business community providing a value,
  • Develop a founder project systematizing all concepts and using all basic elements of startup management.

Grading

Course grading range

Grade Range Description of performance
A. Excellent 90-100 -
B. Good 75-89 -
C. Satisfactory 60-74 -
D. Fail 0-59 -

Course activities and grading breakdown

Activity Type Percentage of the overall course grade
Assignment 50
Quizzes 15
Peer review 15
Demo day 20

Recommendations for students on how to succeed in the course

Participation is important. Showing up is the key to success in this course.
You will work in teams, so coordinating teamwork will be an important factor for success. This is also reflected in the peer review being a graded item.
Review lecture materials before classes to do well in quizzes.
Reading the recommended literature is optional, and will give you a deeper understanding of the material.

Resources, literature and reference materials

Open access resources

Closed access resources

Software and tools used within the course

Teaching Methodology: Methods, techniques, & activities

Activities and Teaching Methods

Teaching and Learning Methods within each section
Teaching Techniques Section 1 Section 2
Problem-based learning (students learn by solving open-ended problems without a strictly-defined solution) 1 1
Project-based learning (students work on a project) 1 1
Contextual learning (activities and tasks are connected to the real world to make it easier for students to relate to them); 1 1
Business game (learn by playing a game that incorporates the principles of the material covered within the course). 1 1
развивающего обучения (задания и материал "прокачивают" ещё нераскрытые возможности студентов); 1 1
концентрированного обучения (занятия по одной большой теме логически объединяются); 1 1
inquiry-based learning 1 1
Just-in-time teaching 1 1
Activities within each section
Learning Activities Section 1 Section 2
Lab exercises 1 1
Cases studies 1 1
Individual Projects 1 1
Group projects 1 1
Discussions 1 1
Presentations by students 1 1
Simulations and role-plays 1 1
Oral Reports 1 1

Formative Assessment and Course Activities

Ongoing performance assessment

Section 1

Activity Type Content Is Graded?
Individual and group reflection Progress check-up
Q&A session
Critical incidents (CI) analysis
Reflection and feedback
 1
Training Business training on the topic of the workshop with the aim to concept understanding, the skills development, knowledge systematization and practical implementation. 0
Group project 5-minutes group pitches on the topic of the current class.


Suggested structure:
- What is the main problem a Founder can face here?
- What are the main techniques/instruments he can use?
- What are the main strategies of implementation?
- What is a practical value?
- What else can we propose?
 1
Individual presentation Students make presentations showing the ways of practical implementation of the business aspect that was discussed in current class into their startup. 1

Section 2

Activity Type Content Is Graded?
Individual and group reflection Progress check-up
Q&A session
Critical incidents (CI) analysis
Reflection and feedback
 1
Training Business training on the topic of the workshop with the aim to concept understanding, the skills development, knowledge systematization and practical implementation. 0
Group project 5-minutes group pitches on the topic of the current class.


Suggested structure:
- What is the main problem a Founder can face here?
- What are the main techniques/instruments he can use?
- What are the main strategies of implementation?
- What is a practical value?
- What else can we propose?
 1
Individual presentation Students make presentations showing the ways of practical implementation of the business aspect that was discussed in current class into their startup. 1

Final assessment

Section 1

  1. Grading criteria for the final project presentation:
  2. The student shows his ability to measure business progress, reflect and make conclusions,
  3. The student can show that he can face main business critical incidents effectively using various strategies,
  4. Students show that his dealing with a mentor is productive,
  5. Demonstrates effective practical implementation of the following concepts/issues: implementation of scientific work into business practice, business mission, strategical projecting, team building, problem-solving and flexibility, customer relationship, work/life balance.
  6. Performs good communication, pitching and presentation skills, inspired by the project, eager to develop it.

Section 2

  1. Grading criteria for the final project presentation:
  2. The student shows his ability to measure business progress, reflect and make conclusions,
  3. The student can show that he can face main business critical incidents effectively using various strategies,
  4. Students show that his dealing with a mentor is productive,
  5. Demonstrates effective practical implementation of the following concepts/issues: founder’s competitiveness and professional value, investor relationship, community management, business modeling, finance management, networking, team building and human potential management, client orientations, sales, risk-management and branding.
  6. Performs good communication, pitching and presentation skills, inspired by the project, eager to develop it.

The retake exam

Section 1

Section 2

Retrieved from "https://eduwiki.innopolis.university/index.php?title=IU:TestPage&oldid=7079"