Requirement communication and implementation

I don't know how everyone works together in their daily work and projects, the Requirement Analysis in the project does not know the specific methods for communication and coordination.

The English name of the cartoon chart below is "How Projects Really Work", which is also the "Swing demand Chart" that the product manager or project manager often calls ". Today, when I was looking for this image, I found a site with this image as the topic. This cartoon image is derived from the official version 1.0 and the beta version 1.5 Based on the familiar version 2.0. The following is a one-to-one list.

How Projects Really Work (version 1.0)

How Projects Really Work (version 1.5)

How Projects Really Work (version 2.0)

Presumably, those who want to meet product requirements and project requirements are familiar with the above "Swing demand Chart", and will feel the same in the daily product and project demand management. Indeed, requirements in products or projects
Communication and requirement understanding have become an important cost in the project. It has become a top priority for the project to effectively understand the customer's needs and correctly convey them to the project implementers.

Recently, I saw another picture about the product project requirements. Now I will call it the "Gun demand diagram. Just like the above charts, you only need to use text instructions to make them more memorable.

What the customer wanted was a gun with simple structure, low price, and ability to adapt to various environments, but he described it as an underwater rifle (Russian APS underwater assault rifle );

The Project Manager only remembers the simple structure and low price part (the so-called "people's assault gun" VG1-5 developed by Nazi Germany at the end of World War II is basically pieced together with edges );

The project constructor designed a product that is very different from the customer's needs, but still basically decent (the 7mm-caliber EM-2 developed by the UK after the second world war without a tornado, all aspects of performance is good );

On this basis, programmers made a weakening of the caasma version (Britain was forced to follow the NATO agreement to adopt the SA-80 56mm small-caliber assault rifle, there are many quality problems );

The implementation consultant blew this product very awesome (the "ideal individual weapon" program of OICW in the United States has the ability to launch 20mm smart grenades and 56mm bullets, the project has been suspended for an indefinite period );

Project documents are clear at a glance;

The final product handed over to the customer was a piece of junk goods (the stochastic gun produced by Britain during World War II, known for its simple structure, low price, ugly shape, and poor security );

The customer spent far more than the product value (the 89-style assault rifle in Japan, each of which is priced at $3900, And the M16A2 in the same period is only worth more than $500 );

The after-sales service of the product is completely rubbish (the liberation of FP-45 *, is the simple weapon that the US Strategic Intelligence Agency used to distribute to the resistance organizations occupied by the Axis States during World War II, in order to avoid being captured and used by the enemy, the product is extremely crude and can only be loaded and shot in a single shot. He was lucky when he was hit 10 meters away ......);

What customers really need is AK47 ......

Understanding and communication of requirements is a prerequisite and necessary for product and project implementation. This is worth taking seriously and should be understood and correctly communicated to everyone on the project line before the project starts.