When we design a product plan, we need to sort out the logic, so as to ensure the rigor of the product plan and reduce the chance of later rework. If we start drawing prototypes directly when we receive the requirements, without logical sorting, it is easy to cause many mistakes in product solutions, which directly affects our work efficiency.
Generally speaking, before we draw a product prototype, we first need to sort out two core logics:
1. Product solution logic
It starts from the perspective of the macro system and cuts into the requirements at the level of sustainable iteration, which usually requires the cooperation of multiple roles. When sorting out product solutions, we must pay attention to the problems faced by different roles, how to continue to observe, and think holistically from an optimization perspective.
We can start with the actions of the first user and carry out logical deduction. If we want to develop a platform for customers to place orders online, then we can start with the action of placing orders for customers who want to ship. After the customer places an order, which downstream role should the order data receive? After receiving it, which other downstream roles need to cooperate and support, so as to continuously extend and expand.
We can only present all the role intersection scenes in the style of a swim lane diagram after sorting it out clearly, clarify that each role must support the specific work of the entire product solution, and finally output the flow chart of the product solution.
2. Page flow
The page flow is a logical combing from the micro product function level, and it is a product capability included in the product plan. It is often used for the optimization of large and small function points, and the sorting out of a certain function point in version upgrades.
For example, in the scenario where the customer places an order, accepts it, and creates the order we mentioned above, what page is the customer on, what module is clicked to place the order, and how does the acceptance department create the waybill after acceptance. The specific operation process of such a page needs to be sorted out one by one.
If you want to optimize function points, you can start from the core page where users and data meet; if it is an independent function, you can start from the function entrance, thinking about who the users are on each page and what the needs to be solved are.
3. Precautions
Whether it's a swim lane diagram, a flowchart, or a simple wireframe, as long as the logic can be clearly described. When thinking about a plan, there will be multiple plans and multiple scenarios. When we cannot judge the pros and cons, we can output multiple plans and discuss and decide together.
To sort out the plan, it is necessary to strengthen communication with the team members involved in the requirements, especially the opinions of developers need to be taken seriously to ensure that the plan is feasible. After the plan is sorted out, it is necessary to discuss and confirm with the team members and leaders as soon as possible to ensure that there are no major flaws in the plan.
In order to further improve the quality of requirements analysis, the CoCode requirements analysis tool uses AI to quickly analyze user requirements defects, such as ambiguity, duplication, omission, inconsistency, and complexity, in a few minutes through requirements testing and consistency testing, and accurately lock requirements problems, thereby more efficiently correcting defects. In addition, the tool can automatically generate UML diagrams to provide a basis for design.
At present, CoCode releases a series of AI development tools: Co-Project intelligent project management tool (requirement itemization, automatic generation of test cases), requirement analysis tool, review analysis tool, and story point estimation tool. Among them, the Co-Project project management platform has released 4 major versions, free trial for 30 days; and released a series of CMMI efficient implementation tools to achieve full coverage of the CMMI standard process and fully support the implementation of CMMI3-5 levels.