Difference between revisions of "IU:TestPage"

From IU
Jump to navigation Jump to search
Tag: Manual revert
Line 1: Line 1:
   
  +
= Capstone Project =
−
= IT Product Development =
  
−
* '''Course name''': IT Product Development
 +
* '''Course name''': Capstone Project
−
* '''Code discipline''': CSE807
 +
* '''Code discipline''': -
−
* '''Subject area''': Software Engineering
 +
* '''Subject area''': Subject Areas to choose from: -
   
 
== Short Description ==
  
== Short Description ==
  +
This course covers the following concepts: People Management; Processes and Project Development, Planning and Controlling.
−
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 ===
  +
* CSE113 - Logic & Discrete Maths
−
* CSE101
  
  +
* CSE201 - Mathematical Analysis I
−
* CSE112
  
  +
* CSE202 - Analytical Geometry and Linear Algebra I
−
* CSE122 or CSE804 or CSE809 or CSE812
  
  +
* CSE401 - Fundamentals of Computer Architecture
  +
* CSE101 - Introduction to Programming
  +
* CSE103 - Theoretical Computer Science
  +
* CSE203 - Mathematical Analysis II
  +
* CSE204 - Analytical Geometry and Linear Algebra II
  +
* CSE117 - Data Structures and Algorithms
  +
* CSE112 - Software System Analysis and Design
  +
* CSE801 - Software Project
  +
* CSE301 - Introduction to Artificial Intelligence
  +
* CSE206 - Probability and Statistics
  +
* CSE402 - Physics I (Mechanics)
  +
* CSE105 - Operating Systems
  +
* CSE205 - Differential Equations
  +
* CSE333 - Introduction to Optimization
  +
* CSE302 - Introduction to Machine Learning
  +
* (SD, CS, DS, AAI) CSE106 - Databases
  +
* (SD, CS, DS, AAI) CSE501 - Networks
  +
* (SD, CS) CSE502 - System and Network Administration
  +
* (SD, CS, AAI) CSE114 - Distributed and Network Programming
  +
* (AAI) CSE338 - Reinforcement Learning
  +
* (DS) CSE310 - Statistical Techniques
  +
* (DS) CSE340 - Nature Inspired Computing
  +
* (RO) CSE410 - Physics II (Electrical Engineering)
  +
* (RO) CSE403 - Control Theory
  +
* (RO) CSE408 - Theoretical Mechanics
  +
* (RO) CSE406 - Fundamental of Robotics
   
 
=== Prerequisite topics ===
  
=== Prerequisite topics ===
  +
−
* Basic programming skills.
  
−
* OOP, and software design.
  
−
* Familiarity with some development framework or technology (web or mobile)
  
   
 
== Course Topics ==
  
== Course Topics ==
Line 26: Line 50:
 
! Section !! Topics within the section
  
! Section !! Topics within the section
 
|-
  
|-
  +
| People Management, Leadership and Teamwork ||
−
| From idea to MVP ||
 
  +
# People Management Styles
−
# Introduction to Product Development
  
  +
# People management & Leadership skills
−
# Exploring the domain: User Research and Customer Conversations
  
  +
# Teamwork Tools: Trello, BitBucket, Miro, Github
−
# Documenting Requirements: MVP and App Features
  
−
# Prototyping and usability testing
  
 
|-
  
|-
−
| Development and Launch ||
+
| Project development and realization ||
  +
# Defining and measuring processes
−
# Product backlog and iterative development
  
  +
# Project Life Cycle
−
# Estimation Techniques, Acceptance Criteria, and Definition of Done
  
  +
# Project Development and Management methodology
−
# UX/UI Design
  
−
# Software Engineering vs Product Management
  
 
|-
  
|-
  +
| Planning and controlling projects ||
−
| Hypothesis-driven development ||
 
  +
# Introduction - Planning & Controlling Software Development Projects
−
# Hypothesis-driven product development
  
  +
# Work Breakdown Structures
−
# Measuring a product
  
  +
# Estimation Methods
−
# Controlled Experiments and A/B testing
  
  +
# Activity Planning
  +
# Milestone Planning
  +
# Release Planning
  +
# Tracking Reporting & Controlling
 
|}
  
|}
   
Line 47: Line 73:
   
 
=== What is the main purpose of this course? ===
  
=== What is the main purpose of this course? ===
−
What is the main goal of this course formulated in one sentence?
 +
What is the main goal of this course formulated in one sentence?
−
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 goal of this course is to enable a student to understand the phases of project development; to manage both human and computational resources through control of the development process. The main task is to combine all the knowledge obtained during the study at the university and turn it into real projects.
   
 
=== ILOs defined at three levels ===
  
