First analyze why the demand changes frequently before taking corresponding measures.
Changes in demand generally include the following situations:
Requirements unclear. The product did not evaluate and analyze the requirements during the requirements collection phase. During the design process, the product came up with new ideas and proposed changes in requirements.
Different users have different ideas. During the project process, the product continuously collects user feedback, hoping to meet user feedback and propose changes to requirements.
During the development and testing phases, problems that cannot be implemented or errors in business processes are discovered, and requirements changes are proposed.
The superior leader’s ideas, what the product wants to meet, and the proposed change of requirements.
Some trivial things may seem simple, but in fact they are needs that affect the entire system, such as adding permissions, adjusting fields, or reducing some functions.
How to avoid Uncertainty in demand leads to more duplication of work:
First of all, we must clarify our interest demands, understand the reasons for the changes, and find a balance point.
Secondly, evaluate the priority of requirements, communicate with multiple parties according to the schedule, and ensure that the project can proceed normally.
According to the process, the certificate will be stored by email. Once the design is sealed and entered into development, no changes to the requirements are allowed.
Do you have too many projects running in parallel? The situation: While pursuing the restoration of Project 1, I had to continuously hold meetings to communicate the needs of Project 2. I also had to do design analysis for Project 3, and at the same time, I had to revise the design draft of the delivered Project 4. I worked overtime to the point of breaking out, and finally I started to doubt myself: What on earth are I doing!?
Don't let work control you, learn to control work. Learning time management is to ensure that you can work in a quite comfortable state and rhythm. Think mainly from the following highlights:
Time allocation: during a project: thinking, communication, Allocation of the time ratio occupied by output.
Improvement of design efficiency, such as normative summary and use of shortcut keys.
For time management, I recommend the book "Be Friends with Time" Book.
You have thought about so many issues during the design process, how can you let others know what you are thinking about? What about the process?
There are always no highlights during the review. How can we make the mediocre 15 minutes more memorable?
How to enhance the persuasiveness of the design plan?
What should you do when the product does not agree with your solution?
All of the above This is a problem I encountered during design reviews.
When I first started the design review, I was very weak and nervous. I was helpless. I just started to talk a few words about the plan, but when I saw the expressions of a group of big guys, I became even more panicked! Often what the big guys say at this time will be nodded in approval, but after the review, they will feel that there is still a problem. In fact, the suggestions given by everyone are not necessarily the most appropriate, and you need to make independent thinking and judgment on your own.
The design review is a good time to communicate with everyone You can use this opportunity to express your design thinking. In order to improve my ability to explain the review plan, I actively participated in the team's reviews, thinking about everyone's explanation ideas and words, and then combined with my actual situation to improve my expressive power.
粤ICP备***号 粤公网安备 44010xxxx449号 Powered by YCMS SiteMap
本站为YCMS源码系统演示网站,所有信息均来自网络,仅用于填充页面效果
如演示信息侵犯了您的权益,请联系我们,将第一时间删除