ENHANCING USER EXPERIENCE THROUGH EFFICIENT PRODUCT FEATURE DEVELOPMENT WITH MOSCOW METHODOLOGY PRIORITIZATION: A CASE STUDY OF SAFEUR
Product development is an iterative process in a business to stay aligned with trends and meet both consumers and users needs. This paper aims to identify those factors and implement them within the case of Safeur’s product, particularly Lake Toba’s Boat Kit. Past product-performance indicated that...
Saved in:
Main Author: | |
---|---|
Format: | Final Project |
Language: | Indonesia |
Online Access: | https://digilib.itb.ac.id/gdl/view/84100 |
Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
Institution: | Institut Teknologi Bandung |
Language: | Indonesia |
Summary: | Product development is an iterative process in a business to stay aligned with trends and meet both consumers and users needs. This paper aims to identify those factors and implement them within the case of Safeur’s product, particularly Lake Toba’s Boat Kit. Past product-performance indicated that the product is not sufficiently engaging due to the product’s limited features, both in educational and entertaining aspects. This was a problem-solving research project, focused on identifying users’ wants and needs to enhance their overall experience. Previous studies have found various key factors in enhancing users' experience, such as social interaction and technological integration. Preliminary research was conducted to identify the baseline of those key factors based on Safeur's user experience. Preliminary results indicated these key factors as their main concern on Lake Toba’s Boat Kit: aesthetics, complexity, playability and educational value. Interviews were conducted with six different users to collect insights regarding these key factors. Furthermore these insights were validated through data triangulation from two experts and previous literature review. Six different product feature development features were developed based on collected data, then prioritized using MoSCoW methodology, diversified into Must-have, Should-have, Could-have, and Won’t-have. Two final product feature developments were selected as Must-haves, and are planned to be implemented by the end of second quarter of 2025. |
---|