top of page

Forum Posts

Md Saim
Jul 31, 2022
In Fashion Forum
5. Discuss on a small scale first Before the meeting is notified, the product business email list manager communicates with the core stakeholders about the needs of the review (such as R&D docking personnel), eliminates major problems in advance, and avoids major accidents at the meeting. The scene of the requirements review is often intense, and usually everyone will ask various questions from their own perspectives for the product manager to answer. So what can be done to improve the efficiency and quality of the meeting, so that everyone can have a happy meeting? After reading the case below, you may know that this should be done. At a requirement review meeting, the PM explained the functional operation logic very clearly, but the R&D did not understand the application scenarios of the function; whether the steps of the system operation were too complicated to discuss repeatedly; the PM and R&D debated on the realization method of a certain function; the R&D was very serious It is necessary to understand the restrictions of each field... 1. Discuss around the topic Discussions around preset themes are one of the prerequisites for ensuring the efficiency and quality of meetings. During the meeting, we need to identify in time whether the current topic is still in the agenda. If it is beyond the scope, we need to guide it back in time. The extended topics can be recorded in advance, and relevant personnel can be organized for discussion after the meeting.
Discussions around preset themes are one of the prerequisites. content media
0
0
1
Md Saim
Jul 31, 2022
In Fashion Forum
1. Clarify the theme of the meeting Everyone is busy, so meeting topics, topics, and business email list outcomes need to be clear and communicated in advance. Taking the above example as a warning, not only the progress and resources are affected, but also the character value of the organization personnel. If the character score is too low, it will not only affect the organization of the meeting, but other work will also be difficult to carry out within the team. 2. Prepare meeting materials The requirements documents, prototypes and other materials used in the requirements review meeting need to be prepared and sorted out in advance. You can't just rely on one mouth at the meeting, and let everyone else make up their minds at the meeting. 3. Confirm staff time Personnel and time are the basic elements of a meeting, and an invitation to a meeting can only be issued after confirmation. Participants: The personnel who review the requirements generally include UI, R&D (front-end, back-end, mobile), testing, and operations. According to the scope of the requirements, other relevant personnel also need to participate. Meeting time: As the number of people increases, everyone has their own business, and it is difficult to coordinate the time at this time. We first confirm the attendance time with key stakeholders, and then coordinate the time of other personnel. 4. Multiple channels of notification Meeting invitations will generally be notified separately via email and WeChat. The email notification is formal and easy to trace the follow-up events, but the attention is not enough. Therefore, after the email notification, the stakeholders will be reminded again on WeChat. Please attach the meeting materials and key notes to the email meeting invitation, so that the meeting and staff can understand the information in advance. How to write it is not discussed here. On the day of the meeting or 1 hour before the start of the meeting, wechat reminds the relevant participants again to avoid being busy with other things and forgetting to attend the meeting.
Meeting invitations will generally be notified separately via email and WeChat.  content media
0
0
1
Forum Posts: Members_Page

Md Saim

More actions

Subscribe Form

Thanks for submitting!

©2021 by Hang It Up Kim. Proudly created with Wix.com

bottom of page