A brief talk on product manager, research and development, test, three friends how to communicate effectively

A brief talk about product manager, research and development, testing, three friends of that point (1)

The internship time, has been in the work for five years, has been engaged in software development and testing work, during the part-time also done part of the product manager thing, the delicate relationship between the three, quite sentiment.

1. first to read the "pain points" of these three posts

At the party, often encounter the following situations, after hindsight, often have a sense of amused feet.

The development of GG is like this:

A chat to their project, two eyes began to take the light, while opening the mad spray mode,BlaBla A pile of high-tech terminology, on the one hand scold testers do not know the technology, the bug is not the key issue, Advanced Bug they couldn't find it at all.

On the other hand, the product manager PRD write Dog, and some even a prototype can not be drawn, all day know to stand there to ask for demand, ask for demand, make as if they really understand the user and product requirements like ... Between words, is full of dissatisfaction with their own environment and non-technical positions of contempt.

Program Ape GG pain points:

Pain Point One: The tester is not involved in the early stage,Bugs are dragged to the end only to mention, modify code, reaching, the most hateful is that the test is also chasing us to beg a set of design documents, design documents and technical implementation is sometimes two different things good or bad?

Pain Point two: Product manager does not write the requirements of the document, do not prototype design, is the mouth of communication, we research and development is not your lover, is not your belly of the worm, how do we know what you want it?

Pain Point three: project progress to rely on their own control, to compile code, but also to write summary design, detailed design, code design, the most hateful is to write the original internal look, product requirements documents are not, no comparison, write these and what is the significance? Wasting time, we work overtime every day.

Pain Point Four: Meet the current technology can not achieve the demand and a strong product manager, only cry, you tell him technical difficulty and risk, he pulled a voice with you said, "Users want this!!" ”

Pain Point Five: Program ape GG have a large number still in the ranks of single nobles, perennial overtime and boring work atmosphere, creating their stuffy character and sad status quo, although they are smart, but not good at showing themselves, although they have a good income, but still can not find female friends ...

The children's shoes for testing are like this:

Side do test are girls, MM are Most of the objects are research and development staff, generally speaking, testing for the development of GG are also extremely helpless.

"As a researcher, how can you ignore the bug that the test put forward ?" "A test of MM so complained," I see or they do not have the ability to program, not a bug for so long, said the mouth is worn, not modified? "

This shows that the developers can not effectively modify the bug, is the most let the test MM sad and headache problems.

Test The pain points of MM:

Pain Point one: Because the product development environment is unfamiliar, the test environment configuration takes a lot of time.

Pain Point Two: research and development for the test proposed bug can not be modified in time.

Pain Point Three: research and development to modify the bug, also do not Change the status in the Bug Management Library, submit test re-testing, but save up, to the end, not to disturb the test of the work rhythm.

Pain Point three: The definition of bugs, often with the development of dry war.

Pain Point Four: the right to test the discourse is not high, not respected, the general document Bug will be directly ignored.

Pain Point Five: the product to go online before the overnight overtime, really will deadly good?

Pain Point Six: Some children's shoes do white box, code Walk, analysis logic let people pain, encounter code style chaotic program Ape write garbled, more want to die ...

It's even more interesting to be a product manager's children's shoes:

At the same time there are multiple product managers in the presence of the party, they often a face confused, some simply do not know what they do is not a product manager's responsibility category, some say that they are doing operations, some say they like sales, and some said the product manager's title, the original also have to write code ...

In particular, just graduated a year or two of new products, feel that they do not know the technology, but do not understand the user, even if the company's products, but also dare not say that it is well-know, let alone the whole industry and market understanding and foresight.

Each company is in a different industry, the product is not the same, or even the same company different product departments do the product may vary greatly, larger companies, may also be more subdivision of the job responsibilities of the product manager, biased towards the front-end, biased back-end, biased operation, biased design, and biased data.

The product manager's classmates often suffer from the user, the research and development and the test three aspects pressure, the superficial discourse right is very high, because " PM is responsible for the entire product after all Ah! "But in fact, many of the company's technical team do not put the product managers in contempt, think they are a group of" do not know the technology, but also come to point to the "Zhao"!

in a highly-regarded environment, product managers are jittery, fearful, tested and developed every time because of a problem with the definition of a bug when tearing, product managers are the last to go after the people, also tend to be detained on the "definition of demand unclear" big black hat.

Product Wang's pain point:

Pain Point One: The scope of work is too wide, a kind of chores are not pleasing the feeling.

Pain Point Two: No innovative ability of the company do not you, but there is innovative ability can not play, because the product innovation is often very cautious, basic are users can not find the "micro-whole".

The pain points three: Originally thought to be a few years will become a profession and the domain has the macroscopic cognition senior talented person, did not expect in the end is to draw several pictures axure Prototype, the understanding of the product in the mind is still that way.

Pain Point Four: BRD Business requirements documentation, MRD Market Requirements document,PRD Product Requirements Document There is no time to write, before clearly and research and development communicated a functional details, the results have problems, and returned to pursue my PRD did not write, is the technical implementation of the poor, but also to blame!

Pain Point Five: I do the product manager is because nothing will go to internship, finally left, but to say this is my interest, I do not know, I do not see their future.

Pain Point Six: For the change of PM, because since then no longer programming, a year later, in addition to lip better than before, feel their career development more and more not high-end, basic one year later, can not go back to do the development.

Pain point Seven: Not a skill,axure and PS also learn to dabbler, always feel very confused, do not know their next job product direction is not this, if it is, no fresh feeling, if not, feel again to again , is the continuity of the profession not good? Alas, still confused ...

This article from "Better self, start from here" blog, please be sure to keep this source http://milkyqueen520.blog.51cto.com/11233158/1749693

A brief talk on product manager, research and development, test, three friends how to communicate effectively