In the daily project process, have you ever encountered the following situations, which made showcase not play its due role? Or is there no showcase at all?
1, insufficient preparation?
When everyone was in place to start showcase, they found that the environment was not ready, and they finally got it ready, and found that the version of the experience package was wrong, which made showcase unusable.
2. Low-level mistakes?
Finally, it can be demonstrated, but participants find low-level errors (typos on the interface) and obvious bugs, which wastes a lot of time.
3. The problem has not been followed up.
Everyone gets together to spit out the function. The exhibition turned into a tea party, and then the meeting was over. It is useless to show links.
4. It's too late to show
The product will soon be gray, but experts have put forward many opinions, and the online time has been delayed.
So how do we show our products? Combined with previous experience, the following are some technological methods for your reference and discussion.
First, the preparation stage.
1. Presentation opportunity: It is recommended to arrange it before the system test of each iterative development. The sooner the problem is found, the lower the cost of modification.
2. Exhibition organization: The organizer needs to determine the specific time (it is recommended to set a fixed time every week), collect the functional content to be displayed in advance, determine the participants and make an appointment with experts. Participants generally include: product, testing, development, design and leaders of various roles, product experts, design experts, department managers, etc. According to the importance of demand, people at different levels can be selected to participate.
3. Set pre-conditions: Only when the pre-conditions are met can you enter the showcase, thus improving the efficiency and quality of each showcase.
& gt Requirements for passing self-inspection: Self-inspection items can include common errors and some basic requirements in showcase to avoid low-level errors in the presentation process.
& gt？ Make sure the presentation is complete: it cannot be a semi-finished product. If different platforms are involved, at least one platform can complete this process.
& gt？ Experience of each role: All roles involved in requirements development, including product, design, development, backstage and so on, can pass the experience test if the requirements need to be demonstrated to the company's top management.
& gt？ User experience passes: user ce (customer? Engagement), generally, user research engineers choose specific user experience functions according to product characteristics, and record users' operating habits, problems and opinions. Experience problems discovered by ce need to be evaluated and modified before they can enter the showcase.
Second, show the stage.
1. environment preparation: prepare the demonstration environment in advance, including demonstration equipment, and deploy the application version to be demonstrated and the data needed for demonstration. For some major projects and functional demonstrations at important stages, it is best for the presenter to string together the functions to be demonstrated from a business perspective as much as possible, and prepare the demonstration steps and key paths.
2. Organization form: Generally, face-to-face meetings are convened and presided over by the organizers. The product manager (developer) will demonstrate in sequence, first introducing the commercial value of the function and what the user's needs are met, and then demonstrating. At the meeting, experts gave feedback according to the demonstration results. For the product demonstration of the mobile phone terminal, the speaker can also guide the participants to have a one-to-one practical experience according to the function points.
3. Full-role participation: Try to ensure that all roles are present, including PM, product, design, development and the person in charge of each role, so as to avoid the team's inconsistent understanding of feedback issues.
4. Problem recording: The organizer or full-time staff is responsible for recording the feedback problems on the spot and synchronizing them with the participants after the meeting.
Third, the problem follow-up and resumption stage.
1. Problem modification: After the showcase is completed, the product manager (developer) corresponding to the requirement needs to organize the development team (including development, design, backstage, testing, etc.). ) Evaluate the modification points, determine the priority, responsible person and modification completion time, and some requirements may need to re-evaluate the functional logic and interaction design.
2. Problem verification: After the development and modification are completed, the product, development and testing jointly verify the closing problem, and major changes need to be re-launched in showcase.
3. Re-quote: The exhibition needs to re-quote the demand modification points of the previous issue. Demonstrate the modification of the last question of each repetitive requirement to ensure that each modification has a closed loop.
4. Process improvement: The organizer can record, analyze and summarize the problems in each showcase, improve the self-inspection list or optimize the existing showcase process.
abstract
The target audience of showcase is often an important person who decides whether the demand can go online and whether the team development function is recognized, so it is very important to show professionalism and efficiency in the process of showcase. The above methods provide reference, and I believe everyone's showcase will do well.