In 2021, when I change jobs, I need to do a phased knowledge summary. In addition, I talked to Mr. Ma Chang from the Jira community Whatsapp Database about the incompatibility of the C-side product manager on the B-side, which led to the difficult demand problem in the delivery of the B-side major customers. As usual, let’s talk about the basics of perspective first. The author Whatsapp Database has 10 years of experience in the software industry. In the past 7 years, I have delivered many major customer projects, done various projects, and encountered various types of customers; the limitation of perspective is that all Major customers are operators.
This article mainly discusses the thorny issues in making requirements, and has some overlap with the project manager in terms of responsibilities; the Whatsapp Database topics discussed include: requirement change, delivery inconsistency, requirement collection, requirement pool management, executive demand response, etc. Each topic first analyzes the reasons, Then give Whatsapp Database solutions. Note: The "customer" in the text usually represents the interface person who receives the needs of the business party on behalf of Party A or the company. 01 Customers are change freaks Frequently changing customer requirements is a headache.
Means we fail to solve customer problems, wastes time, and frustrates the team and affects morale. There are 4 possible reasons for frequent customer Whatsapp Database changes: there is a gap between requirements and products, the customer is not the original requester, the customer himself does not think clearly, and the customer's business changes frequently. The gap Whatsapp Database between demand and product is mainly because the demand described by the customer is inconsistent with what he really wants. He does not know whether it is what he wants until the product is used by him.