=== ILOs defined at three levels ===
Line 54: Line 80:
 
==== 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 ...
  +
* List existing tools for a teamwork
−
* Describe the formula for stating a product idea and the importance of delivering value
  
  +
* Describe the skills required for people manager
−
* Remember the definition and main attributes of MVP
  
  +
* Describe the skills required for a good leader
−
* Explain what are the main principles for building an effective customer conversation
  
  +
* Explain the steps of project Life Cycle
−
* Describe various classification of prototypes and where each one is applied
  
  +
* Know how to plan and control software/hardware projects
−
* 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? ====
  
==== 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 ...
  +
* Get ideas about the work in the main structural divisions
−
* Formulate and assess the product ideas
  
  +
* Formulate the idea as a project task
−
* Perform market research for existing products
  
  +
* Set objectives and goals properly
−
* Design effective customer conversations
  
  +
* Perform the given tasks in a certain limit of time
−
* 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? ====
  
==== 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 ...
  +
* Adapt to real working conditions in various institutions and organizations
−
* Conduct user and domain research to identify user needs and possible solutions
  
  +
* Gain experience while working in teams
−
* Elicit and document software requirements
  
  +
* Organize and plan the projects
−
* 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 94: Line 107:
 
! Grade !! Range !! Description of performance
  
! Grade !! Range !! Description of performance
 
|-
  
|-
−
| A. Excellent || 90.0-100.0 || -
 +
| Pass || 60.0-100.0 || -
 
|-
  
|-
−
| B. Good || 75.0-89.0 || -
 +
| Fail || 0.0-59.0 || -
−
|-
  
−
| C. Satisfactory || 60.0-74.0 || -
  
−
|-
  
−
| D. Fail || 0.0-59.0 || -
  
 
|}
  
|}
   
Line 109: Line 118:
 
! Activity Type !! Percentage of the overall course grade
  
! Activity Type !! Percentage of the overall course grade
 
|-
  
|-
−
| Assignment || 50
 +
| Presentation || 45
−
|-
  
−
| Quizzes || 15
  
−
|-
  
−
| Peer review || 15
  
 
|-
  
|-
−
| Demo day || 20
 +
| Final Presentation || 55
 
|}
  
|}
   
 
=== Recommendations for students on how to succeed in the course ===
  
=== 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.
 +
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.
   
 
== Resources, literature and reference materials ==
  
== Resources, literature and reference materials ==
   
 
=== Open access resources ===
  
=== 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 ===
  
=== 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 ===
  
=== 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 156: Line 156:
 
|-
  
|-
 
| inquiry-based learning || 1 || 1 || 1
  
| inquiry-based learning || 1 || 1 || 1
  +
|-
  +
| Task-based learning || 1 || 1 || 1
 
|}
  
|}
 
{| class="wikitable"
  
{| class="wikitable"
Line 162: Line 164:
 
! Learning Activities !! Section 1 !! Section 2 !! Section 3
  
! Learning Activities !! Section 1 !! Section 2 !! Section 3
 
|-
  
|-
−
| Lectures || 1 || 1 || 1
 +
| Experiments || 1 || 1 || 1
 
|-
  
|-
−
| Interactive Lectures || 1 || 1 || 1
 +
| Modeling || 1 || 1 || 1
−
|-
  
−
| Lab exercises || 1 || 1 || 1
  
 
|-
  
|-
 
| Development of individual parts of software product code || 1 || 1 || 1
  
| Development of individual parts of software product code || 1 || 1 || 1
 
|-
  
|-
 
| Group projects || 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
  
| Discussions || 1 || 1 || 1
 
|-
  
|-
−
| Presentations by students || 1 || 1 || 1
 +
| Presentations by students || 1 || 1 || 0
−
|-
  
−
| Written reports || 1 || 1 || 1
  
−
|-
  
−
| Experiments || 0 || 0 || 1
  
 
|}
  
|}
   
Line 195: Line 187:
 
! Activity Type !! Content !! Is Graded?
  
! Activity Type !! Content !! Is Graded?
 
|-
  
|-
  +
| 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>What methodology are you going to apply:<br>- Shortly describe the method(-s) that could solve the problem. || 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
  
−
|-
  
−
| 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
  
−
|-
  
−
| 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
  
−
|-
  
−
| 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
  
 
|}
  
|}
   
Line 210: Line 196:
 
! Activity Type !! Content !! Is Graded?
  
! Activity Type !! Content !! Is Graded?
 
|-
  
|-
  +
| Presentation of Current Progress || Prepare a short pitch for your current project progress (5-7 slides). <br><br>Suggested structure:<br>What problem you are solving:<br>- State the problem clearly in 2-3 short sentences.<br><br>What methodology are you going to apply:<br>- Shortly describe the method(-s) that could solve the problem.<br><br>Which tasks are you performing:<br>- Shortly describe the tasks that are being solved.<br>- Describe the current problems in realization if any. || 0
−
| 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
  
