Bc: It Product Development - Revision history

M.petrishchev: M.petrishchev moved page Bc:It Product Development to Bc: It Product Development

2022-04-18T10:53:58Z

M.petrishchev moved page Bc:It Product Development to Bc: It Product Development

← Older revision	Revision as of 10:53, 18 April 2022
(No difference)

R.akhmetzyanov: R.akhmetzyanov moved page Bc:ItProductDevelopment to Bc:It Product Development

2022-04-15T06:46:09Z

R.akhmetzyanov moved page Bc:ItProductDevelopment to Bc:It Product Development

← Older revision	Revision as of 06:46, 15 April 2022
(No difference)

R.akhmetzyanov: R.akhmetzyanov moved page BTE:ItProductDevelopment to Bc:ItProductDevelopment

2022-04-15T06:42:39Z

R.akhmetzyanov moved page BTE:ItProductDevelopment to Bc:ItProductDevelopment

← Older revision	Revision as of 06:42, 15 April 2022
(No difference)

R.sirgalina at 14:07, 12 April 2022

2022-04-12T14:07:25Z

← Older revision		Revision as of 14:07, 12 April 2022
Line 224:		Line 224:
	\| 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		\| 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 ===
		+	'''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'''
		+	# 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.
		+	# Experimentation: What usability tests and experiments you conducted, what did you learn, how did it affect your funnels and metrics.
		+
		+	=== The retake exam ===
		+	'''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'''
		+	# 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.

R.sirgalina at 14:07, 12 April 2022

2022-04-12T14:07:25Z

@@ Line 211: / Line 211: @@
 |-
 | 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
 |}

R.sirgalina at 14:07, 12 April 2022

2022-04-12T14:07:19Z

@@ Line 197: / Line 197: @@
 |-
 | 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
 |}

R.sirgalina at 14:07, 12 April 2022

2022-04-12T14:07:19Z

@@ Line 179: / Line 179: @@
 |-
 | Experiments || 0 || 0 || 1
 |}

R.sirgalina at 14:07, 12 April 2022

2022-04-12T14:07:18Z

← Older revision		Revision as of 14:07, 12 April 2022
Line 133:		Line 133:
	* Amplitude Product Analytics, https://www.amplitude.com/		* Amplitude Product Analytics, https://www.amplitude.com/
	* MixPanel Product Analytics, https://mixpanel.com/		* MixPanel Product Analytics, https://mixpanel.com/
		+	= Teaching Methodology: Methods, techniques, & activities =
		+
		+	== Activities and Teaching Methods ==
		+	{\| class="wikitable"
		+	\|+ Teaching and Learning Methods within each section
		+	\|-
		+	! Teaching Techniques !! Section 1 !! Section 2 !! Section 3
		+	\|-
		+	\| Problem-based learning (students learn by solving open-ended problems without a strictly-defined solution) \|\| 1 \|\| 1 \|\| 1
		+	\|-
		+	\| Project-based learning (students work on a project) \|\| 1 \|\| 1 \|\| 1
		+	\|-
		+	\| Differentiated learning (provide tasks and activities at several levels of difficulty to fit students needs and level) \|\| 1 \|\| 1 \|\| 1
		+	\|-
		+	\| развивающего обучения (задания и материал "прокачивают" ещё нераскрытые возможности студентов); \|\| 1 \|\| 1 \|\| 1
		+	\|-
		+	\| концентрированного обучения (занятия по одной большой теме логически объединяются); \|\| 1 \|\| 1 \|\| 1
		+	\|-
		+	\| inquiry-based learning \|\| 1 \|\| 1 \|\| 1
		+	\|}
		+	{\| class="wikitable"
		+	\|+ Activities within each section
		+	\|-
		+	! Learning Activities !! Section 1 !! Section 2 !! Section 3
		+	\|-
		+	\| Lectures \|\| 1 \|\| 1 \|\| 1
		+	\|-
		+	\| Interactive Lectures \|\| 1 \|\| 1 \|\| 1
		+	\|-
		+	\| Lab exercises \|\| 1 \|\| 1 \|\| 1
		+	\|-
		+	\| Development of individual parts of software product code \|\| 1 \|\| 1 \|\| 1
		+	\|-
		+	\| Group projects \|\| 1 \|\| 1 \|\| 1
		+	\|-
		+	\| Quizzes (written or computer based) \|\| 1 \|\| 1 \|\| 1
		+	\|-
		+	\| Peer Review \|\| 1 \|\| 1 \|\| 1
		+	\|-
		+	\| Discussions \|\| 1 \|\| 1 \|\| 1
		+	\|-
		+	\| Presentations by students \|\| 1 \|\| 1 \|\| 1
		+	\|-
		+	\| Written reports \|\| 1 \|\| 1 \|\| 1
		+	\|-
		+	\| Experiments \|\| 0 \|\| 0 \|\| 1
		+	\|}

R.sirgalina at 14:07, 12 April 2022

2022-04-12T14:07:18Z

← Older revision		Revision as of 14:07, 12 April 2022
Line 83:		Line 83:
	* Build a data pipeline to monitor metrics based on business goals and assess product progress in regards to design changes.		* 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		* Evolve and improve a product in a data-driven evidence-based iterative manner
		+	== Grading ==
		+
		+	=== Course grading range ===
		+	{\| class="wikitable"
		+	\|+
		+	\|-
		+	! 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 ===
		+	{\| class="wikitable"
		+	\|+
		+	\|-
		+	! 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.<br>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.<br>Review lecture materials before classes to do well in quizzes.<br>Reading the recommended literature is optional, and will give you a deeper understanding of the material.
		+
		+	== Resources, literature and reference materials ==
		+
		+	=== Open access resources ===
		+	* 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:
		+
		+	=== Closed access resources ===
		+	* 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 ===
		+	* Firebase Analytics and A/B Testing, https://firebase.google.com/
		+	* Amplitude Product Analytics, https://www.amplitude.com/
		+	* MixPanel Product Analytics, https://mixpanel.com/

R.sirgalina at 14:07, 12 April 2022

2022-04-12T14:07:18Z

← Older revision		Revision as of 14:07, 12 April 2022
Line 43:		Line 43:
	# Controlled Experiments and A/B testing		# Controlled Experiments and A/B testing
	\|}		\|}
		+	== Intended Learning Outcomes (ILOs) ==
		+
		+	=== 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.
		+
		+	=== 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 ...
		+	* Describe the formula for stating a product idea and the importance of delivering value
		+	* Remember the definition and main attributes of MVP
		+	* Explain what are the main principles for building an effective customer conversation
		+	* Describe various classification of prototypes and where each one is applied
		+	* State the characteristics of a DEEP product backlog
		+	* 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? ====
		+	By the end of the course, the students should be able to ...
		+	* Formulate and assess the product ideas
		+	* Perform market research for existing products
		+	* Design effective customer conversations
		+	* Prototype UI, design and conduct usability tests
		+	* Prototype user interface
		+	* Design and conduct usability testing
		+	* Populate and groom a product backlog
		+	* Conduct Sprint Planning and Review
		+	* Choose product metrics and apply GQM
		+	* Integrate a third-party Analytics tools
		+	* Design, run and conclude Controlled experiments
		+
		+	==== 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 ...
		+	* Conduct user and domain research to identify user needs and possible solutions
		+	* Elicit and document software requirements
		+	* 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