IU:TestPage

IT Product Development

• Course name: IT Product Development
• Code discipline: CSE807
• Subject area: Software Engineering

Short Description

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

Prerequisite subjects

• CSE101: Introduction to Programming
• CSE112: Software Systems Analysis and Design
• CSE122 OR CSE804 OR CSE809 OR CSE812

Prerequisite topics

• Basic programming skills.
• OOP, and software design.
• Familiarity with some development framework or technology (web or mobile)

Course Topics

Course Sections and Topics

Section	Topics within the section
From idea to MVP	Introduction to Product Development Exploring the domain: User Research and Customer Conversations Documenting Requirements: MVP and App Features Prototyping and usability testing
Development and Launch	Product backlog and iterative development Estimation Techniques, Acceptance Criteria, and Definition of Done UX/UI Design Software Engineering vs Product Management
Hypothesis-driven development	Hypothesis-driven product development Measuring a product 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

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

• 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.