−
|-
  
−
| 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 Work || Assignment 5. Launching 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. AC, DoD and Midterm Presentation<br>1. Produce acceptance criteria for 3-5 most important user stories in your product.<br>2. Produce definition of done checklist<br>3. Estimate the items in your product backlog<br>4. 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 || 1
  
 
|}
  
|}
   
Line 223: Line 205:
 
! Activity Type !! Content !! Is Graded?
  
! Activity Type !! Content !! Is Graded?
 
|-
  
|-
  +
| Presentation (Project Defense) || Prepare a 5-minutes presentation on your project. During the presentation clearly define the role and contribution of each member of a team.<br><br>Suggested structure:<br>What problem you are solving:<br>- State the problem clearly in 2-3 short sentences.<br><br>What methodology is used:<br>- Describe the method(-s) that were used to solve the problem.<br><br>What are the results:<br>- Describe what you achieved during the course. || 1
−
| 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 midterm project presentation:
 
# 1. Problem: short clear statement on what you are solving, and why it’s important.
  
# 1. Problem: short clear statement on what you are solving, and why it’s important.
  +
# 2. Methodology: clear statement of the methods to be used.
−
# 2. User: should be a specific user, can start from generic and then show how you narrowed it.
  
−
# 3. Solution: how do you target the problem, what were the initial assumptions/hypotheses
  
−
# 4. Elicitation process: interviews, how many people, what questions you asked, what you learnt.
  
 
'''Section 2'''
  
'''Section 2'''
  +
# The activity in this section is not graded. The presentation is needed only to see the current state of the project realization.
−
# 5. Arriving at MVP: how you chose features, describe prototyping and learning from it, when did you launch, and how it went.
  
−
# 6. Team and development process: how it evolved, what were the challenges, what fixes you made to keep progressing.
  
−
# 7. Product demo: make it clear what your current product progress is.
  
 
'''Section 3'''
  
'''Section 3'''
  +
# Grading criteria for the final project presentation:
−
# 7. Hypothesis-driven development: how did you verify value and understandability of your product, what were the main hypotheses you had to check through MVP.
  
  +
# 1. Problem: short clear statement on what you are solving, and why it’s important.
−
# 8. Measuring product: what metrics you chose, why, what funnels did you set for yourself, and what was the baseline for your MVP.
  
  +
# 2. Methodology: clear statement of the methods used.
−
# 9. Experimentation: What usability tests and experiments you conducted, what did you learn, how did it affect your funnels and metrics.
  
  +
# 3. Results: students provided the achieved results and can interpret them
   
 
=== The retake exam ===
  
=== The retake exam ===
 
'''Section 1'''
  
'''Section 1'''
−
# For the retake, students have to implement a product and follow the guidelines of the course. The complexity of the product can be reduced, if it is one person working on it. The grading criteria for each section are the same as for the final project presentation. There has to be a meeting before the retake itself to plan and agree on the product ideas, and to answer questions.
 +
# For the retake, students have to follow the guidelines of the course and contribute to a new project. The complexity of the product can be reduced, if it is one person working on it. The grading criteria for each section are the same as for the final project presentation. There has to be a meeting before the retake itself to plan and agree on the project content, and to answer questions.
 
'''Section 2'''
  
'''Section 2'''
   

Revision as of 11:22, 18 April 2023

Capstone Project

  • Course name: Capstone Project
  • Code discipline: -
  • Subject area: Subject Areas to choose from: -

Short Description

This course covers the following concepts: People Management; Processes and Project Development, Planning and Controlling.

Prerequisites

Prerequisite subjects

  • CSE113 - Logic & Discrete Maths
  • CSE201 - Mathematical Analysis I
  • CSE202 - Analytical Geometry and Linear Algebra I
  • CSE401 - Fundamentals of Computer Architecture
  • CSE101 - Introduction to Programming
  • CSE103 - Theoretical Computer Science
  • CSE203 - Mathematical Analysis II
  • CSE204 - Analytical Geometry and Linear Algebra II
  • CSE117 - Data Structures and Algorithms
  • CSE112 - Software System Analysis and Design
  • CSE801 - Software Project
  • CSE301 - Introduction to Artificial Intelligence
  • CSE206 - Probability and Statistics
  • CSE402 - Physics I (Mechanics)
  • CSE105 - Operating Systems
  • CSE205 - Differential Equations
  • CSE333 - Introduction to Optimization
  • CSE302 - Introduction to Machine Learning
  • (SD, CS, DS, AAI) CSE106 - Databases
  • (SD, CS, DS, AAI) CSE501 - Networks
  • (SD, CS) CSE502 - System and Network Administration
  • (SD, CS, AAI) CSE114 - Distributed and Network Programming
  • (AAI) CSE338 - Reinforcement Learning
  • (DS) CSE310 - Statistical Techniques
  • (DS) CSE340 - Nature Inspired Computing
  • (RO) CSE410 - Physics II (Electrical Engineering)
  • (RO) CSE403 - Control Theory
  • (RO) CSE408 - Theoretical Mechanics
  • (RO) CSE406 - Fundamental of Robotics

