I believe that many product students have faced the situation of taking over the "mess" project, the UI interface of various styles, the processing logic of the eighteen bends of the mountain road, and countless hidden pits. Some projects are category email list so complicated that we need to category email list investigate for days or even weeks for every small change we make, but online bugs are still inevitable. And what the author wants to share with you today is another scene in the process – the multi-national team refactoring together. There are both sadness and joy, but the most important thing is to gain valuable cross-team, cross-country and cross-cultural project cooperation experience.
Hope to give you some inspiration. The product of the author's project is a merchant-side app that provides services such as offline transactions, merchant/store self-service, and viewing sales and commission reports for large, medium, and small merchants category email list that cooperate with the company. The back-end mainly connects category email list with the company's core data system. The initial version of the app was made by a Czech outsourcing company and had only a few simple functions. After the launch, the number of merchants was relatively low (the average over the project, through communication with the Czech development team and reading related documents.
I found the following problems: The function category email list is too single, and there is almost no connection with the outside Failure to grasp the pain points of merchants to solve data mess The iteration cycle is too slow and does not reflect agile development In response to the category email list above problems, after many discussions in the group, we quickly formulated a series of solutions: 1. Resident research Through the telephone communication with some merchants in the early stage, we realized a very serious problem in the previous product design: it was separated from the actual needs of users.