A PM's guide to communicate effectively with software engineers

Re:A PM's guide to communicate effectively with software eng... by BlargMcLarg on Monday February 21, 2022 @07:00PM (#30422396)

This feels like a huge leap to justify "quantity of communication = quality of communication", while disregarding the effects it has on individuals, or the product. It also pushes people further into constant synchronous communication.

>Every single one of these promotes communication

It promotes adaptation. It doesn't specify whether it should take half your workday or just 30 minutes, that's for individuals to figure out and progressively adapt to.

[ Parent | on HN ]

Re:A PM's guide to communicate effectively with software eng... by TameAntelope on Monday February 21, 2022 @07:20PM (#30422572)

If you can't see how "interaction" and "collaboration" requires "communication", I probably can't help you.

[ Parent | on HN ]

Re:A PM's guide to communicate effectively with software eng... by BlargMcLarg on Monday February 21, 2022 @07:37PM (#30422725)

Fortunately I do not require your help. If you would instead highlight where exactly the manifesto requires a quantity of communication as large as half a day if not more, or prove that this is so valuable it warrants bypassing individual needs, I'm all ears.

[ Parent | on HN ]

Re:A PM's guide to communicate effectively with software eng... by TameAntelope on Monday February 21, 2022 @07:52PM (#30422823)

What, do you think, I meant when I wrote about "interactions" and "collaboration"? Am I quoting something or are those words I chose on my own?

[ Parent | on HN ]