Prerequisite topics

Course Topics

Course Sections and Topics
Section Topics within the section
People Management, Leadership and Teamwork
  1. People Management Styles
  2. People management & Leadership skills
  3. Teamwork Tools: Trello, BitBucket, Miro, Github
Project development and realization
  1. Defining and measuring processes
  2. Project Life Cycle
  3. Project Development and Management methodology
Planning and controlling projects
  1. Introduction - Planning & Controlling Software Development Projects
  2. Work Breakdown Structures
  3. Estimation Methods
  4. Activity Planning
  5. Milestone Planning
  6. Release Planning
  7. Tracking Reporting & Controlling

Intended Learning Outcomes (ILOs)

What is the main purpose of this course?

What is the main goal of this course formulated in one sentence? The main goal of this course is to enable a student to understand the phases of project development; to manage both human and computational resources through control of the development process. The main task is to combine all the knowledge obtained during the study at the university and turn it into real projects.

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

  • List existing tools for a teamwork
  • Describe the skills required for people manager
  • Describe the skills required for a good leader
  • Explain the steps of project Life Cycle
  • Know how to plan and control software/hardware projects

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

  • Get ideas about the work in the main structural divisions
  • Formulate the idea as a project task
  • Set objectives and goals properly
  • Perform the given tasks in a certain limit of time

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

  • Adapt to real working conditions in various institutions and organizations
  • Gain experience while working in teams
  • Organize and plan the projects

Grading

Course grading range

Grade Range Description of performance
Pass 60.0-100.0 -
Fail 0.0-59.0 -

Course activities and grading breakdown

Activity Type Percentage of the overall course grade
Presentation 45
Final Presentation 55

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.

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 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
Task-based learning 1 1 1
Activities within each section
Learning Activities Section 1 Section 2 Section 3
Experiments 1 1 1
Modeling 1 1 1
Development of individual parts of software product code 1 1 1
Group projects 1 1 1
Discussions 1 1 1
Presentations by students 1 1 0

Formative Assessment and Course Activities

Ongoing performance assessment

Section 1

Activity Type Content Is Graded?
Presentation Prepare a short 2-minutes pitch for your project idea (2-5 slides). 

Suggested structure:
What problem you are solving:
- State the problem clearly in 2-3 short sentences.

What methodology are you going to apply:
- Shortly describe the method(-s) that could solve the problem.		 1

Section 2

Activity Type Content Is Graded?
Presentation of Current Progress Prepare a short pitch for your current project progress (5-7 slides). 

Suggested structure:
What problem you are solving:
- State the problem clearly in 2-3 short sentences.

What methodology are you going to apply:
- Shortly describe the method(-s) that could solve the problem.

Which tasks are you performing:
- Shortly describe the tasks that are being solved.
- Describe the current problems in realization if any.		 0

Section 3

Activity Type Content Is Graded?
Presentation (Project Defense) Prepare a 5-minutes presentation on your project. During the presentation clearly define the role and contribution of each member of a team.

Suggested structure:
What problem you are solving:
- State the problem clearly in 2-3 short sentences.

What methodology is used:
- Describe the method(-s) that were used to solve the problem.

What are the results:
- Describe what you achieved during the course.		 1

Final assessment

Section 1

  1. Grading criteria for the midterm project presentation:
  2. 1. Problem: short clear statement on what you are solving, and why it’s important.
  3. 2. Methodology: clear statement of the methods to be used.

Section 2

  1. The activity in this section is not graded. The presentation is needed only to see the current state of the project realization.

Section 3

  1. Grading criteria for the final project presentation:
  2. 1. Problem: short clear statement on what you are solving, and why it’s important.
  3. 2. Methodology: clear statement of the methods used.
  4. 3. Results: students provided the achieved results and can interpret them

The retake exam

Section 1

  1. For the retake, students have to follow the guidelines of the course and contribute to a new project. The complexity of the product can be reduced, if it is one person working on it. The grading criteria for each section are the same as for the final project presentation. There has to be a meeting before the retake itself to plan and agree on the project content, and to answer questions.

Section 2

Section 3

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