TU-E4100 - Startup Experience D, Lecture, 6.9.2023-30.11.2023
This course space end date is set to 30.11.2023 Search Courses: TU-E4100
Review of 1st prototype and 1st version of Framework DL: 23rd Oct 23:59
Completion requirements
This initial report lays the groundwork for future versions, so build a strong foundation. Template: 5 to 7 slides MAX that can be used as a reading deck (to be understood and used without a specific speaker to explain it). Guiding questions:
Submission required. 5 to 7 slides MAX of a reading deck presentation.
24th October we will review and give feedback for each team.
Grading: Pass / Fail
Make a submission
Due: Monday, 23 October 2023, 11:59 PM
Framework instructions:
All sections of the framework should be filled in with content even if it's preliminary. The framework should demonstrate an initial understanding of the project's components and how each component is related to one another. Try to display your creativity and your early-stage concepts in the framework. We will review this in class (no need for submission)Prototype instructions:
A prototype would need to built and tested even if it's a very basic version. It should serve as a clear purpose for testing a specific aspect of the project. The prototype and the testing should demonstrate a rationale on why it was built, what it aims to test, and how its effectiveness will be assessed. The point of this is to learn how test, know the target that you are testing, see how they are using your prototype, learn from the interactions and realize what you are doing wrong to improve on your approach next time. Remember this is not about your solution or product. This is about understanding the customers and the users. You need to submit your prototype demo ie. video, pictures, and test results via the documentation report.Documentation report:
For your first documentation report, provide clear reasoning and sources for your project's statements and claims in the framework and how you have built the prototype. Demonstrate how your data collection process was carried out. Ensure all decisions are well-founded and based on hard data. Your report documentation for prototype 1 and framework 1 should include insights into how users interact with the prototype and key learning from testing. The report should also provide some analysis of the effectiveness of the prototype and its limitations as well as plan for future development.This initial report lays the groundwork for future versions, so build a strong foundation. Template: 5 to 7 slides MAX that can be used as a reading deck (to be understood and used without a specific speaker to explain it). Guiding questions:
-Why did you build the prototype?
-What was its purpose?
-Reasoning for decisions and
statements
-Data collection methods and results
-Scientific approach to validation
and solution building
-Limitations and future developments
Submission required. 5 to 7 slides MAX of a reading deck presentation.
24th October we will review and give feedback for each team.
Grading: Pass / Fail
Canvas 1 | Pass | Fail |
---|---|---|
Each section of the framework (Problem Synthesis, Value Proposition, Impact Tracker, Shareholder Arrangement and Value Stream, Expansion Plan, Roles and Resources, Key Performance Indices) contains some content, even if it's preliminary. | Several sections of the framework are entirely blank. | |
The framework demonstrates an initial understanding of the project's components. | The framework lacks any substantial content or understanding of project components. | |
The framework includes a basic overview of how these components relate to each other. | There is no coherent connection between the different sections. | |
Creative ideas and early concepts are evident in the framework. | The framework shows no creative ideas or preliminary concepts. | |
Proto 1 | Pass | Fail |
A prototype has been built, even if it's a very basic version. | No prototype has been built. | |
The prototype serves a clear purpose for testing a specific aspect of the project. | The prototype lacks a clear purpose or connection to testing the project. | |
Documentation report 1 | Pass | Fail |
Rationale for why this prototype was built, what it aims to test, and how its effectiveness will be assessed is provided. | No rationale or explanation for why this specific prototype was created or how its effectiveness will be assessed. | |
The documentation includes insights into how users interacted with the prototype and key learnings from testing. | The documentation is entirely absent or lacks insights and key learnings. | |
Some analysis on the prototype's effectiveness and limitations is included. | There is no analysis of the prototype's effectiveness or limitations. | |
The documentation report provides a rationale and explanation for all statements and claims made in the framework. | No rationale or explanations are provided for statements and claims in the framework. | |
It provides sources for statements and claims | Statements and claims lack proper sources or supporting evidence. | |
The data is shown to have been collected via a suitable data collection method. | Data collection methods are not suitable or not shown. | |
All decisions and statements are made based on logic and rationale supported by hard data, either collected through data collection, testing, or interviews. | Decisions and statements lack logic, rationale, or supporting data. |