.png)
Different companies have different software development processes, cooperation methods and target management methods. For email list the team, there is no best way, only the most suitable way for the team .
At this stage, we need to allow ourselves to temporarily forget the previous way of working and embrace the current way of the team. Improvement is okay, but that's after, what needs to be done now is open up to the mix and try to understand why the team has chosen to work this way.
You must know that the evolution and iteration of organizations also follow the rule of survival of the fittest .
The process we need to sort out includes the following 6 points:
How to formulate and manage team goals, such as how to split OKRs, how to align and review them in stages.
What is the review process in product design, and what are the rules within the team for requirements pre-review, interactive review, visual review, and full-staff review.
What is the process of demand management, how to obtain the needs of users and customers, what rules are used to digest demand, how to manage demand pools, etc.
In what form is the product requirements document written, using Word? Full-scale design drawings?
What key elements are needed, user stories? flow chart? How to save and manage these documents.
And what is the product acceptance and online release process, what needs to be done, and who is responsible, these also need to be known as much as possible.
If you want to get this information, you can explore and understand it in the in -depth chat in the fourth session . More information can only be mastered gradually in subsequent work practice.
If there are these collaborative process documents inside, that's the best, bookmark and read. If not, then take the time to take the initiative to sort out and settle.
Trust me, colleagues and future generations will appreciate and admire you.
6. Humble Observation of Meetings
Auditing a meeting is an efficient way to get product context , work atmosphere, and co-worker style . The principle is to see more, think more, and evaluate less .
For example, if you participate in a requirement review meeting , if you have time, you can read the design draft in advance to understand the project background and try to understand why it is done. Read more and think more, and try to comment as little as possible, because the information difference is too large, and the evaluation is easy to be biased.
Of course, if you don't understand something, you can ask in time or ask after the meeting.
Another example is to participate in product launches, pre-sales managers demonstrate products for customers , etc., to understand colleagues in other positions, what they are doing, and why they are competent.
Of course, if there is a user interview meeting, it is even more necessary to participate~ You can directly contact the user's feedback.