Recently, we are adjusting product planning and priority around the upcoming products. Communicated with the team about the product planning project time of one month.
At work, we were also asked if we had ever encountered a scenario where the timeline was required to synchronize with the product plan. For example, the leader came today and said, “You are responsible for the one-year planning of our products.”
How would you answer such a question?
Product planning In practical work, the difficulty is not to make product planning. Because each of us can make a plan based on the current possibilities and things to do, and make a beautiful PPT.
There is no problem in arranging full planning, the difficulty is that you do not know whether planning can be landed?
-
Will there be something unexpected in a week?
-
After a month, does the market have other requirements?
-
Found so many bugs that you had to postpone?
This is that we need to understand before product planning, planning is the difficulty of landing planning. Every plan is very good, can come out of the plan must be standing on the condition of “hypothesis”
Product planning for development
Product managers design product planning periods based on business or requirements priorities. But really what can go online, or the development of the students to decide.
A good project control is important, of course, but the technical difficulty and the right mix of developers will all contribute to how quickly product planning can proceed to the desired state.
So after the product planning comes down, the product manager should take the product planning and development person to touch the planning whether there is adjustment.
For example, resources involving third-party data linkage, account migration, and interface writing of underlying services need background developers.
When it comes to product writing and UI adjustments, front-end developers are needed.
Usually a product’s UI is presented after the prototype. The time to produce a prototype is assumed to be 1 day, the UI might take 3 days, and development might take 1 month.
This problem is caused by the linkage between the front and back ends and the background management module of a page.
Some students may ask, I did not do the background prototype? Why do you need development time in the background?
Your data storage, data generation is required in the background maintenance. Even if there is no management of visual cleansing in the early stage, there are still background resources to be responsible for maintenance.
Product planning and project management
After product planning, product managers will start to respond to the needs of each stage. For example, a module function to do first, it is necessary to comb requirements output demo
Colleagues should do a good job of project management, how much time output requirements prototype, HOW much time UI design, how much time development, how much time testing.
More than 40 people in the development team. It is suggested to split each module to the corresponding developer for the convenience of finding the person in charge, urging progress and adjusting bugs.
If the team is small, it is recommended to directly manage the handover according to the product planning time point. Which time version point, seize this time point for acceptance.
Finally, I recommend no more than 2 months for product planning. Too long product planning, it is impossible to land, such planning is meaningless.
The content of product planning should be synchronized with the development and design of the team, so that the team can know what the weekly task is, and clearly avoid the problem of unreasonable resource utilization.
Well, that’s our original for today. I will insist on writing 2 original work cases every week
Recommended reading:
Do it for a year and recruit 100 product managers
My first book. Here it is
In 2018, let’s move on!